An SEO audit is an evidence-based investigation of how a website supports discovery and useful customer journeys. It identifies problems, explains their likely impact and turns justified findings into implementable priorities. A crawl export or a score by itself is not a complete audit.
The scope should follow the business and application. A store, a local service website and a membership portal have different URL patterns, access rules and conversion tasks. Preserve those differences instead of applying every tool warning as a universal instruction.
Define the question and access boundaries
Record the website's important offers, public page types and intended outcomes. Identify available access to code, CMS, analytics and Search Console. State what cannot be verified rather than filling gaps with assumptions.
Keep private data and credentials out of the report. Read-only inspection should come before changes. A useful audit can progress with public evidence while clearly marking findings that require additional access.
Create the baseline inventory
Combine discoverable links, sitemap URLs and the CMS or route inventory where available. Record status, indexability, title, description, H1, canonical and page purpose. Include the test date and environment.
A crawl sees only what its configuration can discover. Compare inventories before declaring a page absent. Separate a local implementation issue from evidence about a different production deployment.
Investigate technical findings by cause
Check public responses, directives, alternate versions, rendering, redirects and important customer tasks. Group related errors when the evidence points to one template or configuration problem.
The technical checklist provides individual checks. The audit adds prioritisation and ownership: which problem affects an important page, who can change it and how will the result be verified?
Review content against a real purpose
Check whether the title, heading, body and next step describe the same task. Identify unsupported claims, missing useful information and unnecessary duplication. Do not label a page thin solely because it is shorter than another page.
Use the search-intent guide to distinguish a service explanation from a learning resource. Content recommendations should reflect what the business can accurately provide.
Evaluate architecture and conversion together
Important pages need relevant navigation and contextual references. Forms and contact links need functional checks. A website can be discoverable while failing to deliver enquiries to the right team.
Record the observable failure separately from its possible commercial effect. A broken notification is evidence of a delivery problem; without business records, the audit cannot invent how much revenue it cost.
Write findings that someone can implement
Every significant finding should include the issue, affected URL or file, reproducible evidence, impact, proposed fix, owner and acceptance check. Mark hypotheses as hypotheses.
An illustrative finding might identify one service template generating another page's canonical. A useful recommendation would specify the correct per-page output and a representative verification sample instead of saying only “fix duplicate content.”
Prioritise by impact, confidence and dependency
Address barriers to important public pages and customer tasks before cosmetic warnings. Consider release risk and whether another task must be completed first. A development constraint should remain visible in the plan.
Avoid calling every finding critical. A meaningful severity system helps the business allocate effort. Keep low-priority items in a backlog rather than pretending they need immediate work to prevent disaster.
Verify the implemented result
Back up significant changes, preserve application logic and test affected routes. Compare before-and-after evidence. Use appropriate system checks and tests, but do not equate a passing test suite with complete SEO verification.
Google's Search Console starting guide is useful for search evidence. The actual audit should also inspect the website itself. Discuss SEO services or request a consultation with a clear scope so the work ends in verified improvements rather than an unowned recommendation list.