How to Launch a Website: The Pre-Launch and Launch-Day Checklist

By Christoph Olivier, Founder, CO Consulting

Last reviewed: July 2026

Most launch checklists tell you what to build. This one tells you what to do in the final 48 hours and the launch hour itself: the functional QA, the redirect deployment, the analytics verification, and the DNS cutover sequence that takes a site live without dropping rankings or losing a single lead. If you want the 90-day SEO plan for a brand-new domain, read our SEO checklist for new websites. This page is the go-live operation.

How do you launch a website step by step?

To launch a website, you run four phases in order: functional QA (test every form, link, and mobile layout on a staging copy), technical and SEO checks (SSL, redirects, sitemap, robots.txt, remove staging noindex tags), analytics setup (install and test GA4 events before launch), then the launch-hour cutover (lower DNS TTL, flip DNS, verify, submit sitemaps). Do not touch DNS until the first three phases pass.

The order matters because each phase gates the next. A form that fails QA is a lost lead the moment traffic arrives. A leftover noindex tag from staging silently deindexes the whole site. A missing 301 map hands your old rankings to a wall of 404s. Sequence protects you.

The checklist below is written for a real go-live. It assumes you have a staging environment (a private copy of the site) and, if you are replacing an existing site, a list of every old URL.

Pre-launch checklist: functional QA (2 to 4 weeks out)

Pre-launch QA confirms the site works before anyone sees it. Test every form, button, link, and layout on the staging site across desktop and a real phone on cellular data, not office WiFi. Combable content for typos, placeholder Lorem ipsum, and broken images. Fix everything here, because after cutover every defect is public and costing you conversions.

Start two to four weeks before your target date. Rushing a launch checklist into one afternoon is how you ship a contact form that emails nobody. Work through these:

1. Forms and lead capture. Submit every form. Confirm the notification email arrives, the CRM record is created, and the thank-you or redirect fires. This is the single most expensive thing to get wrong.
2. Links and navigation. Crawl the staging site with a tool like Screaming Frog. Fix every internal 404 and broken outbound link before launch.
3. Mobile rendering. Load the site on a real phone. Check tap targets, menu behavior, and that nothing overflows the viewport. Mobile-first indexing means Google ranks what the phone sees.
4. Content proof. Read every page. Remove placeholder text, fix typos, confirm images have alt text, and check that phone numbers and prices are correct.
5. Cross-browser. Open the key pages in Chrome, Safari, and Firefox. Layout breaks show up browser by browser.
6. Load speed. Run the top templates through PageSpeed Insights. Aim for a Largest Contentful Paint under 2.5 seconds and pages that render in under three seconds; speed affects usability, conversions, and rankings.

Pre-launch checklist: SEO and technical checks

The SEO and technical pass makes the site indexable and safe to crawl the instant it goes live. The three items that break launches most often are leftover staging noindex tags, a missing or wrong 301 redirect map, and an SSL certificate that is not fully installed. Clear those, then confirm sitemap, robots.txt, canonicals, and title tags.

These checks are where new-site owners lose rankings they never had to lose. Run them on staging, then re-run them minutes after cutover.

• Noindex sweep. Staging environments are usually set to noindex so Google ignores them. Templates inherit that tag. Audit every page for a leftover <meta name="robots" content="noindex"> before you launch, and re-check the live site immediately after. This tag alone can deindex an entire launch.
• SSL certificate. Confirm HTTPS is live and that HTTP requests 301 to HTTPS. Most hosts offer one-click SSL; verify it actually applies to the naked domain and the www subdomain.
• robots.txt. Replace any staging Disallow: / with a production robots.txt that allows crawling and points to your sitemap.
• XML sitemap. Generate it, confirm it lists live URLs only, and hold it ready to submit at cutover.
• Canonicals and titles. Confirm each page self-canonicalizes to its live HTTPS URL and that title tags and meta descriptions are unique. Our technical SEO checklist for founders covers the full crawl-and-index pass.
• Schema and analytics tags staged. Confirm structured data validates and that tracking is installed but pointing at production.

How do you launch a website without losing SEO rankings?

To launch without losing rankings, you only have a rankings problem if you are replacing an existing site or changing URLs. In that case, map every old URL to its closest new URL and deploy 301 (not 302) redirects at cutover. A 301 passes ranking signals; a 302 is treated as temporary and passes little. Miss the map and old rankings hit 404s and disappear within weeks.

A brand-new domain with no history cannot lose rankings it does not have, so redirects do not apply. The redirect work below is for relaunches, redesigns, and platform migrations.

Build the map from your old sitemap and Search Console’s list of indexed pages, not from memory. Every URL that ever earned a link or a ranking needs a target. Spot-check 50 redirects after cutover and confirm each returns 301 to the correct page.

Setting up analytics before you launch

Install and test analytics on staging before launch so the first real visitor is counted. Set up Google Analytics 4 with conversion events for form submissions and phone-number clicks, connect Google Search Console for indexing and query data, and add a heatmap tool like Microsoft Clarity. Fire a test event in GA4 DebugView and confirm it lands before you go live.

