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.
- 01Inventory current DNS records and TTLs
- 02Confirm canonical host and redirect plan
- 03Review certificate and email records
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.
- 01Lower TTL before planned migration when useful
- 02Stage certificates and redirects
- 03Keep previous configuration recoverable
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.
- 01Resolve from multiple networks
- 02Test apex, www, IPv4 and IPv6 paths
- 03Verify HTTPS, email authentication and monitoring
Common pitfall
A shortcut to avoid
Changing many unrelated DNS records during launch makes rollback and failure diagnosis unnecessarily difficult.
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.