Website delivery

Website launch checklist: checks before and after go-live

A practical website launch checklist covering forms, content, accessibility, search settings, rollback and the first checks on the live domain.

Turn the checklist into a release record

Use this website launch checklist when the site is ready for final testing, whether it is a new build or a replacement. Record the release version, planned time, decision-maker and people available to help. Beside every check, leave room for a result, evidence and any outstanding issue.

Agree which failures stop the launch. A missing decorative image and an enquiry form that loses messages should not have the same priority. Write down who can accept a remaining issue, its workaround and the date it will be reviewed. Do not turn an unresolved problem into a tick simply because a deadline is close.

Freeze the version being tested. If copy, configuration or code changes afterwards, repeat the affected checks. Make sure the person approving the release knows which version the evidence describes and where to find it.

Check the journeys customers actually use

Start from the pages a visitor is likely to enter, not only the homepage. Follow the route to an enquiry, booking or purchase, where those features exist. Check buttons, telephone links, downloads and any external service that forms part of the journey.

Submit a clearly labelled test enquiry and confirm it arrives in the intended inbox or system. Check both the visitor's confirmation and the staff notification. Try missing required fields, an invalid address and a failed connection. Error messages should help someone recover without losing information unnecessarily.

For accounts or payments, use the provider's approved test process before launch and agree any production verification separately. Confirm test credentials and test-mode settings will not be left in the public journey. Never use a real customer's information to create a convenient test case.

Review the final content and access

Read contact details, service descriptions, prices and opening information on the release version. Remove placeholder copy and unapproved testimonials. Confirm downloads are the intended editions. Check that policy links lead to the correct documents, with an appropriate owner responsible for their accuracy.

Use a keyboard to move through navigation and forms. Check that focus is visible and that labels explain inputs. Review image alternatives and try enlarged text. W3C warns that its preliminary checks cover only some accessibility issues; these launch checks do not certify accessibility or legal compliance.

Test important layouts on representative phones and browsers. Check that menus can close, banners do not obscure actions and long error messages remain readable. Record a device or browser-specific failure precisely so the developer can reproduce it.

Verify the production setup

Ask the technical owner to check the live domain, HTTPS, intended canonical addresses and search visibility settings. A staging restriction must not accidentally prevent public pages from being indexed. Private areas must retain their access controls; making a site public does not mean making every route discoverable.

For changed URLs, test the agreed redirect map and update internal links. Google's site-move guidance covers monitoring old and new URLs and checking migration settings. A functioning redirect is not a promise that search positions will remain unchanged.

Check analytics against the agreed measurement and privacy configuration. A dashboard receiving events does not prove those events represent useful enquiries. Document what counts as success, exclude clearly labelled internal tests where practical, and check that the team can interpret the results.

Make recovery possible before switching over

Confirm the recovery route for this particular site. A static deployment may need the previous build restored; a transactional application may also need to reconcile records created since release. Ask who can perform recovery and what information could be lost or duplicated.

Keep the previous working version and required configuration available to the authorised team. Agree a contact route for urgent faults and a temporary customer message if the service becomes unavailable. Do not assume that the person who built the site will be available without an agreed support arrangement.

Repeat critical checks on the live domain

Immediately after release, repeat the main customer journey, destination inbox check and key redirect tests. Confirm monitoring reaches the responsible person. Watch for issues that did not appear on staging, such as domain configuration, external integrations or notification delivery.

Schedule a follow-up review of enquiries, errors and user feedback. GOV.UK's live-phase guidance treats ongoing support and improvement as part of running a service. For your own site, give those responsibilities named owners and an agreed review routine. Close the launch record only when the handover is complete and remaining issues are visible.

Website launch checklist: copyable release record

Copy this record for the release being tested. A tick means the check has evidence, not simply that somebody intends to do it. Use not applicable with a reason for features the site does not have.

Release: [version]. Live domain: [address]. Planned launch: [date and time]. Release owner: [name]. Technical contact: [name]. Decision-maker: [name]. Recovery instructions: [location].

Check record: [journey or setting]. Owner: [name]. Tested version and environment: [details]. Result: [pass / fail / not applicable]. Evidence: [location]. Outstanding issue and user impact: [details]. Retest required: [yes / no].

Before launch: [ ] Main visitor journeys tested. [ ] Test enquiry received by the intended team. [ ] Errors and recovery checked. [ ] Content approved. [ ] Accessibility checks recorded. [ ] Representative devices checked. [ ] Domain and search settings checked. [ ] Redirects tested where relevant. [ ] Recovery route confirmed.

Go/no-go decision: [launch / hold]. Decision-maker and time: [details]. Accepted remaining issues: [issue, owner, workaround and review date]. Rollback trigger: [specific failure]. Person authorised to act: [name].

After launch: [ ] Critical journey repeated on the live domain. [ ] Notifications received. [ ] Key redirects rechecked. [ ] Monitoring contact confirmed. [ ] Remaining issues handed over. Follow-up review: [date and owner].

Further reading

Big idea. Small first step.

What could work
better for your business?

Tell us where you want to go. We’ll help you work out how to get there.

Let’s talk about it