Post-Migration Website QA
A final crawl and manual review for links, redirects, metadata, forms, assets, accessibility and server behaviour after launch.
Crawl every reachable page
Check status codes, internal links, image requests, CSS/JS assets, canonical tags, title tags and robots directives. Compare the crawl against the migration inventory.
Test redirects separately
Use the old URL list as a test set. Confirm important old URLs issue the intended permanent redirect directly to the final destination without loops or chains.
Test human workflows
Submit forms, use menus on mobile, open downloads, check phone/email links and navigate key journeys. Automated crawling does not validate every interaction.
Review visual regressions
Look for white-on-white text, cropped headings, missing hero images, layout shift and dropdowns that disappear before users can click them.
Recheck speed and accessibility
A migration can improve architecture while introducing oversized images or weak contrast. Run production checks after caching and CDN behaviour are active.
Compare against the pre-migration inventory
QA is strongest when the test set was created before the rebuild. Use the original inventory to verify every keep, merge and redirect decision. This catches orphaned content that a crawl of the new site alone cannot reveal because the missing page is no longer linked anywhere.
Check server-only failures
Inspect the network panel and server logs for 403, 404 and 500 responses that may not be obvious on the page. Fonts, favicons, JSON files, form endpoints and verification assets can fail while the main HTML still appears normal.