Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Read complete journeys from acquisition to support
- 02Verify claims, prices and product names
- 03Check empty, loading and error copy
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Resolve contradictions and placeholder language
- 02Put evidence beside important claims
- 03Assign owners and review dates
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Run comprehension and proofreading passes
- 02Click every content link and action
- 03Compare production metadata with visible copy
Common pitfall
A shortcut to avoid
Reviewing only the homepage leaves product states, forms and support content inconsistent at launch.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.