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.
- 01Check HTML and selected asset counts
- 02Review failed, truncated or inaccessible resources
- 03Confirm the resolved URL and same-origin boundary
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 blocking or delivery errors when appropriate
- 02Keep comparisons on the same canonical route
- 03Interpret sparse scans more cautiously
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.
- 01Repeat incomplete captures
- 02Compare asset selection and fetch counts
- 03Document target-site changes between scans
Common pitfall
A shortcut to avoid
Reading broad evidence as higher confidence in authorship goes beyond what coverage actually establishes.
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.