Why the last hour before launch matters so much
Most website problems I get called about were avoidable. A contact form that quietly stopped sending emails for three weeks. A homepage still carrying “Lorem ipsum” in the footer. An entire redesign that dropped off Google because the staging site’s “block search engines” setting got carried over to the live server. None of these are hard to catch. They just need someone to slow down and check before the site goes public.
Launch day has a way of creating pressure. The client wants it live, everyone is tired of the project, and there is a temptation to flip the switch and deal with the rest later. That is where the expensive mistakes happen. A short, ordered checklist removes the guesswork. Here is the one we run through for every site we put live.
1. Content and proofreading
Start with the words, because they are the thing your visitors actually read. It sounds obvious, yet placeholder text and broken links slip through on nearly every project I have seen that skipped a proper content pass.
- Read every page out loud, or get someone who did not write it to read it. Fresh eyes catch typos the author’s brain auto-corrects.
- Search the whole site for “lorem”, “placeholder”, “TODO” and the client’s internal notes.
- Check every link, including buttons and footer links. Click them. A link checker tool helps, but manual clicking catches the ones pointing at the wrong page.
- Confirm phone numbers, email addresses and the physical address are correct and consistent everywhere they appear.
- Look at every image. Are any missing, stretched, or still watermarked stock previews?
- Set a proper 404 page that helps people find their way back, rather than dumping them at a dead end.
If the site is replacing an old one, this is also the moment to make sure nothing important was left behind in the migration. Old blog posts and landing pages that still earn traffic need to survive the move.
2. SEO and redirects
This is where launches go badly wrong, and the damage is often invisible until rankings quietly fall off a cliff a fortnight later.
The single most common launch mistake is leaving the “discourage search engines” setting switched on. Check it first, check it twice.
In WordPress that setting lives under Settings, Reading. On a staging site it should be on. On the live site it must be off. Confirm your robots.txt is not blocking anything it should not, and that your sitemap.xml exists and lists your real pages.
If URLs have changed, every old address needs a 301 redirect to its new home. Miss this and you throw away years of accumulated ranking authority. We wrote a full walkthrough on how to plan a website redesign without losing your SEO, and the redirect map is the part people skip most often. Beyond redirects, run through the fundamentals:
- Every page has a unique title tag and meta description.
- One H1 per page, describing what the page is about.
- Canonical tags point to the correct version of each URL.
- Images have descriptive alt text that says what each one shows.
- The SSL certificate is active and every page loads over https with no mixed-content warnings.
For anything more technical, from structured data to crawl settings, our rundown of technical SEO basics every small business site needs is worth a read before you launch rather than after.
3. Speed
A site that looks finished can still be painfully slow. Visitors do not wait around, and Google notices load times too. Before launch, run the homepage and a couple of inner pages through a speed test and act on the obvious wins.
- Compress large images. A 4MB hero photo is the usual culprit. Get it under a few hundred kilobytes without visible quality loss.
- Enable caching and, if you can, a content delivery network.
- Remove plugins and scripts you added during the build but never used.
- Test on a real phone over mobile data, not just your office wifi.
Speed is not a nice-to-have. It affects bounce rate, conversions and rankings all at once, which is why we keep banging on about why website speed matters more than you think. Fixing it before launch is far easier than retrofitting it later.
4. Forms and anything that sends an email
Your contact form is often the only way a lead reaches you. If it fails silently, you lose enquiries and never know it happened. So test it properly.
- Submit a real test enquiry from the live site and confirm the email actually arrives, including checking the spam folder.
- Check the notification goes to the right inbox. On more than one project the form was pointing at a developer’s address, not the client’s.
- Confirm the success message shows after submission so visitors know it worked.
- Test any autoresponder or thank-you email the visitor receives.
- Make sure spam protection is on. You want to filter junk without blocking genuine people.
While you are in there, it is worth sense-checking the form design itself. A few small changes to field count and layout can lift completion rates noticeably, as we cover in our piece on form optimisation.
5. Analytics and tracking
If you launch without tracking in place, you lose the first weeks of data forever and you cannot measure whether the new site is doing its job. Set this up before go-live, not after.
- Confirm your analytics tag is firing on every page. Use the platform’s real-time report and load a page to watch yourself appear.
- Set up conversion tracking for form submissions, phone taps and any other action that matters to the business.
- Verify the site in Google Search Console and submit the sitemap so Google starts crawling the new structure.
- Remove any tracking that was only there for testing, and double-check you are not counting your own visits.
6. Accessibility
An accessible site is easier to use for everyone, and it keeps you on the right side of the law. You do not need a full audit to catch the basics before launch.
- Check colour contrast. Light grey text on a white background is a common failure that also hurts ordinary readers on a sunny day.
- Make sure every image has alt text and every form field has a proper label.
- Try navigating the site with just the keyboard. Can you reach every link and button with the tab key?
- Confirm the page still makes sense at 200% zoom and on a small screen.
- Use clear link text. “Read our pricing guide” beats “click here” for screen reader users and for search engines.
7. Backups and a way back
Take a full backup of the site immediately before you go live, and know how to restore it. If something breaks during launch, you want a clean version to fall back on rather than trying to reverse changes under pressure.
- Back up both the files and the database.
- Store the backup somewhere off the server, not just on it.
- Check that automatic backups are scheduled going forward, so the site stays protected after launch.
- Save login details and hosting access somewhere the business owner can actually find them.
Right after you go live
Launching is not the finish line. Spend twenty minutes checking the live site behaves the way the staging version did.
- Load the homepage in a private browser window so you are not seeing a cached copy.
- Send one more test through the contact form on the live URL.
- Check the site on a phone and a tablet, not only your desktop.
- Look at Search Console over the next few days for crawl errors or coverage warnings.
Then keep an eye on it for the first week. Watch your analytics, check the forms are still delivering, and fix small issues while they are still small.
A checklist is only as good as the person running it
None of this is complicated. It is the discipline of doing it every time, in order, without skipping the boring steps because the site “looks fine”. A site can look perfect and still be blocking Google, dropping form enquiries and loading in eight seconds on a phone.
We handle this process on every project we put live, so nothing gets left to chance on launch day. If you have a launch coming up and want a second pair of eyes before you go public, get in touch and we will happily talk it through.
Frequently asked questions
Leaving the search engine visibility setting switched off. Staging sites are usually set to block Google, and that setting often gets carried over to the live site by accident. The result is a finished website that never appears in search results. Always check this first on launch day, then check it again a few days later.
Yes, if any page addresses have changed. Every old URL should point to its closest new equivalent with a 301 redirect. Skipping this loses the ranking authority those pages built up over the years and leaves visitors hitting dead ends from old links and bookmarks.
Submit a genuine test enquiry from the live site and confirm the email arrives in the right inbox, including checking the spam folder. Do not assume it works because it looks fine. Forms fail silently more often than anything else on a website, and you can lose weeks of enquiries before anyone notices.
Before. If you launch without tracking in place, you permanently lose data from your first weeks live and cannot measure whether the new site performs better than the old one. Set up your analytics tag and conversion tracking, then use the real-time report to confirm it is firing before you go public.
For a small business website, budget an hour or two to work through content, SEO, speed, forms, analytics, accessibility and backups properly. Larger sites need longer. It feels slow when everyone wants the site live, but that time is far cheaper than fixing problems in public after launch.
