What to check before launching a website

Forms, content, mobile journeys and access: a checklist for launch.

A white checklist with blue checks for a website launch

Check the main journeys on real devices, enquiry delivery, content and access. Agree on support and ownership after launch.

01. Walk through the customer journey

Open the site on a phone, find a service and send a test enquiry. Check errors, confirmations and where the data arrives. A button click alone does not mean an enquiry was received.

Check more than a perfectly completed form: leave a field empty, enter an invalid contact and try submitting twice. Confirm that input survives an error and that the result is explained clearly. For a shop, check the basket, payment and order notifications in the agreed test mode. Verify the final result in the receiving system. A success message in the browser is insufficient if the manager never receives the data.

02. Review content and links

Review contact details, service names, language versions and system messages. Ensure the public version has no test materials or links to unfinished pages.

List the pages that must be ready on launch day. Review every language, image, button label and empty-content state. Remove demonstration contacts and unsupported figures, and confirm rights to photos and logos. Policies and data-processing information should reflect how the site actually works; agree their contents with the appropriate specialist. Give editors a short guide to updating content without breaking the structure, including image sizes and the fields needed for each page type.

04. Agree on post-launch support

Hand over access and instructions, define how issues are reported, and agree on updates and backups. Document who owns content, technical changes and enquiry checks.

Assign owners for the domain, hosting, email, analytics and external services. Transfer access through the agreed channel and check recovery arrangements. Record who receives enquiries outside working hours and who handles an outage. A backup is useful alongside a tested restoration procedure. Support terms should explain which issues are covered, how to report them and how new features are estimated after launch. Ownership needs to be operational, not just a list of passwords.

05. Prepare deployment and rollback

Agree the release time, sequence of actions and a short post-switch check. When replacing a live site, decide how new orders or enquiries are handled during migration. Define conditions for stopping the release and a route back to the previous version. Restoring files does not necessarily restore data, so database changes and recovery need their own plan. A launch decision should follow agreed checks rather than simply the completion of visual work.

06. Check the site after launch

Immediately after publishing, repeat the main journey on the real domain and verify enquiry delivery. Then monitor errors, integration failures and user reports. Check analytics separately from the business outcome: a recorded submission event does not replace a delivered request. Performance assessment also needs real-user data. After domain verification, use Search Console to review crawling, indexing and search queries. Publishing a site does not create instant organic traffic; it starts a period of observation and improvement.

A short launch acceptance sheet

CheckEvidence
Form and integrationA test enquiry arrives and is visible to its owner.
Phone and keyboardThe main journey is usable and errors are clear.
Content and URLsTest data is removed; key URLs and redirects are checked.
SearchDomain, sitemap and indexing rules match the launch plan.
Recovery and supportOwners, backup and the support route are agreed.

Sources and further reading