01Start with the business question
An audit for a new launch differs from an investigation into a traffic drop. Record the important services or products, recent changes, target audience and known problems. Ask which pages should generate enquiries and which provide supporting information. This keeps the review connected to the business rather than a tool’s total warning count.
Access to Search Console and analytics can improve the diagnosis. A public-only review should state what it could establish and which questions remain open. Missing access is not evidence that a hidden system is broken.
02Cover content and technical foundations
Review crawl access, indexing directives, canonical URLs, redirects, sitemaps and important internal links. Inspect shared templates and mobile journeys. Examine whether commercial pages explain the offer, whether articles fulfil their titles and whether evidence supports factual claims.
Check the distinction between a confirmed error and a recommendation. A 404 for an intentionally retired page is not the same as a broken menu link. A long title is a readability question, not a universal character-limit violation.
03Make the report actionable
For each material finding, provide the affected URL, observed evidence, likely impact, a recommended action and a close-out test. Identify whether the work belongs to content, development, hosting or the business owner. Keep uncertain interpretations separate from confirmed defects.
A prioritised report should make trade-offs easier. Correct index-blocking mistakes and failed enquiry paths before spending time on cosmetic suggestions. Where several pages share the same defect, explain the template-level change rather than presenting hundreds of duplicate tasks.