A Website Launch Checklist for UK Business Owners

Set a clear standard for launch readiness

Do not launch until the main customer journeys work, essential content and data checks are complete, your business can control and maintain the site, and someone is ready to monitor it. Before giving the go-ahead, agree what counts as ready and who will check each item. A phase-by-phase checklist helps you record the check, its owner, the evidence to request and whether a failure should block launch.

Start by agreeing the scope: which pages and functions are included, and what visitors most need to do. That might mean finding a service, making an enquiry or completing a booking. Assign each check to your business, the website supplier or a named person at each; do not assume responsibility is understood. Ask for evidence that fits the check, such as a demonstrated journey, a test submission, a confirmed login or a written handover note.

• Scope and ownership: Confirm the agreed pages, key tasks and the person responsible for each check. Evidence: An agreed checklist. Block launch? Yes, if a core task is out of scope or has no owner.
• Core customer journeys: Have the responsible person complete the priority tasks from start to finish. Evidence: A demonstration or recorded test result. Block launch? Yes, if a core task fails.
• Essential content and data handling: Check that important information is present and that submissions reach the intended person or system. Evidence: Content sign-off and a test submission. Block launch? Yes, if missing information or an unmanaged data-handling issue creates a material problem.
• Operational readiness: Confirm who can access and maintain the site, and who will monitor it after publication. Evidence: A confirmed login and handover note. Block launch? Yes, if the business cannot control the site or no one can monitor it.

Keep this review focused on essential readiness, not a full migration, security or conversion review. A small, documented issue may be acceptable if it does not obstruct a core task or leave an operational or data-handling problem unmanaged. Record its owner and follow-up plan rather than treating every imperfection as a launch blocker.

Check the agreed pages and customer journeys

Before approving the agreed pages, check that they give customers accurate information and lead them to the right next step. Review the content yourself, then ask the supplier to demonstrate any journey or interaction you cannot verify from the published pages alone.

• Compare the pages with the approved scope. Check the page list against the agreed requirements and confirm that each page is present, complete and ready for customers. The business owner or nominated content lead should flag missing pages, draft text or material changes from what was approved. Ask the supplier to show where any agreed items sit in the site.
• Verify business details and service information. Check the business name, services, opening details, contact information and locations against the information the business intends customers to rely on. Confirm that booking or enquiry arrangements are described accurately. The person responsible for those details should sign them off; do not assume the supplier can confirm whether they are current.
• Read each page as a customer would. Look for missing or repeated text, inaccurate headings, unsuitable images and links that do not work or lead to the wrong place. Check that calls to action use clear wording and match the next step the business offers. Ask the content owner to record corrections and confirm when they have been made.
• Follow the main customer journeys. Start at a likely entry page and follow the route to an enquiry, booking or other agreed outcome. Try the navigation, relevant links and buttons, including routes between pages. Check that each step leads where expected and that customers are not left at a dead end. Ask the supplier to demonstrate journeys that depend on functionality you cannot assess yourself.
• Try relevant forms and online steps. Using realistic test details agreed with the supplier, submit each form customers will use. Check that required fields are understandable, that a successful submission produces a clear confirmation, and that errors explain what needs correcting. Confirm with the supplier where submissions are sent and who is responsible for receiving them. Agree how to test without sending test messages to real customers or disrupting normal work.
• Check recovery routes. Deliberately leave a required field blank or enter information in the wrong format. Confirm that the customer can see what needs fixing and can correct it without losing their progress, where applicable. Make sure there is a clear way to contact the business if an online step cannot be completed.
• Record sign-off and evidence. Name the person who owns content approval and keep a short record of checks, outstanding corrections and decisions. For interactions you cannot verify independently, ask the supplier for a live demonstration or a recorded test result. Resolve inaccurate core information or a broken route to the intended enquiry or booking before treating that journey as ready.

Test the site on relevant devices and browsers

Check the website on the screens and browsers your customers are expected to use, focusing on the journeys that matter to the business. Agree the test devices and browsers with your supplier rather than trying to test every possible combination.

