The average SEO audit report fails in the same way: sixty pages of findings, every one marked "high priority", and six months later nothing has changed. The problem is rarely the analysis. It's the structure. A report built as a list of everything wrong hands the hard part, deciding what to do, back to the person least equipped to do it.
This template is built the other way round. It leads with the handful of things worth doing first, gives every finding an owner and a way to check it's fixed, and keeps the long tail out of the way. Copy it, adapt it, and use it for your own site or for clients.
What a good audit report has to do
Before the template, the test. A report is doing its job if the person reading it can answer three questions in under five minutes:
- What should we do first? Not the full list, the next move.
- Who does it? The developer, the content writer, the business owner, the hosting company.
- How will we know it worked? What changes, and where to look.
If your report can't answer those on the first page, it will be read once and filed.
The template
Copy this into a document and fill in each section. The comments in brackets explain what goes where; delete them as you go.
# SEO audit: [site or page], [date]
## 1. Summary
[Two or three sentences a business owner can read on its own. What's the
overall picture, and what's the single most important thing to fix?]
Scope: [pages or site sections checked]
Method: [tools and checks used, and anything NOT checked]
Audited by: [name] Next review: [date]
## 2. Do these first (top 3)
| # | Fix | Why it matters | Owner | Effort | How we'll verify |
|---|-----|----------------|-------|--------|------------------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
## 3. Quick wins
[Small fixes that take under an hour each. Title tags, missing
descriptions, a stray noindex, broken links. List with owner.]
## 4. Findings by area
### 4.1 Crawling and indexing
### 4.2 Speed and Core Web Vitals
### 4.3 On-page (titles, descriptions, headings, content)
### 4.4 Structured data
### 4.5 Mobile and accessibility
### 4.6 Trust and security (HTTPS, headers, email authentication)
### 4.7 AI readiness (crawler access, entity links, quotable content)
For each finding:
- What we found: [plain English, with the exact page or setting]
- Evidence: [screenshot, value, or the line of code]
- Why it matters: [the effect on visitors, rankings or enquiries]
- Fix: [what to change, specific enough to hand to the owner]
- Owner / effort / priority:
## 5. What's working
[Things that are already right. It builds trust in the rest of the
report and stops people "fixing" what isn't broken.]
## 6. Roadmap
[Anything bigger than a quick win, in order, with rough timing.]
## 7. Measuring the result
[Which numbers to watch (Search Console clicks and impressions for the
affected pages, Core Web Vitals, enquiries) and when to re-check.]
## Appendix
[Full crawl exports, raw data, anything a specialist might want.]
How to fill in each section well
The summary is for the person who pays. Write it last, in plain English, and resist the urge to include a score. A single number invites arguments about the number instead of action on the causes (why a website score isn't an audit).
"Do these first" is the most important part of the report. Pick three. Rank them by impact on the business goal (enquiries, sales, being found) against effort, not by how technical or alarming they sound. A missing meta description on the homepage often beats a complex crawl-budget issue on a 30-page site.
Every finding needs evidence. "Images are too large" gets ignored. "The hero image on /services is 4.1 MB and takes 6 seconds to load on 4G" gets fixed. Specific pages, specific values.
Every finding needs an owner. If nobody's name or role is next to it, it belongs to nobody. Be honest when the owner is outside the team, such as the hosting provider or a plugin developer.
Say how you'll verify it. "Re-run the check and confirm the title is under 60 characters", or "Confirm the page appears in Search Console's indexed pages within two weeks". This is the step most reports skip, and it's why the same issues appear in next year's audit.
Keep the long tail in the appendix. A 200-row crawl export belongs at the back, not in the findings. If a specialist needs it, it's there.
See a finished example
Our sample report is a real, unedited AuditCrow scan of a real UK business site, published with the domain anonymised. It follows the same shape as this template: one verdict, the fix that matters most with its evidence, then a prioritised task list in plain English. It's a useful reference for tone, and for how much detail each finding needs.
Filling it in faster
You can run every check in this template by hand with free tools: Google Search Console, PageSpeed Insights and the free checkers on this site for redirects, title and meta tags, structured data and robots.txt. Our guide to how to audit a website walks through the checks in order.
If you'd rather start from findings than a blank page, a free AuditCrow scan fills in most of sections 2 to 4 for one page automatically, already prioritised, with the fix for each written in plain English. Agencies running audits across client sites can see how AuditCrow handles that.
