Establish a baseline
Before rebuilding, record the approved URLs, page titles, canonical tags, navigation and representative screenshots. Include mobile views, long content and unusual templates. Keep private or customer data out of comparison artifacts.
Check the generated output
Crawl the authorized build for broken internal links and missing assets. Compare the old and new URL inventories, then document intentional removals and redirects. Check titles, descriptions, canonical URLs, social metadata, sitemap entries and indexing directives.
Test behavior as well as appearance
Use a keyboard to navigate menus and forms. Check visible focus, form labels, error messages and reduced-motion behavior. Review mobile overflow and zoom. Automated accessibility checks help find issues, but do not replace manual review.
Exercise the integrations
With permission, send a clearly labeled test submission through each form and verify receipt. Check spam controls, success states and failure states. Review external search, booking and payment flows with the account owner; do not create real charges as a casual test.
Release with an exit route
Agree on acceptance criteria and unresolved differences before deployment. Keep the previous release and DNS configuration available for rollback. After switching traffic, verify HTTPS, key redirects, forms and public indexing behavior. Delivery evidence should describe checks actually performed, with failures visible.