SEARCH ENGINE
FENG SHUI

Technical

Business SEO audits: deliver decisions, not a score sheet

A useful audit connects each issue to a page, a possible effect and a verifiable action. A long generic recommendation list is not an implementation roadmap.

Define scope

Specify hostname, languages, page types and priority journeys. Record inaccessible areas and measurements not performed. Conclusions should match actual coverage rather than an exhaustiveness promise unsupported by collection. Include the source and date of each inventory.

Classify evidence

Separate observed errors, hypotheses and general practices. For a broken page, provide URL, status and test. For suspected content weakness, explain the reader question and missing answer. An automated score alone does not explain a problem.

Prioritise repairs

Compare probable effect, affected volume, risk and effort. Important-page access and functioning journeys normally deserve attention before cosmetic metadata changes. Assign owner, deadline and dependencies so recommendations become executable work.

Accept the changes

Define how to verify a repair and retain the result. Sending a recommendation to another team does not complete it. Repeat the original check after publication and record limits on verification rather than silently closing the issue.

A four-step method: Scope → Evidence → Prioritise → Accept
A process, not a statistical result.
  1. Scope
  2. Evidence
  3. Prioritise
  4. Accept

Worked example

Audit ticket: URL / evidence / affected need / hypothesis / action / owner / effort / acceptance. Example: correct an internal link to a 404 by pointing to its equivalent, then test the click and final response.

Check before moving on

These checkboxes are not saved.

Sources & method

Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.

Topic provenance: Quand faire un audit SEO ? (consulted capture: 2023-11-30). Search Engine Feng Shui. This record does not confirm an individual byline.

This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.

Decide which URL should be indexed before calling a status an error

An excluded URL may be behaving as intended. Google’s Page indexing documentation distinguishes intentional alternatives from pages whose exclusion conflicts with the site’s purpose. Do not change canonical or noindex settings simply to reduce a report’s count.

  1. Write the intended state for the exact URL: public search result, alternative copy or private utility. Confirm who owns that decision.
  2. Compare the report’s date with the current HTTP response, robots directives, canonical target and actual content. A browser’s HTTP 200 does not establish Google indexing.
  3. If the exclusion matches the intended state, keep it and document why. If it conflicts, identify the smallest confirmed defect before proposing a change.
  4. Verify the implementation separately from any later search result. Do not promise indexing or a ranking position.

Fictional audit: /print/guide/ intentionally duplicates /guide/ and names it as canonical. Its exclusion is consistent with the design. Conversely, the unique public /guide/ accidentally contains noindex after a preview deployment: that conflicts with its documented purpose and warrants a scoped fix. An authenticated account page remains private; removing protection to make a report green is inappropriate.

Record: exact URL __; intended state __; report/crawl date __; live response __; directive __; canonical __; actual difference __; action/owner __; later verification __. Google’s guidance does not treat alternative language pages as ordinary canonical duplicates. Keep complete language equivalents self-canonical and use their proper hreflang relationship. This exercise uses no account data and is not a fresh GSC audit of this site.

Decide which URL should be indexed before calling a status an error
Public original · Intentional alternative · Private utility.

Source: support.google.com.

Keep reading

All guides ↗

A three-ticket audit that can be accepted

Priorities become clearer when two people can repeat the same check. Use a small ticket queue before assigning an overall score: record the reader task, observed failure, exact action and evidence that will close it.

Three hypothetical tickets

ObservationActionAcceptance evidence
A guide’s internal link ends at a 404.Find the genuine equivalent and change that link.Click the corrected link; final 200 contains the expected answer.
A translated page points its canonical to another language.Check equivalence and set the correct self-canonical for a complete translation.Rendered/head HTML, reciprocal language links and final URL agree.
A title is vague but the reading path works.Describe the existing task accurately.One title, matching H1 and unchanged factual promise.

Do the access repair first, then the metadata

  1. Capture the failing URL, date and status; record how the link was reached.
  2. Check the proposed destination’s intent. An unrelated homepage is not an equivalent answer.
  3. Prepare the precise change and keep the previous file or configuration for rollback.
  4. Repeat the original click after publication. Add the final response and expected content to the ticket.
  5. Leave search impact unmeasured until comparable data exists. A 200 is technical evidence, not proof of ranking recovery.

Do not treat all canonical or redirect reports as errors. Decide whether they implement the intended URL relationship. An incomplete translation must not be declared a full language equivalent simply to complete a checklist. Google distinguishes canonicalization from redirecting readers; its guidance supports the checks, while this fictional ticket order is an editorial example, not a universal priority score.

Broken journey; Repair + replay; Language identity; Check equivalence; Vague title; Verify promise
Original audit triage board; the tickets are hypothetical, with no invented traffic values.

Steps: Broken journey → Repair + replay → Language identity → Check equivalence → Vague title → Verify promise.

Download the working card ↓

Written by Search Engine Feng Shui. Source: Google · Canonical URLs.