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.
- 01Identify the intended customer and urgent job
- 02Compare headline promises with product behavior
- 03List reasons to choose this solution now
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.
- 01Lead with the concrete outcome
- 02Explain the distinctive mechanism
- 03Support the claim with a product artifact or proof
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 interviews
- 02Test message recall after a short visit
- 03Check sales and support language for alignment
Common pitfall
A shortcut to avoid
Trying to include every feature in one statement usually removes the central reason to care.
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.