Use these steps as a working checklist and adapt them to the project’s evidence, scope, and constraints.
Practical steps
- Create a route table with page type, locale, owner, intended index state, and preferred canonical URL.
- For each route, define observable acceptance checks: expected HTTP status, title, one primary heading, canonical, robots rules, and language links where used.
- Require the rendered page to expose its main text and metadata in the response HTML; list exceptions that need client rendering and how they will be verified.
- Define behavior for redirects, sitemap inclusion, forms, keyboard use, mobile layout, and a genuine 404 response.
- Attach a test URL and evidence for each requirement; assign a reviewer and a pass/fail result instead of “looks good”.