Why launch QA fails without a checklist
Launches concentrate risk: new URLs, redirects, content migrations, third-party scripts, and last-minute design changes. A structured QA checklist prevents “we will fix it after launch” from becoming the default process.
1) Links and redirects
Confirm primary navigation, footer, CTAs, and sitemap destinations resolve. Collapse redirect chains and verify old marketing URLs still land correctly.
- Crawl for broken internal and external links
- Validate redirect map from the previous site or staging URLs
- Check key campaign landing pages linked from ads and email
2) SEO foundations
Titles, meta descriptions, canonicals, robots directives, and heading structure should be intentional on every key template. Staging noindex leftovers are a classic launch defect.
3) Accessibility smoke test
Keyboard navigation, form labels, contrast on primary CTAs, and meaningful image alternatives should be checked on homepage, forms, and conversion pages. Use the accessibility checker and WCAG checker for a broader pass.
4) Performance and security basics
Review heavy homepage modules, third-party scripts, and caching on critical templates. Confirm HTTPS, security headers posture, and cookie/consent behavior on production domains.
5) Final go/no-go scan
Run one full pre-launch website quality scan, assign owners to P0 issues, and re-scan after fixes. Keep the sample-style report handy for stakeholders with our sample report page.