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.
- Scope
- Evidence
- Prioritise
- 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.
- Write the intended state for the exact URL: public search result, alternative copy or private utility. Confirm who owns that decision.
- 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.
- If the exclusion matches the intended state, keep it and document why. If it conflicts, identify the smallest confirmed defect before proposing a change.
- 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.
Source: support.google.com.