SEO Audit Report: Free Template, What to Include and an Example

Most SEO audit reports fail in the same way: a hundred-row export lands in someone's inbox, nobody knows which three rows matter, and six months later the same issues show up in the next audit. A good report is short at the top, specific in the middle and ends with who does what. Below is a template you can copy, the reasoning behind each section, and an example of a finding written so that a developer can fix it without a meeting.

Key Takeaways

• Lead with decisions, not data. The first page should say what is wrong, what it costs and what to do first.
• Every finding needs five fields: what is wrong, where (URLs or templates), why it matters, how to fix it, and who owns it.
• Prioritize by impact and effort, and group issues by template - one fix to a template often clears hundreds of URLs.
• In 2026, add an AI search readiness section: AI crawler access, content in the HTML, and whether key pages answer questions clearly.

The Template

Copy this into your document tool and fill it in. Section notes follow below.

# SEO Audit: [Site] - [Month Year]

## 1. Executive summary
- Overall state in one sentence.
- Top 3 issues, each with impact and the fix.
- What we recommend doing in the next 30 days.

## 2. Scope and method
- Pages/sections audited, date of crawl, tools used.
- What is out of scope.

## 3. Scorecard
| Area                   | Status | Issues | Top issue                     |
|------------------------|--------|--------|-------------------------------|
| Indexing & crawling    |        |        |                               |
| Technical performance  |        |        |                               |
| On-page & content      |        |        |                               |
| Structured data        |        |        |                               |
| AI search readiness    |        |        |                               |

## 4. Priority findings
| # | Issue | Affected (URLs/template) | Impact | Effort | Owner | Status |
|---|-------|--------------------------|--------|--------|-------|--------|

## 5. Findings by area
### 5.1 Indexing & crawling
### 5.2 Technical performance
### 5.3 On-page & content
### 5.4 Structured data
### 5.5 AI search readiness

## 6. Roadmap
- Next 30 days / 60 days / 90 days.

## 7. How we will measure progress
- Metrics, baseline, target, where they are tracked.

## 8. Appendix
- Full issue export, crawl settings, glossary.

What Goes in Each Section

1. Executive summary. Written last, read first. One sentence on the overall state, the three issues that matter most with their business impact, and the first actions. If a reader stops here, they should still know what to do.

2. Scope and method. What was audited, when, and with which tools. This protects you when someone asks why a section was not covered, and makes the next audit comparable.

3. Scorecard. One row per area with a status and the single most important issue. Keep it to five or six areas; a scorecard with twenty rows is a second export.

4. Priority findings. The heart of the report. Rank by impact and effort, and record findings per template where possible: "all product pages" is one fix, while 4,000 URLs listed separately look like 4,000 fixes.

5. Findings by area. The detail behind the priority table. Each finding uses the same structure (see the example below), so developers and writers can work through them without asking questions.

6. Roadmap. Turn findings into a 30/60/90-day plan with owners. An audit without a roadmap is a list of opinions.

7. Measurement. Which metrics should move, from what baseline, and where they are tracked: indexed pages and impressions in Search Console, Core Web Vitals, AI impressions in Search Console's Generative AI report, AI assistant referrals in analytics.

8. Appendix. The full export, crawl settings and definitions. Everything that supports the report but would bury it.

The AI Search Readiness Section

Audit reports written before 2025 rarely had this section. Today it should answer four questions, each with evidence:

1. Can AI search crawlers reach the site? List how robots.txt treats OAI-SearchBot, PerplexityBot, Claude-SearchBot and the training bots, and whether a firewall or CDN blocks them. Our AI Bot Access Rules check reports the rules per bot.
2. Is the content in the HTML? Most AI crawlers do not run JavaScript, so client-rendered content is invisible to them. See which crawlers render JavaScript.
3. Do key pages answer questions clearly? Question-style headings, a direct answer in the first sentences, facts with sources. The Self-Contained Answer Passages check tests this; our AEO guide explains the rules.
4. Are pages eligible for AI features? For Google, that means indexed and eligible for a snippet, with the Search generative AI control in Search Console left on include (the default since August 2026); nosnippet and restrictive max-snippet values limit what AI Overviews can use.

Example: A Finding Developers Can Act On

Finding 3 - Product pages ship a generic meta description

• What: Every product page uses the same site-wide meta description instead of a product-specific one.
• Where: Product template (/products/*), about 1,200 URLs.
• Why it matters: Search results show the same text for every product, so the snippet does not help anyone choose; Google may rewrite it with text from the page instead.
• How to fix: In the product template, set the description from the product summary, trimmed to about 150-160 characters, falling back to the site-wide text only when the summary is empty.
• Owner / effort: Frontend, about 2 hours. Verify: view source on three product pages after deploy.

Five fields, one template, a verification step. The Meta Description check flags this pattern page by page, and every issue in our audit comes with a fix prompt you can paste into a ticket or an AI assistant; the audit also exports to CSV and Jira.

Mistakes That Make Audit Reports Useless

• Exporting instead of reporting. A raw crawl export is an appendix, not a report.
• No priorities. If everything is critical, nothing is.
• Counting URLs instead of templates. It exaggerates effort and hides the real fix.
• Vague fixes. "Improve page speed" is not a task; "serve the hero image at 1200 px in WebP and preload it" is.
• No owner and no date. Findings without owners do not get fixed.
• No baseline. Without a starting measurement, nobody can tell whether the work paid off.

Where the Data Comes From

Fill the template from a mix of sources: Google Search Console for indexing and real-user performance, a crawler for site-wide technical issues, PageSpeed Insights for slow templates, and a page-level audit for your most important pages. Our technical SEO audit guide covers the checks behind sections 5.1-5.4, our comparison of SEO audit tools covers which tool fits which part, and our 99-point SEO audit checklist lists what to check in each area.

Sources

1. Control your snippets in search results - Google Search Central
2. AI features and your website - Google Search Central
3. Generative AI performance report - Google Search Console Help