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.
- 01Review which features raise the model output
- 02Check whether direct builder markers were observed
- 03Count actionable findings separately
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.
- 01Improve concrete security and quality issues
- 02Review high-influence patterns for product distinctiveness
- 03Preserve familiar behavior that helps usability
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 a before-and-after comparison
- 02Confirm changes affect delivered HTML or assets
- 03Check that usability and performance did not regress
Common pitfall
A shortcut to avoid
Inventing dozens of fixes to match a high number confuses model similarity with an issue count.
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.