Website launch checklist: what to verify before release
A practical acceptance sequence for journeys, forms, mobile layouts, search access, analytics and recovery before a public launch.
ecomvision editorial team
2 min
Published
Updated
Key takeaways
- 01Test the built release with realistic configuration.
- 02A submit click does not prove enquiry delivery.
- 03Prepare a working rollback before switching.
Start with the main journey
Arrive through the home page, a search landing page and a case link. Check the offer and contact route, then repeat on a phone and with a keyboard.
Try long headings, empty lists and slow connectivity. Real data often exposes issues that a standard mockup misses.
Follow the enquiry to its destination
An agreed test should reach the actual mailbox, CRM or work channel. Verify contact details, context, errors and duplicate handling.
Separate form starts, button presses and confirmed delivery in analytics. Mark the test enquiry so it does not distort sales reporting.
Check search access
Canonical pages need direct access and readable HTML. Verify titles, descriptions, H1, language, sitemap and robots rules. Map moved content to direct redirects.
Missing pages must return an appropriate status instead of a successful placeholder. Check service routes and parameter variants separately.
- Core pages return 200.
- Missing pages return 404 or 410.
- Canonical and language targets exist.
- Public images require no authentication.
Plan the switch and observation
Preserve the previous build and required data, assign the switch owner and define recovery. Rollback must remain compatible with any data changes.
After publishing, verify public HTTPS, forms, images and analytics again. Watch errors and enquiry quality. Launch concludes a delivery stage, not the responsibility to operate the site.