01 / Reports
An audit report turns crawl data and verified findings into a document that people can read, agree with, and act on. A good report is short at the top, detailed underneath, and organized around decisions rather than around the order of a crawler's tabs.
This lesson covers the structure of an SEO audit report, the executive summary, how to present findings and evidence, visuals, formats, and common reporting mistakes. It builds on the Findings lesson in Site Audits.
1. What an audit report is for
An audit report has three jobs: explain the current state of the site, recommend what to fix and in what order, and create a baseline for measuring progress. Everything in the report should support one of those jobs.
Leadership reads the first page. Managers read the priorities. Developers read the individual findings. Structure the report so each group finds what it needs without reading everything.
2. Report structure
| Section | Contents | Main reader |
|---|---|---|
| Executive summary | Overall state, top risks, top opportunities, expected outcomes | Leadership and clients |
| Scope and method | What was crawled, when, with which settings and data sources | Everyone, for context |
| Health overview | Key metrics and trends compared with the previous audit | Managers |
| Prioritized recommendations | Ordered list of fixes with impact, effort, and owner | Managers and teams |
| Detailed findings | Evidence, root cause, recommendation, acceptance criteria | Developers and content teams |
| Appendix | URL lists, exports, and accepted exceptions | Implementers |
3. Writing the executive summary
The executive summary should fit on one screen. State the overall condition in one sentence, then list the three to five findings that matter most, each with its business impact.
Summary sentence
Lead with what the reader should decide, not with how many warnings exist.
4. Presenting findings
Group findings by theme, such as indexability, site architecture, content, tracking, and AI visibility, then order them by priority within each theme. Each finding should include a short title, affected template, number of URLs, sample URLs, impact, recommendation, and acceptance criteria.
5. Visuals that help
| Visual | Good for |
|---|---|
| Trend line | Health score, indexable URLs, or errors over several audits |
| Stacked bar | Status code distribution by site section |
| Crawl depth chart | How many clicks important pages sit from the homepage |
| Before and after table | Showing a specific fix and its result |
| Annotated screenshot | Showing where an issue appears on the page |
Avoid charts that only restate one number. Each visual should answer a question the reader is likely to ask.
6. Report formats
Document or slide report
Best for kickoff audits and leadership presentations.
Interactive HTML report
Lets readers filter issues and open affected URLs.
Ticket export
Turns findings into tasks in tools such as Linear or Jira.
Dashboard
Shows ongoing KPIs between full audits.
Spreadsheet appendix
Full URL lists for implementers.
SiteAuditLint produces HTML reports and exports and can create Linear tickets or send issue CSVs to Slack.
7. Common report mistakes
Tool dump
Pasting every crawler warning without verification or grouping.
No priorities
All findings presented with equal weight.
Jargon for executives
Technical terms without business meaning.
No baseline
Nothing to measure future progress against.
No owners
Recommendations without a responsible team.
8. Practical exercise: Draft a report outline
Audit report checklist
0 of 9 tasks completed
Key takeaways
- An audit report explains current state, recommends fixes, and sets a baseline.
- Structure the report in layers for leadership, managers, and implementers.
- The executive summary leads with decisions and business impact.
- Group findings by theme and order them by priority.
- Use visuals only when they answer a question.
- Deliver findings in the formats teams actually use.
Knowledge check
Next, learn how to present and agree priorities with stakeholders in the Prioritization lesson.