Website Launch Checklist: Everything to Do Before (and Right After) You Go Live

Launching a Website Without a Checklist Is a Gamble You Will Lose

Picture a business owner who launches their new site on a Friday afternoon. The design is sharp. The copy is polished. Everyone's excited. By Monday morning, the calls start: Google Analytics isn't firing, the contact form is silently swallowing every submission, and every old URL is returning a 404. The site looks exactly right. Almost nothing actually works. A proper website launch checklist is the difference between a site that works from day one and one that quietly fails while looking great. This post walks through every critical step, in order, including the exact 27-point QA pass the Sproutbox team runs before any site goes live.

Step 1: Audit Your Content and Copy Before Anything Else

This step gets skipped because it feels obvious. Which is exactly why it bites people. Before you touch a single technical setting, every visible element on the site needs a human eye on it, not a preview window on staging, but a real pass through the live-ready build.

• Unique, descriptive title tags on every page. No 'Home | Home' duplicates. Every page title should reflect what that specific page is about.
• Meta descriptions under 160 characters, with the page's target keyword. These show up in search results. Write them like ad copy, not afterthoughts.
• Zero placeholder text. 'Lorem ipsum,' 'TBD,' and 'DRAFT' have no business being anywhere on a live site. Check every page, every section, every modal.
• Descriptive alt text on every image. Both for accessibility and for search engines that can't see images the way humans do.
• A CTA audit on every key page. Are the calls-to-action present? Do they point to the right destination? A CTA that links to a 404 is worse than no CTA at all.
• Legal pages live and linked in the footer. Privacy policy, terms of service, cookie notice if your site collects data. These aren't optional.

Step 2: Lock Down Your Technical SEO Foundation

This is the step most business owners hand to their developer and assume is handled. Sometimes it is. Often, it isn't, because staging environments have different settings than production, and flipping a site live without a technical walkthrough is how critical configuration errors survive into launch day.

1. SSL certificate is active. The URL shows https://, not http://. If your browser shows a 'Not Secure' warning, your visitors will leave before they read a word.
2. The robots.txt file is not blocking search engines. This is the single most common staging-to-live error we see. Developers set robots.txt to block crawlers on staging so Google doesn't index half-built pages, then forget to flip it before launch. One missed setting, and you've cost yourself weeks of indexing time.
3. An XML sitemap exists and is accessible at /sitemap.xml. Confirm it loads and lists your actual pages, not staging URLs.
4. 301 redirects are mapped for every old URL. If this is a redesign, every old page needs to forward to its new equivalent. Not to the homepage. Not to a 404. To the right page.
5. Canonical tags are set correctly. No duplicate content between www and non-www versions of your domain. Pick one and canonicalize everything to it.
6. Schema markup is present on key pages. LocalBusiness, Service, and FAQ schema all help search engines understand who you are and what you do. They're not glamorous, but they matter.

The robots.txt issue deserves more than a bullet point. We've audited sites that were live for three weeks with crawlers completely blocked, the owners had no idea why their pages weren't appearing in Google. That single error can reset months of SEO momentum. Check it before you launch. Then check it again. For a deeper look at how web design and SEO work together from the build stage forward, that post covers the technical overlap in detail.

Step 3: Test Performance, Mobile, and Cross-Browser Experience

Run the site through Google PageSpeed Insights before launch and aim for a mobile score above 70 and a desktop score above 85. The most common culprits pulling scores down are uncompressed images, render-blocking scripts, and unoptimized fonts. Fix these first, they have the biggest impact and the clearest solutions.

For mobile, view every page on an actual phone. Not a browser emulator. An actual device in your hand. Check that forms are tappable without zooming, nav menus open and close correctly, and no content is clipped or overflowing at the edges. Mobile responsiveness isn't just about the layout shrinking down, it's about whether the experience actually works for a human thumb.

Cross-browser testing means Chrome, Safari, Firefox, and Edge at minimum. Safari on iOS trips up more sites than any other browser, especially with CSS animations and video autoplay. Use BrowserStack or a real Apple device for this, DevTools in Chrome does not accurately replicate Safari behavior, and that gap has burned more than a few launches.

Step 4: Verify All Tracking, Forms, and Conversion Paths

This is the step where launches fail silently. The site looks fine. Traffic is coming in. But you have no data, no leads, and no idea. These errors are the most costly precisely because there's no alarm, nothing breaks visibly.

1. Google Analytics 4 is installed and firing. Open the site in a browser, then check GA4 Realtime. A session should appear within 30 seconds. If it doesn't, something is wrong with the installation.
2. Google Search Console is connected to the live domain, not the staging domain. Submit the XML sitemap from within GSC so Google knows where to start crawling.
3. Every form has been tested end-to-end. Fill it out. Submit it. Confirm the notification email arrives at the right address, with the right content. Do this for every form on the site, contact, quote request, newsletter signup, all of them.
4. Conversion events are triggering correctly. If you have a 'Thank You' page or event-based conversion set up, verify it fires in GA4 or your ads platform before the site goes live.
5. Ad pixels are installed and verified. Meta Pixel, Google Ads tag, use the relevant browser extension (Meta Pixel Helper, Google Tag Assistant) to confirm they're firing on the right pages.

