A useful SEO audit answers a decision
An audit should not be a long export of warnings. It should show which obstacle affects an important page or a buyer action, the evidence for it, and who can fix it. Start with Google's SEO Starter Guide and inspect your own property in Search Console.
A small fictional service-business sample
| Observation | Evidence to collect | Priority |
|---|---|---|
| A core service URL is absent from the index | URL inspection, sitemap, robots and canonical checks | Urgent if the page is commercially important |
| An indexed page does not answer the buyer's question | Queries, landing page, offer and next step | High when demand is relevant but the page is weak |
| Reports cannot distinguish a completed inquiry | Submit a real test form and inspect the event | High before judging channel performance |
This is an illustrative sample, not a client audit. A tool warning alone does not prove lost business; verify the template, URL and user path.
Use a reviewable priority rubric
Score each item from 1 to 3 for business impact (does it affect a service page or inquiry path?), evidence confidence, and implementation effort. Address high-impact, high-confidence blockers first, then map dependencies. A crawl issue affecting all service pages can outrank a minor title edit; a broad template change needs testing and a rollback plan.
A useful handoff records the audit scope, sampled URLs, evidence, expected effect as a hypothesis, owner, effort range, and acceptance check—for example: “URL returns 200, is indexable, and the inquiry event fires once.” Do not promise rankings or traffic growth.
Before work, arrange appropriate Search Console and Analytics access, a service and market list, recent site changes, and the business definition of an inquiry. Keep credentials and customer data out of the report. Discuss a scoped SEO engagement with our team.
