Website launch SEO checklist

Website launch SEO checklist: before, during and after go-live

A website launch SEO checklist makes sure a new or redesigned site can be crawled and indexed from day one: staging kept private, noindex and robots.txt rules removed, redirects mapped, Search Console verified and the first queries reviewed. 39 checks across 5 phases. For a deeper review of an established site, use the SEO audit checklist or run the free SEO audit on your live homepage. Before launch, run a mobile-friendly test to confirm viewport scaling and tap targets on a phone.

Written by Vasa, GEO & AEO specialist · Last updated

Audit your launch free

Your progress

0 / 390%

  1. Before launch: staging and site setup0/12
  2. Before launch: redesigns and migrations0/5
  3. Launch day0/10
  4. First week after launch0/6
  5. First month: build visibility0/6

Ticks are saved in this browser only. Nothing is uploaded and no account is needed.

Every check is tickable and your progress is saved in this browser. Each one shows how badly it hurts to skip it (12 are critical), how long the fix takes, and whether it is a developer or content job, so you can split the list before launch day.

Start here: the checks that can sink a launch

0 of 6 cleared

Most launch SEO work affects how fast you grow. These decide whether Google can index the new site at all.

  • — Google drops or never indexes the page, however good it is. details
  • — A leftover 'Disallow: /' blocks crawling of the entire site. details
  • — An indexed staging copy competes with the real site as duplicate content. details
  • — Canonicals pointing at staging tell Google to index the wrong site. details
  • — Rankings and backlinks earned by the old site are lost overnight. details
  • — You cannot see indexing errors or request indexing for new pages. details

How to launch a website without losing SEO

  1. 01
    Prepare staging so nothing leaks

    Keep staging private, write the production robots.txt, and set unique titles, H1s and self-referencing canonicals before the site goes public.

  2. 02
    Map redirects if you are replacing a site

    List every old URL, map each one to its closest new page with a 301, and record a traffic benchmark.

  3. 03
    Verify the live site on launch day

    Remove noindex, check robots.txt and HTTPS, then verify Search Console and submit the sitemap.

  4. 04
    Watch indexing in the first week

    Fix excluded pages, broken links, slow pages and orphan pages while the problems are still small.

  5. 05
    Build visibility in the first month

    Earn relevant links, review your first queries, rewrite low click-through titles and run a full audit.

Filter
Filters apply to the printed PDF as well, so you can print just the critical list.

Before launch: staging and site setup

0 / 12 done

Most launch-day SEO disasters are set up weeks earlier on staging. Fix these while the site is still private, so nothing has to be undone in public.

  • Critical≤ 5 minDev

    The staging or preview URL sits behind a login or sends noindex, so Google never indexes a duplicate of the site before it goes live.

    Check a URL's indexability
  • Critical≤ 5 minDev

    The staging rule 'Disallow: /' is not copied to production. The live robots.txt allows the pages you want found and points to your sitemap.

    Generate a robots.txt
  • Important≤ 5 minDev

    Decide between www and non-www and stick to it in links, canonicals and the sitemap. The other version redirects to it.

  • Critical~30 minContent

    No template defaults such as 'Home' or the framework name. Each title says what the page is about and stays under roughly 60 characters.

    Preview titles in Google
  • Important≤ 5 minContent

    The main heading describes the page, appears once, and headings below it follow in order without skipping levels.

  • Critical≤ 5 minDev

    Each page's canonical points to its own live URL, not to staging, the homepage, or a URL with tracking parameters.

    Check a canonical tag
  • ImportantHalf a day+Dev

    Headlines and body copy load without JavaScript. Pages that only fill in after scripts run are indexed slowly and are invisible to most AI crawlers.

  • Important~30 minDev or content

    Lowercase words separated by hyphens, no IDs or session parameters, and the final URLs settled before launch so you are not redirecting them a month later.

  • Important~30 minContent

    Meaningful images describe what they show; decorative ones use empty alt. Hero images are compressed and sized for the space they fill.

  • Critical~30 minDev

    Text is readable without zooming, buttons are easy to tap, and nothing scrolls sideways. Google indexes the mobile version of your site.

  • Polish~30 minDev

    Organization or WebSite markup on the homepage, plus Product, Article or LocalBusiness where it fits. It validates with no errors.

    Validate structured data
  • Polish≤ 5 minDev or content

    og:title, og:description and a 1200x630 og:image on key pages, so links shared at launch show a proper preview card.

Before launch: redesigns and migrations

0 / 5 done

Skip this group for a brand-new domain. If you are replacing an existing site, these checks protect the rankings and links it already earned.

  • Critical~30 minDev or content

    Export every indexed URL from Search Console, the old sitemap and your analytics, including pages that earn traffic or backlinks.

  • CriticalHalf a day+Dev

    Each old URL has a one-to-one 301 redirect to the most relevant new page. Sending everything to the homepage throws away its rankings.

  • Important≤ 5 minDev

    Old URLs reach their final page in a single hop, and nothing redirects back to itself.

  • Important~30 minContent

    Pages that bring in search traffic keep their topic, main copy and title on the new site rather than being cut down during the redesign.

  • Important≤ 5 minDev or content

    Save current clicks, impressions, top queries and top pages so you can tell a launch dip from a real loss afterwards.

