An audit should make the next decision easier.

Start with the pages that matter

Choose a small set of service, contact and high-value information pages. Record what a visitor should be able to understand or do at each one. Use the current website as the starting point, including useful content and functioning paths.

Separate an observation from an explanation

“This URL returns a missing-page response” is an observation. “This is why inquiries declined” is a hypothesis that needs additional evidence. The audit should keep those statements distinct.

Use a reproducible finding

Observed problem

Name the exact URL, date, behavior and supporting source. Include the customer impact rather than only a tool severity label.

Proposed change

Identify the component, responsible person and the smallest change that addresses the finding. Preserve the current accepted state.

Acceptance check

Describe the expected response, visible content, metadata or interaction after the change. Include the routes that share the affected template.

Business interpretation

Review relevant outcomes with a comparable baseline. A passed technical check does not establish a ranking, lead or revenue gain.

An example you can inspect

The website audit example on this site describes its own public-source review and local candidate. It is a concrete implementation record, not a borrowed client case study.