What we've learned after building hundreds of sites is that tracking errors are almost always discovered too late. A client comes to us two weeks post-launch asking why leads have been quiet. We check the form. It's been erroring silently since day one. The leads weren't quiet, they were lost. A ten-minute verification pass before launch would have caught it.

Step 5: Run the Sproutbox 27-Point Pre-Launch QA Pass

Sproutbox is a Portland-based full-service digital marketing agency specializing in website design, development, and the full marketing stack that supports growth after launch. The Sproutbox 27-Point Pre-Launch QA Pass is the internal checklist our web team runs on every site before handing it to a client. This checklist is baked into our web design process from the first kickoff call, not added at the end as a formality.

CONTENT

1. Unique title tags on every page
2. Meta descriptions on every page, under 160 characters
3. No placeholder text anywhere on the site
4. All images have descriptive alt text
5. All CTAs point to correct URLs
6. Legal pages are live and linked in the footer
7. 404 page is custom-designed and on-brand

TECHNICAL

1. SSL certificate active, site loading on https://
2. robots.txt confirmed allowing search engine crawlers
3. XML sitemap accessible at /sitemap.xml and submitted to Google Search Console
4. 301 redirects mapped for all legacy URLs
5. Canonical tags set correctly, www vs. non-www resolved
6. No broken internal links (full crawl completed)
7. Schema markup present on key pages

PERFORMANCE

1. Mobile PageSpeed score at or above 70
2. Desktop PageSpeed score at or above 85
3. Images compressed and served in WebP where supported
4. Fonts optimized, no excessive render-blocking
5. No console errors on any page
6. Video files are not self-hosted on the server

TRACKING & CONVERSION

1. GA4 firing and confirmed in Realtime
2. Google Search Console connected to live domain
3. All forms tested end-to-end
4. Conversion events verified in GA4 or ads platform
5. Ad pixels confirmed via browser extension
6. Email notifications routing to the correct inbox
7. CMS walkthrough recorded and delivered for client handoff

If even one item in the Tracking & Conversion group is unchecked, do not launch. The rest of the site can be perfect, and those four items can make the launch effectively invisible.

Step 6: Plan Your Launch Day, and the First 30 Days After

Most checklists end at go-live. This one doesn't, because the first 30 days are when you actually learn whether the site works, not just whether it loads.

Launch day: Don't launch on a Friday afternoon. We know this sounds simple, but it's the scenario from the intro, and it happens constantly. Launch mid-week when your team is available to catch issues within hours, not days. Immediately after DNS propagates, run a full crawl with Screaming Frog or Ahrefs to catch redirect errors or missing pages before Google does.

First 7 days: Check GA4 daily. You're looking for traffic anomalies, 404 spikes, and unexpected form drop-offs. Check the Coverage report in Google Search Console three to four days after launch for any crawl errors that surfaced during initial indexing.

First 30 days: Monitor Core Web Vitals in GSC. Watch for ranking shifts on your key pages, especially if this is a redesign, some volatility is normal, but a sharp drop on a previously strong page needs attention. Run a heatmap tool like Hotjar or Microsoft Clarity to see where real users are clicking, scrolling, and dropping off. What you see will surprise you.

One practical tip: set up a GSC email alert for any spike in 404 errors. It takes two minutes. It has saved us from more than a few quiet disasters on sites we've supported post-launch. And honestly, that's the whole point of a post-launch plan, catching the things you didn't know to look for.

Frequently Asked Questions

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

For a small business site under 15 pages, a thorough pre-launch QA pass takes 3 to 5 hours when done carefully. For larger sites with complex 301 redirects or custom functionality, budget a full day. Rushing this process is the single most common reason sites go live with broken tracking or missing redirects, and those problems rarely announce themselves right away.

What happens if I skip the pre-launch checklist and launch anyway?

The most common outcomes are invisible. GA4 setup is missed so you have no traffic data, forms error silently so leads disappear without a trace, and old URLs return 404s so any SEO equity from your previous site is gone. Most of these issues are fixable, but they cost time, rankings, and in some cases real revenue while you're tracking them down. A pre-launch website checklist exists specifically to make these problems impossible to miss.

A Checklist Doesn't Replace a Team Who's Done This Before

A website launch checklist works when someone actually runs it, line by line, on a real device, with real data flowing through real forms. Most launches fail not because the site is bad but because the last 10% of QA gets skipped under deadline pressure. The common advice is to hand your developer a list and trust it gets done. In practice, without a dedicated QA owner, the most important items are the first to fall through the cracks.

If you're planning a redesign or building something new, we're happy to talk through what a launch-ready process looks like for your business. We've seen too many great-looking sites go live broken. That's exactly why this checklist exists.