Launch day

0 / 10 done

The site is public. Spend the first hour confirming that what went live is what you tested, then tell Google about it.

  • Critical≤ 5 minDev

    No page that should rank still carries a noindex meta tag or X-Robots-Tag header left over from staging.

    Check a URL's indexability
  • Critical≤ 5 minDev

    Open yourdomain.com/robots.txt and confirm it is the production file, it allows your key pages, and it lists the sitemap.

    Test robots.txt rules
  • Critical≤ 5 minDev

    The certificate is valid, every page loads over https, and http plus the non-preferred domain 301 to the preferred https version.

    Check the SSL certificate
  • Important≤ 5 minDev

    The sitemap contains final, indexable, canonical URLs that return 200 - no staging links, redirects or noindexed pages.

    Generate a sitemap
  • Critical≤ 5 minDev or content

    Add a Domain property so every subdomain and protocol is covered, and verify it. Add Bing Webmaster Tools too; it feeds other search and AI engines.

  • Important≤ 5 minDev or content

    Submit the sitemap URL and confirm Google reads it with no errors. It speeds up discovery of a new site's pages.

  • Polish≤ 5 minDev or content

    Use URL Inspection on the homepage and two or three key pages and request indexing. There is no need to do every page.

  • Important≤ 5 minDev

    Open the site and confirm your visit appears, and that signups or contact forms are tracked as conversions.

  • Critical≤ 5 minDev

    For a migration, test a sample of high-traffic old URLs and confirm each lands on the right new page with a single 301.

  • Important≤ 5 minDev

    Missing pages show a helpful page with links home, and send a 404 status rather than 200, so Google does not index them.

First week after launch

0 / 6 done

Google starts crawling within days. Watch what it finds and fix problems while they affect a handful of pages, not hundreds.

  • Important~30 minDev or content

    In Search Console, look for pages excluded by noindex, robots.txt, redirects or 'crawled - currently not indexed', and fix anything that should be indexed.

  • Important~30 minDev

    Test the homepage and a key landing page on mobile. Fix oversized images, render-blocking scripts and layout shifts first.

  • Important~30 minContent

    No key page is an orphan reachable only through the sitemap. Navigation and in-text links connect related pages with descriptive anchors.

  • Polish≤ 5 minDev or content

    Choose whether GPTBot, ClaudeBot, PerplexityBot and Google-Extended may read the site, and make robots.txt match that decision.

    Check AI crawler access
  • Polish≤ 5 minDev or content

    An optional plain-text summary of your key pages at /llms.txt helps AI assistants find the pages that explain your product.

    Generate an llms.txt

First month: build visibility

0 / 6 done

A new site is technically ready long before it ranks. This is where impressions turn into clicks.

  • Important~30 minDev or content

    Create a Google Business Profile if you serve a location, and list the site on the directories and communities your customers actually use.

  • Important≤ 5 minContent

    After two to four weeks, see which queries show impressions. Pages ranking on page two are usually the quickest wins for better titles and content.

  • Polish≤ 5 minContent

    Pages with impressions but few clicks get clearer, more specific titles and descriptions that match the query.

    Preview titles in Google
  • PolishHalf a day+Content

    List the questions customers ask before buying and plan one useful page per question, linked from the pages they support.

  • Important≤ 5 minDev or content

    Audit the homepage and main landing pages to catch anything this list missed, and re-run it after each significant change.

Check your new site in one scan

Paste your live homepage. The audit checks indexability, robots.txt, canonicals, schema, mobile layout and AI crawler access, and ranks the fixes by impact.

Frequently asked questions

What is a website launch SEO checklist?
It is the list of SEO checks to run before, during and after a site goes live, so search engines can crawl and index it from day one. This one has 39 checks in 5 phases: staging setup, redesign migrations, launch day, the first week and the first month.
What is the most common SEO mistake when launching a website?
Leaving staging settings in place: a noindex tag or a robots.txt 'Disallow: /' copied to production. Either one can stop Google indexing the whole site, and nothing looks wrong to visitors.
How long does it take Google to index a new website?
Usually from a few days to a few weeks. Verifying Search Console, submitting a sitemap and getting a few links from sites Google already crawls tend to speed it up. Indexing is not the same as ranking, which takes longer.
What should I check before migrating or redesigning a website?
List every indexed URL, map each one to its closest new page with a single 301 redirect, keep the content of pages that already rank, and record current traffic so you can compare after launch.
Do I need to submit my new website to Google?
Google can find a site without it, but verifying Search Console and submitting your sitemap is the fastest reliable way, and it lets you see indexing errors early.
Should a new website block AI crawlers?
It is a business decision. Allowing crawlers such as GPTBot and PerplexityBot lets AI assistants read and cite your pages; blocking them keeps your content out of their answers. Whatever you choose, make robots.txt match it.
Can I check my launch automatically?
Partly. The free IMVASA audit checks the technical items on any public URL, such as indexability, canonicals, robots.txt, structured data and mobile layout. Steps like Search Console setup and redirect mapping need a person, which is what this checklist is for.
Does my progress save if I close the tab?
Yes. Ticked checks are stored in your own browser, with no account and nothing uploaded.