SEO Audit Template: A Client-Ready Audit Report You Can Fill Out (2026)

Before the structure, the principle: an audit report is not a list of everything wrong with a site. It is a prioritized case for action — a document that tells the reader what to fix, why it matters, what it will take, and what they gain. A report that lists fifty findings with no priorities is noise; a report that identifies the five fixes with the highest impact-to-effort ratio is a plan.

Three rules keep an audit honest:

1. Every finding is a problem with a cost, not an observation. "No schema on product pages" becomes "product pages miss rich-result eligibility; fixing schema is a two-hour job with direct CTR upside."
2. Findings are ranked, not enumerated. Severity, effort, and impact go on every finding.
3. The report ends with a roadmap, not a diagnosis. The reader should close it knowing what happens in the next 30, 60, and 90 days.

The XKnow vault applies one more filter — technical perfectionism is the enemy of a useful audit (Technical Perfectionism). A pragmatic audit fixes what moves rankings and revenue; it does not chase theoretical issues with no business impact.

The page a busy reader reads first — and sometimes the only page they read.

EXECUTIVE SUMMARY
─────────────────────────────────────────────
Site:          [domain]
Audit date:    [date]
Auditor:       [name / tool]
Health score:  [X/100 — see scoring below]

The site is [healthy / broadly sound with fixable gaps / structurally weak].
The three highest-impact opportunities are:

1. [Finding] — [impact in one line]. [effort]
2. [Finding] — [impact in one line]. [effort]
3. [Finding] — [impact in one line]. [effort]

