Technical SEO
SEO Audit Evidence Checklist
A reusable checklist for collecting evidence before prioritizing SEO audit findings across technical, content, local, authority, and measurement work.
SEO audit findings need evidence before they need recommendations. This checklist helps separate confirmed issues from guesses, tool noise, and low-priority best-practice warnings.
Use it before scoring impact, confidence, effort, and risk.
Download the working file: SEO audit evidence checklist CSV.
Evidence table
| Field | What To Record |
|---|---|
| Finding | Short description of the issue. |
| Page group | Template, section, location, category, product set, or guide cluster. |
| Sample URLs | A small representative set of affected URLs. |
| Evidence source | Crawl, GSC, analytics, rendered HTML, log sample, SERP, GBP, backlink tool, or manual check. |
| User impact | How this affects discovery, trust, choice, or conversion. |
| Search impact | How this affects crawl, indexation, relevance, authority, local visibility, or snippets. |
| Business impact | Leads, revenue, calls, bookings, support cost, or strategic visibility. |
| Confidence | How strong the evidence is. |
| Owner | Engineering, content, local ops, design, leadership, or SEO. |
| First action | The smallest useful next step. |
| Validation method | How the team will confirm the fix worked. |
Evidence by audit lane
| Lane | Strong Evidence |
|---|---|
| Crawlability | Status codes, robots rules, crawl exports, internal links, sitemap data. |
| Indexability | URL Inspection samples, noindex, canonicals, duplicate clusters, indexed URL patterns. |
| Rendering | Raw HTML, rendered HTML, screenshots, JavaScript errors, missing links or content. |
| Intent | SERP page types, query modifiers, competing pages, searcher task analysis. |
| Content quality | Freshness, examples, proof, source clarity, author context, useful depth. |
| Internal links | Link exports, orphan reports, anchor text, hub-to-detail paths. |
| Local SEO | GBP fields, citations, reviews, local page proof, local actions. |
| Authority | Relevant links, mentions, reviews, partner pages, PR coverage, source quality. |
| Measurement | GSC trends, analytics, conversion data, CRM notes, annotations. |
Weak evidence to avoid
- “The tool says this is an issue” with no affected page examples.
- Ranking screenshots without date, location, device, or query context.
- Word count comparisons without search intent analysis.
- Domain metrics without source relevance.
- One Search Console observation treated as a trend.
- A recommendation without an owner or validation method.
Priority-ready finding
A finding is ready to prioritize when it has:
- Affected page group.
- Representative URLs.
- Clear evidence.
- A likely cause.
- A recommended fix.
- An owner.
- A validation method.
- A reason the business should care.
If those fields are missing, keep investigating before adding the issue to a stakeholder action plan.