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 code, configuration, schema and content changes
- 02Define measurable rollback triggers
- 03Review compatibility with existing data and clients
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.
- 01Keep the previous deploy and configuration available
- 02Make database changes backward compatible
- 03Assign authority and communication steps
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.
- 01Rehearse rollback in a safe environment
- 02Time the procedure and verify state
- 03Test forward recovery after rollback
Common pitfall
A shortcut to avoid
A platform rollback button cannot undo destructive data migrations or external side effects.
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.