Website Launch Checklist: What to Confirm Before Going Live

A website can look finished before it is ready. The pages may be designed, the copy may be approved and the homepage may feel polished, yet the site can still fail at launch because forms are not tested, analytics is missing, redirects are forgotten, mobile layouts have issues or nobody knows who controls the domain. Launch is the moment when a design project becomes a public business asset.

A launch checklist protects the business from avoidable problems. It does not need to be complicated, but it should be disciplined. A new website should be checked from the visitor side, the business side and the search side. The visitor needs a clear and working experience. The business needs enquiries, access and ownership. Search engines need clean structure, redirects and indexable pages.

This guide works for new websites and redesigns. If the project is a rebuild, combine this with the website redesign checklist so useful old pages, traffic and proof are protected before the new version replaces them.

Before technical launch checks begin, confirm that the website contains the agreed pages and that those pages are final enough to publish. This includes homepage, service pages, about, contact, pricing guidance, legal pages, case studies, guides, landing pages and any support pages needed for the launch version. Missing pages should be clearly marked as phase two, not discovered by accident after launch.

Review content for accuracy. Service names, phone numbers, email addresses, staff names, office locations, pricing notes, timelines, testimonials, client logos and policies should be current. Placeholder text, old page titles, test images and draft sections should be removed. If the business has multiple approvers, one person should confirm final publishing approval.

Content should also match the website goal. A site built for leads should not launch with thin service pages and a weak contact path. A site built for trust should not launch without proof. A site built for support should not launch without practical customer information.

Forms should be tested like business-critical systems. Submit the contact form, quote form, newsletter form, booking form and support form if they exist. Confirm that submissions reach the right inbox or CRM, that the thank-you message appears, that auto-replies are correct and that spam protection does not block real users.

Test phone links, WhatsApp links, email links, map links and social links on mobile. If the website depends on calls or WhatsApp, those links should be easy to tap and should use the correct number. If a form asks for budget, timeline or service type, confirm that the business actually receives those details.

The contact page design guide explains this more deeply, but the launch rule is simple: no site should go live until the business has tested how a real enquiry is created and received.

• Submit every important form from desktop and mobile.
• Confirm notifications, auto-replies and thank-you pages.
• Test phone, WhatsApp, email and map links.
• Check spam protection and file upload behavior where used.
• Confirm who responds to each enquiry type after launch.

Many websites are approved on desktop but used on mobile. Before launch, review important pages on real phones. Check the homepage, service pages, contact page, landing pages and any page that receives campaign traffic. Text should be readable, buttons should be easy to tap, menus should work and forms should be comfortable to complete.

Speed checks should focus on priority pages, not only the homepage. Large images, maps, video embeds, chat widgets and unnecessary scripts can slow the site. If the website is built on WordPress, review plugins and image handling before launch. A slow launch can make a new site feel weak immediately.

Test on common browsers and devices where possible. You do not need to chase every rare edge case, but the main visitor experience should be stable across modern Chrome, Safari and mobile browsers.

SEO checks are especially important for redesigns, but new websites need them too. Page titles, meta descriptions, headings, canonical URLs, image alt text, internal links and indexability should be reviewed before launch. Search engines should be able to crawl the pages meant to rank.

If the website replaces an old site, map old URLs to new URLs. Important pages should not disappear without redirects. Old blog posts, service pages, pricing pages and pages with backlinks may still carry value. A beautiful redesign can lose traffic if URL changes are handled carelessly.

Submit or update the sitemap after launch and check robots settings. If the site was blocked during development, remove the block before launch. This sounds obvious, but it is a common launch mistake.

Launch checks should include the small trust details that visitors notice when they are deciding whether a business is real. Company name, registration references where used, office address, service area, phone numbers, email addresses, social links, team details, testimonials and client logos should be accurate. If the website uses awards, certifications, association badges or partner logos, confirm that the business is allowed to show them and that the images are current.

Privacy and policy pages also need attention. A contact form, quote form, booking form, newsletter form or ecommerce checkout collects information, so visitors should be able to understand how their details are handled. The policy does not need to interrupt the experience, but it should be present, accessible and written for the actual website instead of copied blindly from another business.

If the site includes ecommerce, memberships, downloads, recruitment forms or customer portals, test the related notices and consent points before launch. A website built for trust should not create doubt through missing policies, outdated legal pages or unclear data handling.

A launch can involve the designer, developer, hosting provider, domain owner, marketing lead, business owner and sometimes an IT person. Before launch day, decide who does what. Who changes DNS? Who checks SSL? Who tests forms? Who watches analytics? Who approves the final site? Who tells the team that the new site is live?

A fallback plan is not pessimism. It is professional. If something goes wrong, the team should know whether to pause the launch, restore the old site, disable a feature, fix a redirect or contact hosting. The most stressful launches are not the ones with problems; they are the ones where nobody knows who owns the problem.

For larger redesigns, prepare a launch window when the right people are available. Avoid launching late on a Friday if nobody will monitor forms, indexing, payments or hosting over the weekend. A good website maintenance arrangement starts immediately after launch, not months later when small issues have already affected customers.

A business website should not launch blind. GA4, Search Console, conversion events and form tracking should be installed before the site is promoted. Track quote submissions, contact submissions, phone clicks, WhatsApp clicks, booking actions and checkout actions where relevant. Without measurement, improvement becomes guesswork.

Ownership should also be clear. The business should know who controls the domain, hosting, CMS, analytics, Search Console, email routing, backups and maintenance. If a supplier holds everything without proper access, the business is exposed later.

After launch, monitor forms, speed, indexing, redirects and errors for at least the first few weeks. Launch is not a finish line. It is the beginning of real-world feedback. The best websites stabilize quickly because someone is watching.

The first month should also include improvement notes. Which pages are people visiting? Which forms are being used? Which enquiries are low quality? Which questions keep coming through phone calls? Those signals should feed future updates to copy, page structure and landing pages. Launch gives the website a public starting point; measurement turns it into a living business asset.

Keep a simple launch log with the date, DNS changes, analytics checks, redirect notes, known issues and fixes completed. It gives the team a shared record and makes future troubleshooting, reporting and accountability easier.