Article4 Minute Read

The Website Launch Checklist: 25 Things to Check Before Go-Live

25 checks across content, functionality, devices, performance, SEO, security and analytics to run before a new website goes live.

Author

Michael Getu

Last Update

The Website Launch Checklist: 25 Things to Check Before Go-Live

Launch day is when small mistakes become public. A contact form that sends enquiries to a test inbox, a staging site still blocking search engines, a checkout that fails on one browser, a page full of placeholder text that nobody noticed. None of these is hard to prevent. They happen because nobody checked.

This is the checklist we run before any website goes live. Print it, share it, and assign every line to a named person.

Content

  1. No placeholder text or images. Search every page for "lorem ipsum", "TBC", "test" and sample product names.
  2. Spelling and grammar checked by someone who did not write the copy.
  3. Contact details correct everywhere: phone numbers, email addresses, physical addresses and opening hours, including in the footer.
  4. Legal pages in place: privacy policy, cookie policy and terms, reviewed for this site rather than copied from another.
  5. Links work. Run a link checker across the whole site for broken internal and external links.

Functionality

  1. Every form tested end to end: submitted, received by the right inbox or CRM, with an auto-reply if one is expected.
  2. Payments tested with real transactions if the site sells anything, then refunded, including failed card scenarios.
  3. Search, filters and other interactive features tested with real queries, including ones that should return no results.
  4. Third-party integrations confirmed live: booking tools, chat widgets, newsletter sign-ups, CRM connections, with production keys rather than test keys.
  5. Error pages work: a friendly 404 page that returns a real 404 status.

Devices and browsers

  1. Tested on real phones, both iPhone and Android, not only in a desktop browser's mobile view.
  2. Tested in current versions of Chrome, Safari, Firefox and Edge.
  3. Accessible: usable with a keyboard alone, images with alt text, sufficient color contrast, form fields with labels.

Performance

  1. Images optimized and sized for the devices that load them.
  2. Core Web Vitals checked on key pages with a mobile test; aim for the "good" thresholds explained in our technical SEO checklist.
  3. Caching and compression enabled on the server or hosting platform.
  1. The staging noindex is removed. This is the single most common launch mistake. Check robots.txt and the page source of several templates.
  2. Title tags and meta descriptions unique and written for every important page.
  3. XML sitemap generated and submitted to Google Search Console.
  4. Redirects in place from every old URL if this site replaces an existing one, and tested.

Security and infrastructure

  1. HTTPS everywhere, with HTTP and the non-preferred domain variant redirecting to the main address.
  2. Admin accounts reviewed: unused accounts removed, strong passwords, two-factor authentication on, default usernames changed.
  3. Backups scheduled and tested, with at least one restore actually tried before launch.

Analytics and monitoring

  1. Analytics installed and recording, with key conversions such as form submissions and purchases tracked as goals, and cookie consent working as your policy requires.
  2. Uptime monitoring set up, so you hear about an outage before your customers tell you.

Launch day itself

  • Launch early in the week and early in the day, never on a Friday afternoon, so the team is available to fix problems
  • Have a rollback plan: know exactly how to return to the old site if something serious breaks
  • Keep the old site's data for a few weeks, in case something was missed in the migration
  • Tell the people who need to know: customer service, sales and anyone who will hear about problems first

The first two weeks

Most launch problems are discovered by real users in the first days. Watch:

  • Search Console for crawl errors and newly discovered broken links
  • Analytics for unusual drops on key pages or conversion steps
  • Form submissions arriving where they should
  • Feedback from customers and colleagues, collected in one place

Fix critical issues immediately and batch smaller ones into a planned update a week or two after launch.

Plan it from the start

Most of this checklist is cheap to satisfy if it is part of the plan and expensive if it is discovered on launch day. Include it in your project brief, as covered in how to write a website brief, and agree who owns each item before development starts.

Every website delivered by our tech outsourcing team goes through thorough testing across devices before going live, and we stay available after delivery to keep it running properly. You can see some of those launches in our work.