Website Audit Report Example and Free Template

A website audit report should show what was checked, what the evidence showed, what changed and how another person can verify the result. This page gives you a completed owned-site example and a blank template you can adapt for a client or internal review.

Compare the worked example with the public AuditWeb self-audit. The example covers AuditWeb’s own site and contains no client information or private measurement data.

What is in this website audit report example?

This example contains an executive summary, method and exclusions, three dated findings, a prioritised action plan and follow-up limits. It shows the evidence format rather than pretending that one small review covers every SEO or security question.

The worked scope is the public AuditWeb site review recorded on 5 September 2026. It compared public responses with the Astro source at revision da343a2 and checked the free audit page, the template page, an arbitrary missing URL, build output and available downloads. The 11 September 2026 date on this page records content modification. It is not a blanket test date for every item.

A client version should name the domain, URL sample, systems reviewed, evidence period, reviewer and status. Keep confidential source material in the client’s controlled workspace.

What did the executive summary record?

The 5 September self-audit recorded three concrete defects: a simulated scanner, missing promised downloads and missing URLs that returned homepage HTML with a 200 response.

The first action was to replace simulation with a checker that reads supplied HTML. The second was to publish the files that the resource page actually describes. The third was to add a dedicated 404 document and verify the response after release. No traffic, ranking or revenue improvement was claimed.

This is the useful shape of an executive summary: state the observation, name the affected route, give the first correction and identify what remains unmeasured. Avoid invented sample rankings, forecast traffic or generic “comprehensive” claims.

What technical findings were recorded?

The technical section used the same fields for every issue: affected URL, dated evidence, consequence, correction, status and a reproducible verification step.

1. F–01: The scanner generated simulated results

   Affected URL

   /free-website-audit/

   Evidence recorded 5 September 2026

   The old source called simulateAudit and used a seeded random calculation instead of inspecting a submitted page.

   Consequence

   A visitor could receive a convincing result that did not come from the page submitted.

   Correction

   Replace the simulation with the HTML checker in src/lib/html-audit.js. State that it reads pasted HTML only.

   Status and owner

   Resolved. Live checker cases were re-run on 11 September 2026. Owner: product and engineering.

   Verification

   Live checks covered input-dependent findings, canonical resolution, export and clear behaviour, inert pasted markup, duplicate metadata, noindex and untested images. These checks verify the documented checker cases and do not certify the wider site.

2. F–02: The download page had no promised files

   Affected URL

   /website-audit-checklist/template/

   Evidence recorded 5 September 2026

   The page promised Excel and PDF files but supplied no working file links. The public asset folder had no template at the time.

   Consequence

   Visitors could read about a resource but could not obtain the promised deliverable.

   Correction

   Publish the 50-check PDF and editable Markdown toolkit. Remove the unsupported Excel promise. Add the direct Markdown report-template path.

   Status and owner

   Resolved. Existing PDF and ZIP download responses passed live signature checks on 11 September 2026. Owner: content and engineering.

   Verification

   Live checks confirmed the existing PDF and ZIP routes and signatures. Earlier evidence inspected the PDF contents and toolkit files. This report does not claim that the PDF was reopened on 11 September.

3. F–03: Missing URLs returned homepage HTML

   Affected URL

   /codex-growth-missing-20260905/. Historical probes also included /.env and /.git/config.

   Evidence recorded 5 September 2026

   The missing path returned homepage HTML with status 200. The additional probes also returned homepage HTML. No credentials were observed in the returned body.

   Consequence

   Monitoring and crawlers could not reliably distinguish an existing page from a missing route.

   Correction

   Add a dedicated 404 document and verify the hosting layer’s final response code. A repository 404 file alone does not prove the deployed response.

   Status and owner

   Resolved. The missing-path response returned 404 in the live check on 11 September 2026. Owner: engineering and hosting.

   Verification

   Live check requested a genuinely missing route and confirmed the 404 response and page marker. Recheck after future hosting changes.

The replacement checker makes narrower claims than the old product copy. It parses supplied markup in an inert template and reports title, meta description, canonical, indexing directives, H1, image alt and viewport observations. It does not fetch a site or measure speed, SSL or Google indexing. That boundary belongs in the report and beside the tool.

What did the content and evidence review cover?

The content review checked whether public pages described the implemented product and whether promised resources existed. It did not score client content or private measurement data.

The report therefore records a content correction rather than a ranking diagnosis. The resource page now points to actual Markdown files and the toolkit page describes the supplied PDF and editable documents. A client report can add a page inventory with keep, refresh, consolidate or remove decisions when the source data supports those decisions.

Read the free HTML checker scope before reusing the method. A pasted-HTML observation is evidence about the supplied markup. It is not proof that a live page is indexable or accessible to every user.

What competitive evidence was available?

No competitor crawl, backlink comparison or SERP benchmark belongs in this completed example because none was part of the documented 5 September scope.

A client report can add competitive evidence when it names the comparison set, date, source and selection rule. Keep that section separate from owned-site findings. Do not turn an unrun comparison into a claim about market position.

What action plan followed the findings?

The action plan follows evidence and verification order: correct the misleading checker, publish the promised files and confirm that missing routes return 404 responses.

1. Immediate: keep the HTML checker’s scope beside its input and verify a known noindex and missing-alt example.
2. Short term: check both Markdown downloads after deployment. Confirm content type, non-empty body and the expected headings.
3. Release follow-up: request a new missing path and confirm status 404 with a page-not-found body. Review sensitive-path probes as part of hosting hardening.
4. Measurement: compare later observations using the same URLs and definitions. Treat download events or enquiries as usage signals rather than proof of business outcome.

Assign each action to a role and attach the evidence needed to close it. A status such as “resolved and verified” requires the recorded check. “Correction prepared” describes source or local work that still needs a production check.

How should you use the website audit report template?

Start with the scope and exclusions. Then write one finding per issue and finish each finding with an observable verification step.

For a client audit, replace the bracketed prompts with the client domain, exact URLs, evidence dates, tools and access limits. Add only measurements you can reproduce. Link to stable public sources where possible and keep confidential exports outside the public report.

Use the completed example as a format reference. Use the agency toolkit when you also need a prioritisation worksheet, client questionnaire or implementation tracker. Use the professional audit service page for scope and commercial details.

What questions does this report example answer?

What is a website audit report?

A website audit report records the scope, evidence, findings, fixes and verification steps for a website review. A useful report separates observed facts from impact estimates and untested areas.

What should each audit finding contain?

Each finding should name the affected URL, dated evidence, reproduction steps, consequence, recommended fix, owner, status and an observable verification method.

Is this a client audit report?

No. This worked example covers AuditWeb’s own site. It is an owned-site case study with public evidence and no private client or Search Console data.