Website Audit Report Example: What a Good One Contains

Most audit report templates are a cover page and a table of contents. What actually makes a report land with a client is structure: who each section is written for, how findings connect to evidence, and what the report admits it cannot claim. This page walks through that structure section by section, with a live generated example you can inspect.

1. The one-page summary, written for the decision-maker

The person who approved the invoice usually reads one page. That page should state: what was reviewed (the exact scope and dates), the overall result with its severity band, the three to five gaps that matter most in priority order, and — explicitly — what was not verified. Leading with the boundary instead of the score is what separates a defensible report from a sales document.

2. The findings section, written for the implementer

The developer who fixes things needs different material: for each finding, the check that produced it, its state (pass, fail, not applicable, unknown), the evidence reference behind it, why it matters operationally, and a concrete next step with a rough effort size. A finding without an evidence reference is an opinion; a finding with one is a work item.

Finding: Meta descriptions missing on 4 of 12 sampled pages
Check: descriptions (metadata, 10 points) — coverage 67
Evidence: evidence.descriptions (per-page rows, observed 2026-07-29)
Why it matters: affects how results render in search; quick to fix
Next step: write descriptions for the 4 pages listed in the rows
Effort: small (under a day)

3. The score — only if it is traceable

A score earns its place when every point can be traced: total → area → individual check → evidence ID → dated observation. The sample report shows this as a check-to-evidence map. If any link in that chain would break, present the finding qualitatively instead — a precise-looking number with an untraceable origin is how reports lose technical readers.

4. Prioritized gaps, ranked by points left on the table

Ranking gaps by their point value gives the client a defensible "fix this first" list without pretending to predict business outcomes. The sample report ranks its gaps this way, largest first, each with its evidence reference attached.

5. The limits section — the part most reports skip

Every honest audit report states what it does not claim: that it is an operational review inside a stated boundary, not a security audit, compliance review, or a prediction of rankings, traffic, or revenue. Clients trust reports more, not less, when the limits are printed in the report itself. The sample report ends with exactly such a block.

Use this structure with your own tools

Nothing above requires buying anything: the structure works in a document you write by hand, and the free 100-point scorecard produces the score, gap ranking, and Markdown export in your browser. For the full client-audit process around the report — scoping, evidence collection, pricing — see the client website audit guide.