Define the sample before testing

Run a focused technical review without false completeness

Record the website objective, page types and test conditions. Look for blockers first, preserve evidence and explicitly flag questions that cannot be confirmed without a full crawl, private data or longer observation.

Express audit process: define sample, inspect, prioritise and prepare report
Objective and sample → inspection → evidence → prioritised report.

Message for a specialist

“Review one domain on a pre-agreed template sample. Check availability and indexability first, then desktop/mobile, performance, metadata, navigation and the primary action. For every finding provide URL, evidence, impact, priority and next step. List what was not checked and where a full audit is needed. Do not submit a raw tool export as the report.”

What to prepare

  • the website objective and primary visitor action;
  • home, category, product, service, article and other unique templates;
  • a clean browser profile and two viewport widths;
  • a table for URL, evidence, impact, priority and action;
  • test date, region and network conditions.

Step-by-step

  1. Record scope and exclusions: domain, templates, maximum URLs and available data.
  2. Test HTTP/HTTPS and WWW variants, responses, robots.txt and sitemap.
  3. On each template inspect canonical, robots, title, description, h1 and internal navigation.
  4. Open desktop and mobile layouts and check first screen, form and visible breakage.
  5. Run a performance test and retain result URL, conditions and key observations.
  6. Group recurring issues by template and assess impact and confidence.
  7. Write a concise report: critical, important, observation, next step and limitations.

Finding template

Page/template:
Observation:
Evidence:
Business/search impact:
Priority and confidence:
Recommended action:
Post-repair verification:

A screenshot without URL and explanation is insufficient. Validator and crawler exports need to be reduced to cause and scale.

Risks, rollback and next step

The audit itself changes nothing, so no technical rollback is required. The risk is treating a sample as proof for the whole site or repairing a symptom without diagnosis. Make a backup and verification plan before implementation.

Review the report with the quality checklist. Full crawling, Search Console, logs, competitor work and implementation are separate phases. When time is limited, order the express audit.