Analytics installed after launch means you never see your launch-day traffic, and launch day is often your highest-traffic day of the quarter. Set it up now.

1. GA4. Install the tag, then define conversion events for every action that matters: form submit, call click, booking. Test each one in DebugView.
2. Search Console. Verify the property (DNS or HTML method) so it is ready to accept the sitemap at cutover.
3. Behavior tracking. Add a heatmap or session-recording tool to see where launch traffic gets stuck.
4. Consent and legal. Confirm the privacy policy, cookie consent, and terms pages exist and that consent gating fires before tags load where required.

If lead capture is the point of the site, wire tracking into the funnel too. Our conversion rate benchmarks give you a yardstick for whether launch traffic is converting at a healthy rate.

The launch-day sequence: going live in the right order

On launch day you execute a timed cutover, not a single button press. Lower DNS TTL 24 to 48 hours ahead, freeze content, do a final noindex sweep, deploy the redirect map, flip DNS, then verify SSL, redirects, and analytics on the live domain within the first hour. Submit sitemaps to Google and Bing last. Run it in this order so rollback stays fast.

This is the part every other checklist skips. Here is the actual sequence, top to bottom:

1. 48 hours out: lower DNS TTL. Drop the time-to-live on your A and AAAA records to around 300 seconds. This makes the eventual DNS swap propagate in minutes and gives you a fast rollback if something breaks.
2. Launch morning: content freeze. Stop editing. Take a final backup of the current live site so you can roll back cleanly.
3. Final noindex and robots sweep. Re-confirm no page carries a staging noindex and that robots.txt allows crawling.
4. Deploy redirects. Push the .htaccess, Nginx config, or platform redirect map so 301s are live the instant DNS flips.
5. Flip DNS. Point A/AAAA records at the new host. Confirm propagation with dig from more than one location.
6. Verify SSL and HTTPS. Load the live naked domain and www over HTTPS. Confirm no mixed-content warnings.
7. Spot-check redirects. Test 50 old URLs. Each should return 301 to the right new page, not a 404 or a 302.
8. Verify analytics live. Open GA4 DebugView on the production domain, complete a real conversion path, and confirm the event lands within two minutes.
9. Submit sitemaps. Submit the XML sitemap in Google Search Console and Bing Webmaster Tools to trigger crawling.

Do not submit sitemaps before DNS and redirects are verified. You want Google’s crawler to hit a clean, redirecting, indexable site on its first visit.

The first 72 hours after launch

The first 72 hours are where problems surface, so watch, do not walk away. Monitor Search Console Coverage, server logs, and GA4 traffic on the new domain daily; the biggest swings in indexed page count and crawl rate happen in this window. Re-test forms once real traffic flows, and watch for 404 spikes that reveal a redirect you missed.

Set a 72-hour watch list: form submissions landing in the CRM, no unexpected 404s in server logs, indexed-page count moving in the right direction, and Core Web Vitals holding under real traffic. If a relaunch loses rankings, this is where you catch it while the fix is still cheap. From here you move into the ongoing work in our SEO checklist for new websites, and if the site needs to drive pipeline, our growth consulting team can help you turn launch traffic into booked calls. When you are ready for a second set of eyes on the plan, book a consultation.

Frequently asked questions

How long does it take to launch a website?

The technical cutover itself takes under an hour once DNS propagates, but the pre-launch checklist should start two to four weeks ahead. SSL setup, redirect mapping, QA, and analytics testing each need time to test and fix. Rushing the checklist into a single afternoon virtually guarantees you ship a broken form, a leftover noindex tag, or a missing redirect.

What is the difference between pre-launch and launch-day tasks?

Pre-launch tasks happen on a staging copy and can be redone freely: functional QA, SEO checks, and analytics setup. Launch-day tasks are the timed, one-way cutover: lowering DNS TTL, deploying redirects, flipping DNS, and verifying the live site. Pre-launch prevents problems; launch day executes the go-live in an order that keeps rollback fast if something breaks.

Do I need 301 redirects when I launch a website?

Only if you are replacing an existing site or changing URLs. A brand-new domain has no rankings or backlinks to preserve, so no redirects are needed. For a redesign with new URLs or a domain migration, map every old URL to its closest new page and deploy 301s (not 302s) at cutover, or old rankings hit 404s and disappear within weeks.

Should I set up Google Analytics before or after launch?

Before. Install GA4 on staging, define conversion events for forms and call clicks, and test each one in DebugView so the first real visitor is counted. Launch day is often the highest-traffic day of the quarter. If you install analytics afterward, you lose that data permanently and cannot measure whether the launch converted.

How do I make sure Google indexes my new site quickly?

Remove any staging noindex tags, confirm robots.txt allows crawling, and submit your XML sitemap in Google Search Console and Bing Webmaster Tools once DNS and redirects verify. Then watch Coverage over the first 72 hours. A brand-new domain has no crawl history, so submitting the sitemap and earning early links are the fastest ways to prompt indexing.