Website Launch Checklist: 25 Things to Check Before You Go Live

The last few days before a new site goes live are when small mistakes slip through: a contact form that sends enquiries to an old inbox, a “discourage search engines” box still ticked from development, a placeholder phone number in the footer. None of these are hard to fix. They’re just easy to miss when everyone is focused on how the homepage looks. This website launch checklist groups 25 checks into five areas, so you can work through them with your developer or on your own, and go live knowing the basics are covered.

Content and design checks

  1. Proofread every page. Read the text aloud, or ask someone outside the business to read it. Fresh eyes catch typos you’ve stopped seeing.
  2. Remove all placeholder content. Search for “lorem ipsum”, “sample page”, “example.com”, test products and stock images with watermarks.
  3. Check contact details everywhere. Phone numbers, email addresses, opening hours and addresses appear in headers, footers, contact pages and sometimes schema markup. Make sure they match each other and your Google Business Profile.
  4. Confirm legal pages are in place. A privacy policy is expected in most countries, and you may need a cookie notice, terms and conditions, or returns information depending on what you sell and where.
  5. Check images. Every image should be compressed, sized sensibly and have alt text. Make sure you have the rights to use every photo.

Functionality checks

  1. Test every form. Submit each form with real details. Confirm the message arrives at the right inbox, isn’t landing in spam, and that the visitor sees a thank-you message or page.
  2. Click every link. Menus, buttons, footer links and in-text links. A link checker plugin or tool helps on larger sites, but click the main navigation by hand.
  3. Test on real devices. At least one iPhone, one Android phone, a tablet and a desktop, in more than one browser. Emulators are useful but don’t catch everything.
  4. Check the custom 404 page. Type a made-up address on your domain. Visitors should see a helpful page with navigation, not a blank error.
  5. Test integrations. Newsletter sign-ups reaching your email platform, booking systems syncing with calendars, live chat connecting to the right person, and any payment gateway processing a real low-value transaction you then refund.

If you’re launching an online shop, there’s a longer list of store-specific checks in my e-commerce website checklist, covering shipping, tax and order emails.

SEO items on your website launch checklist

  1. Allow search engines to index the site. In WordPress, go to Settings, then Reading, and make sure “Discourage search engines from indexing this site” is unticked. This is the single most common launch mistake I see.
  2. Check robots.txt. It shouldn’t block important pages or folders that contain your CSS and JavaScript.
  3. Write unique title tags and meta descriptions. Each important page should have its own, describing what’s on it and including the term people would search.
  4. Set up 301 redirects from old URLs. If you’re replacing an existing site, every old page that had traffic or links should redirect to its closest new equivalent. Skipping this can cost you rankings you’ve built up over years.
  5. Generate an XML sitemap and submit it in Google Search Console. Most SEO plugins create one automatically.
  6. Verify Google Search Console for the correct version of your domain. Google’s guide to adding a property walks through the options.
  7. Install analytics and confirm it’s recording visits, ideally with form submissions tracked as conversions.

Launch is a starting point for search engine optimization, not the end of it, but getting these foundations right means you’re not undoing damage later.

Performance and security checks

  1. Install an SSL certificate and make sure every page loads over https, with http requests redirecting automatically. Look out for “mixed content” warnings from images still loading over http.
  2. Test page speed on mobile. Run your main pages through PageSpeed Insights and fix big problems such as oversized images. My guide to Core Web Vitals for business owners explains what the scores mean.
  3. Set up caching through your host or a plugin, and test that forms and logged-in areas still work afterwards.
  4. Configure automatic backups stored somewhere other than the same server, and check you know how to restore one.
  5. Tighten logins. Strong unique passwords, two-factor authentication for admin accounts, and remove any test or developer accounts that are no longer needed. There’s more in my WordPress security checklist.

Ownership and handover checks

  1. Confirm you own the domain. It should be registered in your name or your company’s, with login details you control, and auto-renew switched on.
  2. Collect all access details. Domain registrar, hosting, WordPress admin, email, analytics and Search Console. Store them in a password manager, not a spreadsheet.
  3. Agree what happens after launch. Who updates plugins, who fixes problems, and how quickly? Get any training you need to edit pages yourself.

When to launch (and when to wait)

Avoid launching late on a Friday or right before a holiday. If something goes wrong, you want people available to fix it. Early in the week, at a quiet time for your business, is usually best.

It’s also fine to launch with some non-essential pages still to come. A blog with two good posts is better than a delayed site waiting for ten. What shouldn’t be compromised are the essentials above: working forms, correct contact details, indexing allowed, redirects in place and access in your hands.

For the first week after launch, check your inbox for form submissions, look at analytics daily, and watch Search Console for crawl errors. Most problems show up quickly if you’re looking.

Frequently Asked Questions

How long does it take to work through a website launch checklist?

For a small business site of five to fifteen pages, a thorough run-through usually takes a few hours spread over a day or two. Redirect mapping for a large existing site takes longer.

Will my rankings drop when I launch a new site?

There can be some fluctuation while Google recrawls the site, especially if URLs change. Proper 301 redirects and keeping your valuable content reduce that risk considerably.

Should my developer handle all of this?

A good developer will cover the technical items. You’re still best placed to check content accuracy, contact details and whether forms reach the right people, so plan to share the work.

Need help?

If you’d like someone to run through these checks before your site goes live, or you need a site built from scratch, my website development service covers launch and handover as standard. See examples on my portfolio, then contact me and I’ll reply within 24–48 hours.

Services That Can Help

Estimate Project