Website Launch Checklist: Before, During and After Go-Live
Most launch problems are not dramatic. A contact form that sends to an old inbox, a staging setting that tells Google not to index the new site, old URLs that now return errors, or emails that start landing in spam because DNS was changed in a hurry. Each one quietly costs you calls and rankings for weeks before anyone notices. This checklist is organized by phase, before launch, launch day and the first 30 days, so you can work through it with your designer or on your own. Where a free tool can check an item in seconds, we link to it.
Key takeaways
- Check robots.txt and noindex settings on launch day: a staging block left on the live site is the classic launch mistake and can keep you out of Google entirely.
- If you are replacing an old site, map every old URL to its new home with 301 redirects before you switch.
- Test every form, booking flow and click-to-call button on a real phone, and confirm who receives the messages.
- Set up GA4 with key events for calls, forms and bookings, then verify the site in Search Console and submit the sitemap.
- Protect email when DNS changes: keep MX, SPF, DKIM and DMARC records intact and recheck them after launch.
- Take a full backup before and after launch, and keep watching Search Console, forms and speed for the first 30 days.
Why do small business launches go wrong?
Usually because launch is treated as one moment instead of a short project. The design gets approved, someone flips the domain, and everyone moves on. The settings that protect search traffic, email and leads live in places nobody looks at, like robots.txt, DNS records and form notification settings.
The fix is boring and effective: a written checklist, one owner for each item, and a second pass the day after launch. This guide focuses on getting a new or redesigned site live safely, whether you built it yourself or someone built it for you.
Pre-launch checklist: content and conversion
Start with what customers see and do. Proofread on a phone, not only on a large monitor, because that is where most local customers will read it.
- Need a privacy policy? Our free privacy policy generator gives you a starting draft to review.
- Check one form submission end to end: form, inbox, reply. Forms that silently fail are the most expensive launch bug we see.
| Item | What to check | Done when |
|---|---|---|
| Copy | No lorem ipsum, typos or old prices | Every page read on mobile |
| Contact details | Name, address, phone match your Business Profile | Identical everywhere |
| Forms | Submit each form; check inbox and spam | Right person gets every test |
| Booking | Make and cancel a test booking | Confirmation email arrives |
| Calls to action | Click-to-call and WhatsApp work on phones | Tested on iPhone and Android |
| Images | Compressed, real photos, alt text added | No huge files over a few hundred KB |
| Legal pages | Privacy policy, terms, cookie notice if needed | Linked in the footer |
| Favicon | Small icon for tabs and bookmarks | Shows in browser tab |
Pre-launch checklist: technical and SEO
These items protect your rankings and security. Most take minutes, but skipping them can undo months of search visibility.
- Google retired its Mobile-Friendly Test in December 2023, so use PageSpeed Insights or Chrome's Lighthouse plus a real phone.
- Check text contrast with our accessibility contrast checker; low-contrast grey text is the most common accessibility fail on new designs.
| Item | What to check | Done when |
|---|---|---|
| Mobile | Layout, tap targets, no sideways scroll | Works at phone width |
| Speed | Core Web Vitals in PageSpeed Insights | LCP 2.5s or less, INP 200ms or less, CLS 0.1 or less |
| Titles and meta | Unique title and description per page | No duplicates or blanks |
| 301 redirect map | Every old URL points to its new page | Spreadsheet of old to new URLs |
| Schema | LocalBusiness markup with correct NAP | Passes Rich Results Test |
| XML sitemap | Lists live URLs only | Ready to submit |
| Accessibility | Contrast, headings, labels, keyboard use | Basics pass |
| Backup | Full files and database backup | Stored off the server |
How do you handle 301 redirects from the old site?
If you are replacing an existing site, your old pages may have rankings and backlinks. When their URLs change and return a 404 error, that value fades. A 301 redirect tells browsers and Google that the page has moved permanently.
Export your old URLs before launch, from the old sitemap, Search Console's Pages report or a crawl. Map each one to the closest matching new page, not all to the homepage. After launch, test a sample of old URLs to confirm each lands on the right page in a single hop.
Also make sure only one version of the site exists: http should redirect to https, and either www or non-www should redirect to the other.
Launch-day checklist: what to do when you go live
Launch on a quiet weekday morning, not a Friday evening, so problems surface while people are around to fix them.
| Step | Check | Tool |
|---|---|---|
| Remove staging blocks | No noindex tag, robots.txt allows crawling | View source, robots.txt |
| SSL | Padlock on every page, no mixed content | SSL checker |
| Redirects | http to https, www rule, old URLs | Browser test |
| Email DNS | MX, SPF, DKIM, DMARC still correct | Email DNS checker |
| Analytics | GA4 tag firing, key events set | GA4 Realtime |
| Search Console | Property verified, sitemap submitted | Search Console |
| Forms again | One live test of each form | Your inbox |
| Business Profile | Website link points to the new site | Google Business Profile |
Why is the noindex left from staging such a common mistake?
Developers rightly hide staging sites from search engines with a noindex tag, a password, or a robots.txt rule that disallows everything. In WordPress this is often a single checkbox under Reading settings. When the site moves to the live domain, that setting can travel with it.
The result: Google drops pages from its index or never adds them, and nobody notices because the site looks perfect to visitors. On launch day, view the page source and search for noindex, open yoursite/robots.txt and make sure it does not say Disallow followed by a lone slash, and use the URL Inspection tool in Search Console on the homepage.
Are SSL, security and email ready?
Every page should load over https with no browser warnings. Run the live domain through our SSL and security headers checker to confirm the certificate, expiry date and basic security headers.
Email is the quiet casualty of launches. When nameservers or DNS move to a new provider, MX records and the SPF, DKIM and DMARC records that keep your mail out of spam can be lost. Google and Yahoo have required authentication for bulk senders since 2024, and many mailbox providers treat unauthenticated mail with suspicion. Check your records with our email DNS checker before and after the switch.
If you run WordPress, update plugins, remove unused ones and turn on two-factor login before launch. Many hacked sites we recover were compromised through an outdated plugin on a fresh install.
How do you set up analytics and Search Console?
In Google Analytics 4, conversions are now called key events. Mark the actions that matter, such as form submissions, booking completions and clicks on phone links, so you can see which pages produce leads. Our GA4 guide for small businesses walks through it.
In Search Console, verify the domain property, submit your XML sitemap and request indexing for the homepage and key service pages. Then follow the steps in Google Search Console for beginners. Add the site to Bing Webmaster Tools too; it can import from Search Console in a few clicks.
If you use cookies for analytics or ads and serve visitors in regions that require consent, set up a cookie banner before tags fire.
What should you do in the first 30 days after launch?
Launch is the start of the data, not the end of the project. Block short check-ins on your calendar.
- Run a full website health check at the end of week one to catch broken links, missing tags and slow pages.
| When | Task |
|---|---|
| Day 1 | Retest forms, booking, calls; check for 404s |
| Day 2-3 | Confirm GA4 key events are recording |
| Week 1 | Search Console: sitemap read, pages indexed |
| Week 1 | Update Business Profile, social bios, directories |
| Week 2 | Review Core Web Vitals and fix slow pages |
| Week 2 | Fix any crawl errors and broken redirects |
| Week 3 | Ask recent customers for reviews |
| Day 30 | Compare leads to the old site; take a new backup |
How ITCM launches client sites
Our process is demo-first: we build the full website and installable app before you pay anything, so testing happens on a finished product, not on promises. Before go-live we run this same checklist, including real-phone form tests, redirect maps from the old site, staging noindex removal and email DNS checks.
Many of our launches replace a hacked WordPress site or a pile of spreadsheets with a site plus a simple CRM, so we pay extra attention to clean backups and to leads reaching the right person from day one. If you are launching a simple site on a builder yourself, this checklist is enough to do it well on your own.
Launch a finished site first, pay only if happy
Skip the guesswork: ITCM builds your website and installable app free first, with 24/7 online booking, lead management, an admin panel and 3 design options. You see it finished and pay $150 one-time only if you are happy. Anything extra gets a fixed quote before any work begins, and an optional care plan starts from $100/month.
Start on the free website offer page.
Frequently asked questions
- What should be on a website launch checklist?
- Content and contact details, tested forms and booking, mobile layout, speed, SSL and redirects, 301s from old URLs, analytics key events, Search Console and sitemap, noindex and robots.txt checks, legal pages, backups, email DNS and your Business Profile link.
- How do I check my new site is not blocked from Google?
- View the page source and search for noindex, open your robots.txt file and make sure it does not disallow everything, and run the homepage through URL Inspection in Search Console.
- How long does it take Google to index a new website?
- Typically anywhere from a few days to a few weeks. Submitting a sitemap and requesting indexing for key pages in Search Console usually helps.
- Do I need 301 redirects if I am redesigning my site?
- Yes, whenever URLs change. Without them, old links and rankings lead to error pages. Map each old URL to the closest new page.
- Will my email break when I launch a new website?
- It can if DNS or nameservers move and MX, SPF, DKIM or DMARC records are not copied. Check them before and after launch.
- What day is best to launch a website?
- A quiet weekday morning, so the people who can fix problems are available. Avoid Friday evenings and your busiest sales days.
- What should I track after launch?
- Form submissions, bookings and phone clicks as GA4 key events, plus indexing and errors in Search Console, and Core Web Vitals for speed.
Related reading & services
- Technical SEO checklist
- How to move your website to a new host
- Website backup guide
- Free website health check
- Get your website built free — pay $150 only if happy
More in Web & Software
- How to Choose a Web Development Company
- How Often Should You Update Your Website? A Practical Schedule
- Signs You Need a Website Redesign, and When a Fix Is Enough
- Website for a New Small Business: Your First Steps Online
- Custom CRM Development: The Complete Guide to Building a CRM Around Your Business
- Custom Software vs Off-the-Shelf: How to Choose
Free tool
Free Website Health Check
Speed, mobile, SSL, basic SEO and broken links on your homepage — in one report.
Try it freeGet a website + app built for free
We build your website and mobile app first, and you see it finished. If you’re happy, you pay $150 one-time. If you’re not, you pay nothing.
See the $150 offer Free website audit