Skip to content
All articles
Web DesignWebsite LaunchPublished · Updated · 5 min read

Website Launch Checklist: What Gets Missed Before Go-Live

Oblix Digital

Oblix Digital

Web design & SEO

Low angle view of a lamp-lit laptop screen showing a website launch checklist on a dark desk.

Most website launches do not fail because of anything dramatic. They fail quietly: a redirect that was never set up, a contact form that stops sending, an analytics tag pasted into the wrong template. Nobody notices for weeks, sometimes months.

I've launched a lot of sites over the years, and the same handful of things get missed. These are the checks that matter before a site goes live.

Sort your redirects first, not after

If you are replacing an existing website, every page that ranks on Google has a URL in its index. Change the address without a 301 redirect and that page effectively disappears. Visitors hit a 404, and so does Google, which eventually drops the page from its results.

Before launch, export a list of your current URLs (a crawler such as Screaming Frog will do this in minutes) and map each one to its new home. It is tedious, and skipping it is a common reason a rebuilt site loses traffic in its first month.

Once the redirects are live, leave them in place. Google recommends keeping them for as long as possible, generally at least a year. Even with everything mapped, Google says any big change to a site can cause rankings to move up and down while it recrawls your pages, so keep an eye on Search Console rather than panicking in the first week.

Set up analytics before launch, not after

This one comes up often: a business launches, shares the link with everyone it knows, and only adds analytics two weeks later. That first fortnight of data, arguably some of the most useful you will get, is gone.

Install and test tracking on a staging version of the site before it goes live, and check that form submissions register as events. A setup that looks right in the code but never records a real event is worse than no analytics at all, because it gives you false confidence.

Test the things people will do

Not just whether the homepage loads. Fill in the contact form yourself, on your phone, on a slow connection if you can. Click every link in the footer. Try to book, buy or enquire exactly as a stranger would, with no knowledge of how the site is built.

Things that are easy to miss

  • Phone numbers that are not clickable on mobile
  • Forms that submit but never email anyone
  • A favicon still set to the default placeholder
  • Broken links in a half-written blog post nobody finished

Keep the test site out of Google

Blocking a test site in robots.txt, the file that tells search engine bots where not to go, won't keep its pages out of Google's results. Google's advice is to use a noindex tag or put the site behind a password instead, and remember to take the noindex off when the site goes live.

A privacy policy is not optional if you collect any personal data, including through a basic contact form. It does not need to be complicated, but it must exist and be accurate about what you do with people's details.

Cookies need the same care. Under PECR, anything that isn't strictly necessary needs the visitor's consent before it's set, and for advertising, such as an ad or tracking pixel, the ICO says none of the exceptions apply. The Data (Use and Access) Act 2025 added an exception for some simple analytics, which the ICO's April 2026 guidance explains, but it only applies if you tell visitors clearly what you collect and give them a simple, free way to say no. Check what your site sets before deciding whether you need a banner.

Speed still decides who stays

A well-designed site that takes six seconds to load on a phone will lose visitors before they see any of it. Compress images before uploading rather than relying on the CMS, and be cautious with background video, which can make an otherwise well-built site feel slow.

Tell Google you exist

Submit your sitemap through Google Search Console on launch day. It's a five-minute job and helps Google find your new pages sooner.

None of this is glamorous, but it separates a smooth launch from a month spent fixing things that should have been caught before anyone saw the site. If you would like someone to run through this list for you, get in touch. It's a same-day job.

Sources

Frequently asked questions

How long before launch should I start testing?

At least a week, ideally two. That leaves time to fix anything broken without rushing, and to test properly on several mobile devices, not only the one on your desk.

Do I need a cookie banner if I don't run any ads?

Possibly. Tracking and advertising cookies need consent. Some simple analytics may now be exempt under the ICO's April 2026 guidance, but there are conditions, so check what your site sets or take advice.

What happens to my old pages when I switch to a new website?

Without redirects, they return a 404 and any rankings or links pointing at them are wasted. A 301 redirect from every old URL to its new equivalent passes that value across and keeps existing links working.

Can I launch without a fully finished blog or portfolio section?

Yes, in most cases. A half-empty section looks worse than none, so it is better to launch with the core pages complete and add the rest once there is real content for it.

Was this helpful?

Share this article

Found this useful? Let's talk about yours.

Tell me about your project and I'll come back with an honest recommendation, timeline and cost, with no obligation.

Start a project