Estimated outcome if all three are fixed:
[what changes — e.g. "indexable pages +40%, key service terms within
reach of page one within 90 days"]

Score honestly. A useful health score weights the layers by impact: indexability and duplication failures cost more than polish items. The vault's checklist covers the layers; this template's scoring weights them (Crawled but Not Indexed).

The audit's context: what the site is trying to rank for, and what the search landscape looks like.

KEYWORD & SERP SNAPSHOT
─────────────────────────────────────────────
Primary keyword clusters (from the keyword map):
  Cluster          | Target page        | Current rank | Opportunity
  ---------------- | ------------------ | ------------ | -----------
  [cluster]        | [/page]            | [#]          | [high/med/low]
  ...              | ...                | ...          | ...

SERP observations for the top clusters:
  - The top ten for [cluster] are [mix of incumbents — e.g. "national
    brands + two thin local pages"]. The weak incumbents make [cluster]
    winnable with [what it takes].
  - Search-intent read: [the format the SERP rewards — guides, lists,
    local pack, video].

Traffic baseline (Search Console, last 90 days):
  Impressions: [n]   Clicks: [n]   CTR: [n]%   Avg position: [n]

The SERP read matters more than the rank numbers: it tells you whether the site is even building the right page type for the intent (SERP Analysis, Search Intent Matching).

The technical findings table — the heart of the audit. Every row is one finding with its ranking axes.

TECHNICAL FINDINGS
─────────────────────────────────────────────
ID  | Finding                              | Sev | Effort | Impact | Status
---- | ------------------------------------ | --- | ------ | ------ | ------
T01 | [e.g. 1,200 URLs crawled but not    | High| 4h     | High   | Open
    | indexed — thin template pages]      |     |        |        |
T02 | [e.g. canonical conflicts on product | Med | 2h     | High   | Open
    | pages]                              |     |        |        |
T03 | [e.g. key content loaded via JS      | High| 8h     | Med    | Open
    | only — invisible to crawler]        |     |        |        |
T04 | [e.g. LCP 4.2s on mobile]           | Med | 6h     | Med    | Open
... | ...                                  | ... | ...    | ...    | ...

Severity key: High = blocks ranking now.  Med = erodes rankings.
               Low = polish.   Effort = engineer/editor hours.

Fill each row from the technical checklist pass (see the full technical audit checklist). The template's value is the discipline of the three axes — a finding without effort and impact estimates cannot be prioritized.

Content-level issues, in the same finding format.

ON-PAGE & CONTENT FINDINGS
─────────────────────────────────────────────
ID  | Finding                              | Sev | Effort | Impact
---- | ------------------------------------ | --- | ------ | ------
C01 | [e.g. two pages target the same     | High| 3h     | High
    | intent — cannibalization]           |     |        |
C02 | [e.g. title tags truncated / not    | Med | 2h     | Med
    | matching intent]                    |     |        |
C03 | [e.g. thin location pages —         | High| 10h    | High
    | city-name-swap templates]           |     |        |
... | ...                                  | ... | ...    | ...

Content links: [which clusters are missing pages / which pages need
depth] — see ⟦On-Page SEO⟧ and ⟦Internal Linking Structure⟧.

The off-page layer — backlink quality, gaps, and opportunities.

LINKS & AUTHORITY FINDINGS
─────────────────────────────────────────────
Domain authority snapshot:
  Referring domains: [n]   Top anchor themes: [...]
  [One or two notable toxic / irrelevant links to disavow or remove]

Link gaps vs top competitors:
  Competitor        | Ref. domains | Gap | Opportunity
  ----------------- | ------------ | --- | -----------
  [competitor]      | [n]          | [n] | [what they have that
  ...               |              |     |  you can earn]

Key finding: [e.g. "competitors earn links from industry roundups and
local press; the site has none — a digital-PR gap, not a volume gap"]
— see ⟦Backlinks⟧ for the gap-analysis method.

The deliverable's payoff — the fix order as a timeline.

30-60-90 DAY ROADMAP
─────────────────────────────────────────────
Next 30 days — indexability & quick wins:
  - [T01] prune/rewrite thin pages blocking indexation
  - [C01] resolve cannibalization (merge or differentiate)
  - Submit key pages for indexing; verify via Search Console

Days 31-60 — architecture & content:
  - [T02] fix canonicals / parameter handling
  - [C03] rebuild thin location pages with unique local proof
  - Publish the highest-opportunity missing cluster page

Days 61-90 — authority & measurement:
  - Launch the [digital PR / link earning] program
  - Re-baseline: rerun the keyword snapshot and compare
  - Report progress against the executive summary's estimates

The roadmap converts the audit from a report into a work plan — which is the entire point of the template. It also sets the review cadence: an audit is a point-in-time picture, and the roadmap should schedule the next one (Technical Perfectionism — audits repeat, perfection does not arrive).

The template structure is the easy half; the discipline is in how you fill it. Three habits separate professional audits from amateur ones:

1. Every finding earns its place. If you cannot state the impact of a finding in one sentence, it is not ready to include. A shorter report with ranked findings beats a long one with noise.
2. Effort estimates are honest. A "fix schema" finding that quietly means "rebuild the product template in three systems" is a 20-hour finding, not a 2-hour one. Mis-scoped effort destroys the roadmap's credibility.
3. The report speaks business, not SEO. The reader does not care about "crawl budget" — they care about "your important pages are not being indexed, which means your content investment is invisible." Translate every technical term into its business cost (Search Intent Matching — the same discipline of translating what people actually want applies to report readers).

A template gives you the shape of an audit. What turns it into a repeatable system is the underlying knowledge: the checklist that catches findings in the first place, the keyword map that says which pages matter, the evidence that says why each fix works, and the industry variations that make an audit specific to a vertical (medical practices, law firms, home services, SaaS each have their own audit emphasis).

The XKnow SEO Vault is a Markdown / Obsidian knowledge system that contains both halves: 460+ interconnected notes covering keyword research, search intent, local SEO, technical SEO, content strategy, E-E-A-T, schema, link building, long-tail SEO, and audits — plus the audit checklists, page frameworks, and research evidence that this template draws on, and industry-specific audit assets.

If you run audits (or want to), the vault is where the full system lives: the checklists to catch findings, the frameworks to present them, and the industry knowledge to make each audit specific — all in Markdown you can adapt and reuse.