• Try a phone and a larger screen. Open the key pages and complete the main journey, such as finding a service and sending an enquiry or booking. Check that text is readable, menus and buttons are easy to use, and routine tasks do not require awkward zooming or sideways scrolling.
• Check the agreed browsers and devices. Ask your supplier which combinations they have checked and why those are relevant to your audience. On each, look for anything that changes the journey: a menu that will not open, a button hidden below other content, or a form that is difficult to complete. Record the device, browser and page or step where an issue occurs.
• Use the site without a mouse. Move through menus, forms and any booking steps with the keyboard. Check that you can reach the controls in a sensible order, activate them, and always see which item currently has focus. Ask the supplier to demonstrate any checks that require specialist tools.
• Check visual clarity and images. Look for text and controls that are hard to distinguish from their backgrounds. Confirm that images carrying useful information have text alternatives, and that these alternatives convey the information a visitor needs rather than simply describing decoration.
• Agree an accessibility target. Choose an appropriate accessibility standard as a target for the work, not as a complete answer to which legal obligations apply to your organisation; check that separately with an appropriate adviser if needed. Ask the supplier to explain what they tested and to show the results or remaining issues.
• Record problems in context. For each issue, note the page or journey, device and browser, what you expected to happen and what happened instead. Ask the supplier to explain whether it prevents a core task or can be logged for follow-up, and agree who will resolve it.

A short, evidenced check of the agreed journeys is more useful than a general assurance that the site works on mobile. Keep the findings with the launch decision so the business can distinguish a genuine obstacle from a cosmetic difference.

Check forms, privacy information and tracking

Before launch, account for every place the site collects personal information and every technology that stores information on, or accesses information from, a visitor’s device. Ask the person responsible for privacy and data handling to check that the site’s explanations and controls match what it actually does.

• Map each collection point. Include contact, enquiry, booking, account and payment-related forms, as well as any other route that asks visitors for personal information. Suggested owner: business owner or the person responsible for handling enquiries. Evidence: a list of forms showing what each collects, where submissions go, who can access them and who follows up. Launch impact: treat a form that loses submissions or sends them to an unmonitored place as a blocker for that journey.
• Check the privacy information at the point of collection. Suggested owner: the person responsible for privacy and data handling, with the business confirming the actual process. Evidence: the relevant page or notice, checked against what the business does with submissions. Do not assume that a generic policy reflects the site’s actual handling. If the information is missing or does not match, resolve it or obtain appropriate advice before relying on that collection point.
• Identify cookies and similar technologies. Ask the supplier to list what the site uses, including analytics or other tracking, what each is for and which service or feature uses it. Suggested owner: the supplier identifies what is installed; the business decides which purposes it needs and who maintains the choices. Evidence: a demonstration of the controls, including what happens when a visitor accepts, rejects or changes a preference.
• Verify operation and ownership. Ask the supplier to demonstrate the site’s forms and any consent or preference controls, then confirm who will review changes when forms, tracking or service providers change. Launch impact: pause the affected feature if the business cannot establish where personal information goes, whether the controls behave as intended, or who is responsible for maintaining them.

This checklist is not legal advice. For questions about how current requirements apply to the business, check official ICO guidance or speak to an appropriate adviser.

Confirm access, responsibilities and handover

Before publication, confirm that the business can access the services the website depends on and knows who will look after it. Ask the supplier to demonstrate the relevant tasks and record any gaps, rather than treating a handover promise as proof that the arrangements work.

