Website Launch SEO Checklist

A website launch checklist for SEO: what to check before go-live, on launch day, in Search Console and Bing, and for speed and tracking afterwards.

Runs in your browser — nothing you enter is uploaded Free · no sign-up
0 of 20 done

Your progress is saved in this browser only.

Before launch

  • Why & how

    Why: Indexed staging sites create duplicate content and leak unfinished work.

    How: Use HTTP authentication rather than robots.txt alone.

  • Why & how

    Why: Templates often ship with the same default title on all pages.

    How: Crawl staging and fix missing or duplicate titles and descriptions.

    Use the Duplicate Title & Meta Description Checker →

  • Why & how

    Why: Page-builder themes often misuse heading tags for styling.

    How: Review the heading tree on each template.

    Use the H1 & Heading Structure Checker →

  • Why & how

    Why: This helps Google show your preferred site name and understand your brand.

    How: Set name, alternateName, url, logo and sameAs.

    Use the WebSite Schema Generator →

  • Why & how

    Why: Google shows favicons next to results; a missing one looks unprofessional.

    How: Use a square icon, a multiple of 48 px, at a stable crawlable URL.

  • Why & how

    Why: Launch announcements on WhatsApp, LinkedIn and X depend on good previews.

    How: Check og:title, og:image and og:url on key pages.

    Use the Open Graph & Social Preview Checker →

Go-live

  • Why & how

    Why: Leftover staging blocks keep a new site out of search entirely.

    How: Check robots.txt and meta robots on every template after go-live.

    Use the Indexability Checker →

  • Why & how

    Why: Duplicate versions split signals from day one.

    How: Test http/https and www/non-www variants.

    Use the HTTPS, WWW & Trailing Slash Checker →

  • Why & how

    Why: Old URLs may have links and bookmarks worth keeping.

    How: Map previous URLs to new ones and implement 301s.

    Use the Redirect Mapping Tool (Site Migration) →

  • Why & how

    Why: A good 404 keeps users on site; a 200 status creates soft 404s.

    How: Request a fake URL and check status and design.

    Use the Soft 404 Checker →

  • Why & how

    Why: Security warnings stop visitors; headers protect against common attacks.

    How: Confirm certificate validity and add HSTS and other key headers.

    Use the Security Headers Checker →

Search engines & sitemaps

  • Why & how

    Why: It helps search engines discover all pages on a new site.

    How: Include only canonical 200 URLs and add a Sitemap line to robots.txt.

    Use the XML Sitemap Generator →

  • Why & how

    Why: Search Console reports indexing problems and lets you request indexing.

    How: Use a Domain property verified by DNS to cover all protocols and subdomains.

  • Why & how

    Why: Bing powers several search and AI experiences; setup takes minutes.

    How: Import from Search Console or verify separately, then submit the sitemap.

  • Why & how

    Why: It can speed up initial discovery of the most important URLs.

    How: Use URL Inspection on your top pages after launch.

Performance & tracking

  • Why & how

    Why: New sites often ship with heavy images, fonts and scripts.

    How: Run lab tests now; field data appears once enough real users visit.

    Use the Page Speed Test →

  • Why & how

    Why: Uncompressed uploads are the most common cause of slow new sites.

    How: Convert to WebP or AVIF and serve responsive sizes.

    Use the Image Compressor →

  • Why & how

    Why: Launch-day data creates the baseline for future decisions.

    How: Test forms, calls and purchases in DebugView.

    Use the GA4 Event Builder & Naming Checker →

  • Why & how

    Why: Broken forms waste the launch traffic you worked to get.

    How: Submit each form and confirm the notification arrives and is not in spam.

    Use the SPF, DKIM & DMARC Checker →

  • Why & how

    Why: Placeholder and staging links often survive into production.

    How: Crawl the live site and fix all 4xx links.

    Use the Broken Link Checker →

About the Website Launch SEO Checklist

A new site can be beautiful and still invisible to search if it launches with a leftover noindex, no sitemap or broken forms. This website launch checklist covers four stages: before launch, go-live, search engines and sitemaps, and performance with tracking.

It is useful for agencies handing over client sites and for owners launching their first site. Items link to tools that check indexability, HTTPS and www consolidation, soft 404s, security headers and broken links, and generate sitemaps and WebSite schema. Share the exported Markdown with your developer so nothing is assumed. If you are replacing an existing site, use this list alongside the website migration checklist. Progress stays in your browser.

How to use it

  1. Work through the before-launch section on staging.
  2. Run the go-live checks within an hour of launch.
  3. Verify Search Console and Bing and submit sitemaps.
  4. Test speed, tracking and every form on the live site.

Frequently asked questions

How long does it take for a new website to show in Google?

It varies from a few days to several weeks. Submitting an XML sitemap in Search Console, requesting indexing for key pages and earning a few links from established sites can speed up discovery. Indexing is not guaranteed, so focus on useful, crawlable pages and check the Page indexing report.

Should I block my website from Google before launch?

Protect the staging site with a password or IP restriction rather than relying on robots.txt or noindex, which can leak into production. robots.txt only controls crawling and is not a security measure. On launch, double-check that no noindex or Disallow: / rule remains on the live site.

What should I set up in Search Console after launch?

Verify a Domain property using DNS so it covers all subdomains and protocols, submit your XML sitemap, inspect and request indexing for the homepage and key pages, and check the Page indexing and HTTPS reports over the following weeks. Add your team as users with appropriate permissions.