Why a launch checklist matters more than you think
Launch day is where small oversights become public embarrassments. A contact form that silently fails, a tracking tag that never fired, a page still blocked from Google, these are easy to miss in the excitement of going live and expensive to discover weeks later when you wonder why the phone is not ringing. A proper website launch checklist turns go-live from a nervous leap into a calm, repeatable routine.
The list below is the one we run at Pro Digital Labs before any site goes live, grouped so you can work through it logically. None of it is glamorous, but it is the difference between a launch that quietly works and one that leaks leads from day one. Print it, tick it off, and keep a copy for the next project.
Content and proofreading checks
Before anything technical, make sure the words and pictures are right. Typos and placeholder text undermine trust faster than almost anything else, and they are entirely within your control. Read every page aloud once; your ear catches errors your eye skips over.
Pay special attention to anything that has to be exactly correct, such as prices, opening hours, phone numbers and the legal business name. A wrong digit in a phone number means a perfectly designed site that nobody can actually reach.
- check_circle1. Proofread every page for typos, grammar and leftover "lorem ipsum" placeholder text
- check_circle2. Check the phone number, email and address are correct and consistent everywhere
- check_circle3. Confirm prices, packages and opening hours are accurate and current
- check_circle4. Replace every placeholder image with the final, properly licensed photography
- check_circle5. Verify the business name, company number and any required legal text are right
SEO and indexing checks
The single most common launch disaster is leaving the site invisible to Google. Many sites are built behind a "discourage search engines" setting so the staging version stays private. Forget to switch it off and your beautiful new site never appears in search, no matter how good it is. This one check is worth triple-checking.
Beyond visibility, get the foundations of search in place on day one so you are not retrofitting them later. Unique titles and descriptions, a working sitemap and clean redirects all help Google understand and trust the new site from the start.
- check_circle6. Remove any "discourage search engines" or noindex setting left over from staging
- check_circle7. Confirm every page has a unique title tag and meta description
- check_circle8. Generate and submit an XML sitemap, and check robots.txt is not blocking key pages
- check_circle9. Set 301 redirects from every old URL to its new equivalent if you are replacing a site
- check_circle10. Verify the canonical domain (www or non-www, http to https) redirects consistently
Speed and performance checks
A slow site frustrates visitors and quietly hurts your rankings. Most speed problems trace back to oversized images, so this is where the biggest quick wins live. Run the site through a tool such as PageSpeed Insights and act on the obvious issues before launch rather than after.
Test on a real phone over mobile data, not just your office wi-fi. The experience of a customer on a train with patchy signal is the experience that actually matters, and it is usually two or three times slower than your desk connection.
- check_circle11. Compress and correctly size all images; serve modern formats such as WebP
- check_circle12. Enable lazy loading for below-the-fold images so the first screen loads fast
- check_circle13. Minify and combine CSS and JavaScript, and remove anything unused
- check_circle14. Test loading speed on a real mobile device over a 4G connection, not just wi-fi
- check_circle15. Confirm caching is switched on so returning visitors load pages instantly
Forms, functionality and conversion paths
Every enquiry form, booking widget and call-to-action button is a place where money can leak out unseen. The classic failure is a contact form that looks like it submits but never delivers the email to anyone. Test each one for real and confirm the message actually lands in the right inbox.
Walk the full journey a customer takes, from landing on the homepage to completing the action you want, and click everything along the way. If you sell online, run a genuine test transaction through to the confirmation screen and receipt email.
- check_circle16. Submit every form and confirm the message arrives in the correct inbox
- check_circle17. Check the thank-you page or confirmation message shows after submission
- check_circle18. Test all buttons, menus and links; fix anything that 404s or goes nowhere
- check_circle19. Run a real test purchase end to end if the site takes payments
- check_circle20. Confirm WhatsApp, click-to-call and map links open correctly on mobile
Analytics, security and the final pre-launch sweep
You cannot improve what you cannot measure, so make sure tracking is live before, not after, your first visitors arrive. Install your analytics, fire a test event and confirm it shows up in real-time reporting. Launching without analytics means the early weeks, often your most informative, are lost forever.
Finally, lock the site down and confirm it looks right everywhere. An SSL certificate is non-negotiable; browsers flag any site without https as "not secure" and visitors flee. Then check the design holds together across the browsers and screen sizes your customers actually use.
- check_circle21. Install analytics, fire a test event and confirm it appears in real-time reporting
- check_circle22. Confirm a valid SSL certificate is active and the whole site loads over https
- check_circle23. Add a favicon, set up custom 404 and check the cookie/privacy notice is present
- check_circle24. Test the layout across Chrome, Safari and Edge, and on small, medium and large screens
- check_circle25. Set up automated backups and confirm you can restore from one if needed
What to do in the first 48 hours after going live
Launch is not the finish line; it is the moment monitoring begins. In the first day or two, keep a close eye on analytics for errors, broken pages and any sudden drop-offs. Submit your sitemap in Google Search Console so indexing starts promptly, and watch the coverage report for pages Google cannot reach.
Ask a few people outside the project to use the site cold and tell you where they get stuck. Fresh eyes catch confusing navigation and unclear wording that the team has become blind to. Treat the first week as a soft-launch shakedown, fixing the small things quickly while traffic is still light.
Keep the checklist; you will use it again
A launch checklist is one of those unglamorous tools that pays for itself on every project. Once you have run through it a few times it becomes second nature, and the panic of "did we remember the redirects?" disappears. Save your version, refine it after each launch, and add anything that bit you last time so it never bites again.
If you are launching with an agency, ask to see their pre-launch process. A good web design partner will already work to a list like this and will happily walk you through it. If they cannot show you one, that tells you something useful about how the rest of the project is likely to go.
Frequently asked questions
What is the most commonly forgotten launch step?expand_more
Removing the setting that hides the site from search engines. Staging sites are deliberately kept private, and that block often survives the move to live. The result is a site Google never indexes. Always confirm search engines are allowed in and submit a sitemap on day one.
Do I really need 301 redirects when replacing an old site?expand_more
Yes, if your URLs are changing. Redirects pass the search authority and any existing rankings from old pages to their new equivalents, and they stop visitors hitting dead ends. Skip them and you can lose months of accumulated ranking overnight, which is far harder to win back than to preserve.
How do I test that my contact form actually works?expand_more
Fill it in and submit it as a real customer would, then check the message lands in the intended inbox, not a spam folder. Test from a phone as well as a desktop. Do this for every form on the site, because one broken form can quietly cost you weeks of enquiries.
Should analytics be installed before or after launch?expand_more
Before. The first weeks after launch are some of the most useful data you will ever get, showing how new visitors behave and where they drop off. Install tracking, fire a test event and confirm it records before you go live, so none of that early insight is lost.
How long does a proper pre-launch check take?expand_more
For a small business site, working methodically through a list like this takes a few hours. On a larger site with e-commerce it can take a day or more. It is time well spent; a problem caught before launch costs minutes, while the same problem found later can cost real custom.