• Access to essential accounts. The business owner or nominated administrator should check access to the domain account, hosting and website administration, plus any other services needed to run the site. Ask the supplier to show where each account is managed and confirm that the business can sign in. Missing access to a service needed to operate the site may be a launch blocker; record any non-essential access still to be transferred.
• People and permissions. Agree who needs access and what each person is responsible for. Ask the supplier to show how users or permissions are managed, or explain who can make changes if the business cannot do this itself. The evidence should be a successful demonstration or clear instructions that the nominated person can follow. Avoid leaving essential access with only someone who will not be responsible after handover.
• Routine content changes. The person expected to maintain pages should make a typical update, such as correcting a service detail, using the agreed process. Ask the supplier to demonstrate the steps and provide concise instructions. If the business will ask the supplier to make changes, record how requests are raised, approved and handled instead. Block launch if an essential update cannot be made by the agreed route.
• Maintenance and problems. Name the person or supplier responsible for technical maintenance and the person who receives reports from staff or customers. Record how to report a problem, what support is included in the agreed arrangement and what is outside it. Ask for the agreed process for backups and restoring the site to be explained; this is an operational handover check, not a full security audit.
• Third-party services and renewals. List the external services the site relies on, such as those used for forms, payments or email, where applicable. For each, record who controls the account, who receives renewal notices and who can resolve access problems. Ask for the list to be checked against the finished site so an account is not overlooked.
• Handover record. Keep the access route, update instructions, support responsibilities and problem-reporting process in a place the right people can find. Credentials should be managed through the agreed secure method, not copied into a general handover document. If an essential account, responsibility or recovery process remains unclear, resolve it before sign-off; log lesser documentation improvements for follow-up.

Use the evidence to make a go/no-go decision

Use the evidence from the checks to decide whether the site is ready for its intended use, not whether every minor issue has disappeared. For each item, record who checked it, what evidence they reviewed, its status and who will handle any follow-up.

Go: the agreed scope is present, essential details are correct, key journeys work, data-handling checks are resolved and the business has the access needed to operate the site. Keep lower-impact issues in a follow-up list with an owner and an agreed next step.

No-go: pause if a core enquiry or booking journey is broken, essential contact details are wrong, data handling remains unresolved or the business cannot access or operate the site. Ask the supplier to demonstrate a critical fix or provide other suitable evidence; a verbal assurance alone may not let you verify it.

Set the bar in proportion to the site’s purpose and agreed scope. A simple service website does not need the same checks as a complex platform, but its essential customer journeys and operational arrangements still need to work.

Monitor key journeys after publication

Once the site is published, repeat the checks that matter most to customers and the business. Treat this as a focused operational pass: confirm key journeys work, and make sure problems have a clear route to resolution.

• Revisit key pages and journeys. The business owner or relevant service lead should open the main pages and complete the important enquiry, booking or purchase journey as a customer would. Record whether the expected page or next step appears.
• Check form delivery. The person responsible for enquiries should submit a test through each important form, then confirm the message reaches the intended inbox or system. Check that the customer-facing confirmation is clear and behaves as agreed. If messages are missing or confirmations fail, assign the issue to the supplier or internal owner responsible for the form.
• Name a problem monitor. Choose a person to review incoming reports and the usual customer contact channels, such as the business’s enquiry inbox or phone line. Make sure colleagues know where to send website issues and who will decide what happens next.
• Record problems so they can be reproduced. The person receiving a report should note the page, device, browser, steps taken, what was expected and what happened instead. Where useful, include a screenshot without exposing customer or other sensitive information. Assign an owner and record the agreed next action.
• Prioritise by impact. The business owner and issue owner should consider whether the problem prevents a customer from completing an important task, gives misleading information or disrupts an internal process. Resolve issues with significant customer or operational impact first; log lower-impact defects for follow-up with an owner.

Keep this pass focused on whether the site works as intended. If it reveals a need for a broader migration, security or conversion review, agree that as separate work rather than letting it obscure the immediate fixes.

Choose a proportionate website solution

Choose the smallest change that meets the business need. A new custom website is not automatically the right answer; compare the work required with the journeys customers need to complete and the way your business will maintain the site.

• Review the current site: List the pages, enquiry routes and other customer journeys that must work. If the existing platform can support them, ask whether a focused update would resolve the gaps without replacing the site.
• Consider an established platform or website builder: These may suit straightforward content and enquiry needs. Check that the required pages and journeys can be delivered, and that your business can manage updates and access after handover.
• Identify where the current setup falls short: A new or substantially rebuilt site may be appropriate if required customer journeys, integrations or day-to-day operating needs cannot be met properly. Describe the specific gap before deciding what to commission.
• Plan for ownership and upkeep: Decide who will control the site, make content changes and arrange ongoing maintenance. Include these responsibilities when comparing a limited update, an established platform and a rebuild.

If you have decided that a new or substantially rebuilt website is needed, Request a website quote as an optional next step. If the need is narrower, ask your current supplier about a focused update first.