Key takeaways
- A useful audit states the affected URL, evidence, impact, owner and verification step for each finding.
- The report below is an illustrative example; it contains no client results or measured ranking gains.
- Prioritize fixes by customer value, scope and confidence rather than a generic SEO score.
An SEO audit report should tell someone what to do next. A long export of warnings is not yet a plan. The reader needs to see which pages matter, what is broken or missing, how the finding was confirmed, and how to verify a fix.
This article shows a compact sample for an imaginary Kathmandu service business. Every URL and observation in the example is invented for teaching; it is not a before-and-after case study or a claim about a client. For the step-by-step inspection process, use the existing complete SEO audit guide. Here we focus on the report a business owner and developer can actually use.
Table of contents
What should the first page of an audit say?
Start with scope and decisions. State the domain and pages reviewed, access provided, tools used, date of inspection, and known limitations. Summarize the three highest-value actions in ordinary language. A reader should know whether the issue affects a money page, a blog article or an intentionally excluded URL. Separate confirmed defects from hypotheses that need further data.
For example, “Three old service URLs redirect to the home page” is a testable finding. “The redirect issue caused a 40% loss of leads” is a much stronger claim that would require comparable lead records and a careful change history. The report should not smuggle the second claim in as if it followed from the first.
Annotated SEO audit report example
Illustrative sample only: Imagine that example-business.test offers building maintenance in Kathmandu and recently changed its site layout. The observations below show how to write findings, not what has happened on a real site.
| Finding and evidence | Priority and owner | Action and verification |
|---|---|---|
Old /services/repair/ returns 200 but contains only a generic “page moved” message. | High · developer | Redirect to the closest live repair service page. Fetch the old URL and confirm the final destination and status. |
| New service page has no clear service area or examples of work. | High · business owner + editor | Add accurate locations served, scope, process and genuine evidence. Review the rendered page on mobile. |
| Sitemap lists a retired page and omits the main maintenance service URL. | Medium · developer | Update sitemap to canonical live URLs; resubmit and check later discovery. |
| Blog articles mention services but do not link to the relevant service page. | Medium · editor | Add a few contextual links where they help the reader. Crawl the site to confirm links resolve. |
| Search Console shows impressions for an informational query, but the matching URL is not known. | Investigate · analyst | Filter by query, inspect the Pages tab and record the actual URL before rewriting any page. |
One row is deliberately marked “Investigate.” Good reports retain uncertainty where evidence is incomplete. Google describes how query and page filters help identify the URL behind a search.
How do you decide what to fix first?
Use a short decision rule rather than an unexplained score. First, fix problems that prevent important pages from working: server errors, an accidental noindex, broken redirects or missing main content. Next, improve pages that can serve a real customer need but lack a clear offer or answer. Then handle smaller metadata, formatting and cleanup tasks. Scale matters: a broken template used by thirty service pages deserves attention before a typo on one archive page.
Include the owner and dependency. The developer can repair a redirect, but the business owner must supply accurate service details and approve real proof. If a finding depends on Search Console access or a crawl after launch, mark that dependency. Google's site-move guidance specifically calls for URL mapping, relevant redirects and checking for crawling or indexing errors after a move.
What evidence belongs beside each finding?
For a technical issue, record the URL, response status, canonical, screenshot or rendered test, and when it was checked. For a content issue, quote the missing or confusing passage and show the searcher's task it fails to answer. For a measurement issue, name the report, date range and filter. Where possible, provide a link to the exact Search Console view or a reproducible test.
Keep raw crawl exports in an appendix, not in place of the summary. A business owner should be able to approve the next action without reading hundreds of rows. A developer should have enough detail to implement and test it. Once a fix ships, append the release date, tested URL and later Search Console observation. A report becomes more useful when it is a living work log.
What an audit report cannot promise
An audit can identify problems and opportunities; it cannot guarantee a ranking position or a delivery date for Google to recrawl and reflect every change. Google's content guidance emphasizes helpfulness and originality, while its site-move documentation notes that processing varies by site and URL. That is why an honest report separates confirmed defects, reasonable recommendations and open questions.
If you are comparing providers, ask to see a redacted sample report, the scope of implementation, and the method used to verify work. The SEO expert selection guide gives further questions. For a service proposal, the report example should make the work concrete without inventing client outcomes.
Sources and further reading
Need an audit with evidence, owners and a clear action plan?
Get in touch