Organise a website launch around checks that matter
A launch checklist should help the team decide whether the website is ready for real visitors. It is more useful when each item has an owner and visible evidence than when it is a long list of vague promises such as “check everything.”
Group checks by visitor task
Start with the journeys people need to complete: finding a service, understanding the company, choosing a language and making contact. List the pages and interactions supporting each journey. Review actual content, not placeholder text, and include a phone-sized screen in the checks.
Separate a launch blocker from a later improvement. A broken enquiry route prevents an essential task; a decorative detail may be suitable for the next iteration. Agree this distinction before pressure rises on launch day.
Prepare ownership and recovery
Name who approves the content, who changes hosting files and who confirms that messages arrive. Keep a protected copy of the previous working version and document how the responsible person would restore it if needed. Verify access before the scheduled change rather than discovering missing credentials during the launch.
Keep credentials out of the shared checklist. Reference the approved access method instead of copying secrets into a document that many reviewers can open.
- Confirm the production domain, contact details and language links.
- Submit test enquiries and inspect the receiving inbox.
- Review important pages for broken links and missing images.
- Record the release version, responsible person and test evidence.
Repeat the essential checks after publication
A staging test does not prove that the production environment behaves identically. After publishing, repeat the enquiry journey on the real domain and check several key pages from a fresh browser session.
For example, a form can look correct while the live hosting configuration prevents delivery. Treat that as a blocker, fix the cause and repeat the relevant test. Avoid marking every item complete simply because the homepage loads. Record remaining minor issues with owners and planned review dates.
Take it into your working day
A reliable launch has clear acceptance checks, a named decision-maker and a practical recovery route. Publication is the beginning of live verification, not its replacement.