Website Launch SEO Checklist

Oof. A website launch can tank years of SEO work REALLY fast, and most teams don't realize it until traffic drops.

So, here's the website launch SEO checklist we actually use. 105 checks across six phases, from early planning through the first month after launch. Grab the parts you need.

Why a relaunch is risky at all

Alright, here's the slightly depressing part. Website launches go sideways ALL the time, including launches run by really smart people who thought SEO was covered.

Google already knows your current site. Then launch day comes and URLs change, content disappears, redirects get missed, or somebody adds a giant video because it looks cool.

We've seen a major e-commerce site drop from 4 million organic users a month to 2 million after a launch. For months, the team was panicking and trying different fixes before they called us.

New websites don't get a free pass

Years ago, we'd actually see a nice SEO bump after some launches. Not anymore. Big changes can take time for Google to process, and brand-new domains can take even longer.

You've got about three months

Find the big problems early and recovery is usually much easier. Let them sit for months and you've given Google a LOT of time to get comfortable with the wrong version of your site.

Got a launch coming and want somebody to pressure-test the plan before it's built? That's the whole job for us.

Talk to a launch SEO expert

How to use this checklist

First, you do NOT need to work all 105 items. Unless website launches are your full-time job, that's probably more than you need.

Figure out where you are in the process and start there. Already building? Skip ahead. Short on time? Start with the must-do items. Need assignments? Grab the spreadsheet.

Also, fair warning, some of these get nerdy. If you're reading one and thinking, "I have no idea what that means," there's a decent chance somebody else should own it.

When SEO should join the project

Across the top is a normal website project. The bar shows how much of it SEO was in the room for.

RFP & firm selectionContent structureWireframesDesignDev siteLaunch & testingGo-live

BestWhole project
Joins at the RFP
Better60+ days out
Joins at wireframes
Workable2 to 4 weeks
Joins at the dev site
Or SEO shows up after go-live

Really not idealMonths of recovery
Don't botherA rebuild, not a fix

Severity

45 CriticalMissing it costs traffic, revenue, or data you can’t get back. Don’t launch without it.
45 ImportantMissing it degrades performance or makes recovery slower. Fix before launch if you can, immediately after if you can’t.
15 RecommendedCompounding advantages, mostly in AI visibility. Skip under deadline pressure, then schedule them.

The checklist

Want to actually track progress and assign stuff? Grab the spreadsheet version. Nothing you check here gets saved.

Rather work it as a spreadsheet?

Same 105 checks, already filtered and sorted, with a status column so you can track who did what.

Phase 01

Scope and contract

Before you sign anything

14 checks

The cheapest launch problems to fix are the ones you write into the scope of work. Every item below costs a sentence now and a rebuild later.

One to watch for. Developers will very often say they'll handle SEO, and what they mean is metadata and an SEO plugin you can fill in yourself. That's a small slice of the list below. Ask which of these items they're actually doing before you assume any of them are covered.

On the flip side, an SEO shouldn't design your navigation or your site. The point of having one at the table is that when you make a call for the brand, you know what it costs you organically before you make it.

  • SEO fundamentals written into the build scope

    Editable page titles, meta descriptions, and image alt text on every template, not just the homepage.

    CriticalSEODev
  • Blog or resource section included in the build

    Even if it launches empty or in draft. Retrofitting a content hub after launch is a second project.

    ImportantContentDev
  • 301 redirect mapping named as a deliverable with an owner

    Decide now whether the dev team, the SEO team, or the client builds the map. Assume nobody and it won't get built.

    CriticalSEODev
  • Site speed and performance work in scope

    Minified scripts, an image pipeline, caching rules. Performance is a build decision, not a post-launch cleanup.

    ImportantDev
  • Metadata layer or SEO plugin specified for the CMS

    Yoast, Rank Math, or the platform equivalent. Confirm it handles titles, descriptions, canonicals, schema, and sitemaps.

    ImportantDev
  • Site security best practices in scope

    HTTPS across every hostname, security headers, and secure cookie attributes.

    ImportantDev
  • Launch week support hours reserved

    Budget real developer time for the week of launch. Something always needs fixing in the first 48 hours.

    CriticalDev
  • Content strategy and new content ownership settled in writing

    Who writes the new pages, who approves them, and by when. Ambiguity here delays launches more than any technical issue.

    CriticalContent
  • Four or more weeks budgeted for dev site review

    Two weeks between a first build and go-live isn't enough to review, fix, and re-review.

    CriticalSEODevContent
  • Standard CMS chosen over custom unless there's a real technical need

    WordPress, Shopify, HubSpot, BigCommerce. A custom CMS means custom fixes for every SEO requirement, forever.

    ImportantDev
  • Dev partner's SEO track record checked

    Ask for a site they launched and look at what happened to its organic traffic afterward.

    ImportantSEO
  • Structured data ownership assigned

    Who writes the schema, who validates it, and which types the templates need.

    ImportantSEODev
  • Analytics and tag migration plan named

    Including who rebuilds key events and conversions in the new environment.

    CriticalAnalytics
  • Staging environment access granted to everyone who needs to review

    Including the SEO team, with permission to crawl it.

    ImportantDevSEO
Phase 02

Architecture, design, and build

Through the redesign process

22 checks

Most launch traffic loss traces back to a decision made here, weeks before anyone ran a crawl. Review architecture and templates while changing them is still cheap.

The principle underneath the whole phase: the less you change, the less risk you carry. Start by being honest about what you're actually doing. Making it prettier is low risk. Rewriting all the content is higher. Rebuilding the navigation so content lives somewhere else entirely is the highest, and it's the one that generates hundreds of redirects. None of that means don't do it. It means know which one you signed up for.

  • New content architecture reviewed against the old site

    Confirm nothing that currently earns traffic is quietly getting dropped in the rebuild.

    CriticalSEOContent
  • New pages checked for overlap with existing ones

    Two pages competing for the same topic split the signal and neither one wins.

    ImportantSEOContent
  • Designs allow real body text on every template

    Image-heavy layouts with almost no text give search engines and AI systems nothing to work with.

    CriticalContent
  • Navigation is complete and crawlable

    Every important page reachable within a couple of clicks, with real links rather than script-driven menus.

    CriticalSEODev
  • Critical content isn't buried behind interactions

    Content hidden in tabs, accordions, or modals is harder for crawlers to weigh. Use hidden="until-found" where collapse is necessary.

    ImportantDevContent
  • URLs stay the same wherever possible

    Every changed URL is a redirect to maintain and a small amount of signal to lose. Change them only where there's a reason.

    CriticalSEO
  • URL patterns are lowercase, hyphenated, descriptive, and shallow

    Treat URLs as a public contract. Once published, they should keep working.

    ImportantDevSEO
  • Heading levels follow content hierarchy, not visual size

    One H1 per page, no skipped levels, no H3 picked because the text looked right.

    CriticalContentDev
  • Primary content and metadata render server-side

    Crawlers, social scrapers, and AI agents index the HTML your server returns. Content assembled later by client-side JavaScript is a gamble.

    CriticalDev
  • Embedded and iFramed content has a visibility plan

    Content inside a third-party embed generally doesn't count as yours. Decide what needs to live in your own HTML.

    ImportantSEODev
  • Templates reviewed on a real phone

    Desktop-only review misses the mobile problems that show up in Core Web Vitals field data after launch.

    ImportantDevContent
  • Module and plugin count kept lean

    Every extra plugin is weight, a conflict risk, and another thing to debug on launch day.

    ImportantDev
  • Question-style subheadings supported in templates

    Descriptive, question-shaped H2s help AI systems pull clean answers out of your content.

    RecommendedContent
  • Content chunked into short sections

    Roughly 300 words or less per section, with the answer stated first. Consistent chunking helps AI extraction more than length does.

    RecommendedContent
  • Author bylines, bios, and dates supported on content templates

    Named authors with sameAs schema linking to real profiles. "Admin" and "Staff" carry no authority signal.

    RecommendedContentDev
  • Tables render as HTML tables

    Data trapped in an image can't be read by search engines or AI systems.

    RecommendedContent
  • Image alt text fields present and populated in the CMS

    Migrate the existing alt text rather than starting from empty fields.

    ImportantContent
  • Breadcrumbs in the UI and marked up as BreadcrumbList

    Helps users orient and gives crawlers an explicit hierarchy.

    RecommendedDev
  • Internal linking plan for priority pages

    Internal links are the strongest signal you control for telling crawlers what a page is about.

    ImportantSEO
  • Dev site blocked from indexing

    Password protection or authentication is safer than robots.txt alone. Verify it before the build goes wide.

    CriticalDev
  • Technical SEO crawl of the dev site

    Two to four weeks before launch at minimum. Use a real crawler, not a free browser extension.

    CriticalSEO
  • Accessibility basics checked on templates

    Color contrast, form labels, keyboard navigation, visible focus, and descriptive link text.

    ImportantDev
Phase 03

Pre-launch

7 to 21 days before go-live

25 checks

Everything here is a backup or a baseline. If something goes sideways after launch, these are the records that tell you what changed.

The phase is also where the technical basics get checked while there's still time to fix it. Page speed work in particular needs a developer and a runway, so finding it two days before go-live means either launching slow or moving the date.

  • Full crawl of the current live site archived

    URLs, titles, meta descriptions, H1s, status codes, and word counts. Save the export somewhere you can find it in six months.

    CriticalSEO
  • Copy of the existing robots.txt saved

    Small file, easy to lose, and you'll want to compare it after launch.

    CriticalSEO
  • Copy of the existing redirect rules saved

    Old redirects that still carry traffic need to survive the migration.

    CriticalDev
  • Existing image alt text exported

    Alt text is one of the first things lost in a content migration.

    ImportantSEO
  • Existing structured data captured

    Record which schema types exist on which templates so you can rebuild or improve them.

    ImportantSEO
  • Top organic pages listed as a protect-list

    Rank pages by organic sessions, clicks, and referring domains. These get checked first on launch day.

    CriticalSEO
  • Redirect map built URL by URL

    Every retired URL points to its closest equivalent. No blanket homepage rules.

    CriticalSEODev
  • Retired products and pages triaged by type before mapping

    Coming back later: leave the page up and say it's out of stock. Gone for good: let it 404. Replaced by a newer version: redirect to the new one. Redirecting a discontinued product to a loosely similar one is a bait and switch, and you can get dinged for it.

    ImportantSEODev
  • Redirect chains flattened to a single hop

    Old redirect plus new redirect is a chain. Point the original URL straight at the final destination.

    ImportantDev
  • Titles and meta descriptions checked on the new site

    Page by page for priority templates, against the approved set.

    CriticalSEOContent
  • Canonical tags point to the live HTTPS URL of each page

    Staging canonicals shipping to production is a common and expensive mistake.

    CriticalDev
  • XML sitemap generated with canonical, indexable URLs only

    No redirects, no 404s, no noindexed pages in the sitemap.

    CriticalDev
  • Sitemap lastmod values reflect real modification dates

    Freshness signals matter more to AI systems than to traditional search, and AI caches run older than Google's.

    RecommendedDev
  • New robots.txt drafted and reviewed

    Allow AI crawlers unless there's a business reason not to. Blocked LLM bots means your content can't be referenced in AI answers.

    ImportantSEO
  • Analytics installed on the new site

    Within 24 hours of launch, so the tracking is live from the first visitor.

    CriticalAnalytics
  • Tag manager container migrated and key events mapped

    Test in the development environment where possible, and plan to rebuild key events rather than assuming they carry over.

    CriticalAnalytics
  • PageSpeed Insights run on the major templates

    Homepage, category, product or service, and article. Record the numbers as your baseline.

    ImportantDev
  • Images compressed and sized

    Most images under 100KB, modern formats, explicit width and height, lazy loading on everything except the LCP image.

    ImportantDev
  • Core Web Vitals checked against thresholds

    LCP at or under 2.5s, INP at or under 200ms, CLS at or under 0.1, measured at the 75th percentile.

    ImportantDev
  • Organization schema on the homepage and validated

    Acts as the identity record AI systems use to work out who you are and what you do.

    RecommendedSEO
  • Schema present beyond a single page

    Consistent patterns across templates build more trust than one heavily marked-up page.

    RecommendedSEO
  • 404 page returns a real 404 status

    A friendly "not found" page that returns 200 is a soft 404, and search engines treat it as a quality problem.

    ImportantDev
  • Baseline rankings, traffic, and indexed page count recorded

    You can't prove what recovered if you never wrote down where you started.

    CriticalSEO
  • Launch runbook written with owners and a rollback plan

    Who does what, in what order, and what happens if it goes wrong.

    ImportantDevSEOAnalytics
  • Launch date set for early in the week

    Whoever fixes launch-day problems goes home on Friday. A broken site sitting through a weekend is two extra days of Google seeing something wrong.

    ImportantDevSEO
Phase 04

Launch day

Go-live and the first few hours

21 checks

Work top to bottom. The first five items catch the failures that do the most damage in the shortest time.

Two habits worth adopting. Soft launch when you can: put the site live, work this list, and hold the press release until you know nothing is broken. And don't launch on a Friday. The people who fix launch-day problems go home on Friday evening, and a broken site sitting through a weekend is two extra days of Google seeing something wrong.

  • robots.txt checked on the live site

    Look for a disallow rule that shouldn't be there. It takes ten seconds and prevents a week of lost crawling.

    CriticalSEO
  • Site-wide noindex removed and spot-checked

    Everyone swears they'd never do this. It happens on something like half the launches we see. Check the source of several templates, not just the homepage.

    CriticalSEO
  • Full crawl of the new live site, compared against the pre-launch crawl

    Diff the URL lists, status codes, titles, and metas. Investigate every unexpected difference.

    CriticalSEO
  • Titles, meta descriptions, and H1s checked against the approved set

    Spot-check every template type, not just a sample of one.

    CriticalSEO
  • Redirects spot-checked manually

    Start with the protect-list of top organic pages. Confirm each lands on the right page.

    CriticalSEO
  • Redirects return a 301, not a 302 or a JavaScript redirect

    Permanent moves need a permanent status code.

    CriticalDev
  • Navigation and key user paths walked by a person

    Menus that broke between the dev site and production, forms that don't submit, product pages that 500. Click through it like a customer would.

    CriticalDevSEO
  • Analytics firing on every template, confirmed in real time

    Open the realtime report and walk the site. Check every template, including checkout or form pages.

    CriticalAnalytics
  • Key events and conversions confirmed firing

    Form submits, purchases, calls, and whatever else the business reports on.

    CriticalAnalytics
  • Dev or staging site taken down, blocked, and deindexed

    Leaving it reachable creates a duplicate of your entire site.

    CriticalDev
  • Paid traffic paused, destination URLs updated before resuming

    Ads pointing at redirected or dead URLs waste spend and hurt quality scores.

    CriticalAnalytics
  • HTTPS enforced sitewide

    Every http URL and every non-canonical hostname redirects to the canonical https version, in one hop.

    CriticalDev
  • New sitemap submitted in Search Console

    Confirm it's accepted and the discovered URL count looks right.

    ImportantSEO
  • Launch annotated in analytics

    Future you will want to know exactly which date the line moved.

    ImportantAnalytics
  • PageSpeed Insights re-run on the major pages

    Compare against the pre-launch baseline and flag anything that got materially slower.

    ImportantDev
  • Mixed content check on key templates

    An HTTPS page loading anything over HTTP triggers browser warnings and blocked resources.

    ImportantDev
  • Internal links point to final URLs, not through redirects

    Menu, footer, and in-content links updated to the new URLs.

    ImportantDev
  • Search Console property verified for the new site

    Set up a domain property if one doesn't exist, so you see every subdomain and protocol.

    ImportantSEO
  • AI crawler access confirmed in the live robots.txt

    Check the training, search, and user-triggered agents separately. See the AI and GEO reference below for the current list.

    RecommendedSEO
  • Core security headers in place

    HSTS, X-Content-Type-Options, frame-ancestors, and Referrer-Policy.

    RecommendedDev
  • Cookie consent and privacy policy live and working

    Consent should gate non-essential scripts without blocking analytics you're relying on this week.

    ImportantDev
Phase 05

First week after launch

Days 1 to 7

12 checks

Google is fussy about relaunches and often delays indexing for weeks before things settle. Watch daily and fix fast, because early problems compound and the clock on full recovery is already running.

A drop in week one is not by itself a crisis. Movement is normal while Google re-crawls. What you're looking for is the difference between settling and a real problem, which is why the baseline from Phase 3 matters so much.

  • Search Console checked daily for crawl errors and coverage changes

    New error types appearing is the earliest warning you'll get.

    CriticalSEO
  • Indexed page count watched for a sharp drop or spike

    A drop means something is blocking indexing. A spike usually means duplicate URLs got exposed.

    CriticalSEO
  • Impressions and clicks watched against the baseline

    Segment by page type so you can see which templates are affected.

    CriticalSEO
  • Organic traffic compared against baseline by template

    A sitewide drop and a single-template drop have very different causes.

    CriticalSEOAnalytics
  • Ranking and visibility movement tracked on priority terms

    Movement in the first week is normal. Sustained decline on money pages is not.

    ImportantSEO
  • Server errors and 404s reviewed, with traffic and backlinks prioritized

    A 404 on a page with organic traffic or referring domains is an urgent fix, not a cleanup task.

    CriticalSEODev
  • Redirect misses found and patched

    Check Search Console and server logs for requested URLs that returned 404 instead of redirecting.

    CriticalDev
  • Second full crawl compared against launch day

    Catches problems introduced by post-launch fixes.

    ImportantSEO
  • Change of address filed in Search Console for a domain move

    Only applies when the domain itself changed. Skip it for a same-domain relaunch.

    CriticalSEO
  • Conversion tracking reconciled against the old site's numbers

    A 40 percent drop in recorded conversions is usually broken tracking rather than a broken site.

    CriticalAnalytics
  • Paid campaigns resumed and landing pages verified

    Confirm each ad destination loads the intended page directly.

    ImportantAnalytics
  • Core Web Vitals field data watched as real traffic arrives

    Lab scores and field data diverge, and field data is what gets reported.

    ImportantDev
Phase 06

Weeks two through four

Days 8 to 30

11 checks

Indexing and rankings usually settle in this window. Anything still down after four weeks needs individual diagnosis rather than more waiting, and you're now inside the three-month window where a full recovery is still realistic.

Now is also the point to stop looking only at your own site. A big part of how both Google and AI systems decide whether to trust you is whether anyone else is talking about you. If you want to be the coolest kid in school, it helps when the coolest kid in school says you're cool.

  • Weekly crawl comparison until counts stabilize

    Stop when URL counts, status codes, and indexable page counts hold steady week over week.

    ImportantSEO
  • Pages that lost visibility triaged individually

    Compare the new page against the archived old version. Look for lost content, changed headings, and weaker internal links.

    ImportantSEO
  • Internal linking gaps filled on priority pages

    Rebuilds often drop the contextual links that supported key pages.

    ImportantSEO
  • Structured data validated across templates

    Use the Search Console enhancement reports rather than testing one URL at a time.

    RecommendedSEO
  • Blog or resource publishing resumed on a normal cadence

    Consistent fresh content signals an active site to both search engines and AI systems.

    RecommendedContent
  • Off-site authority work restarted

    Press, directories, social profiles, partner mentions. Backlinks and citations are how Google and AI systems decide whether anyone else vouches for you, and a relaunch is a reason for people to link.

    ImportantSEOContent
  • AI referral traffic segmented in analytics

    ChatGPT, Perplexity, Gemini, and Claude land in referral or unassigned traffic. A custom channel group makes them visible.

    RecommendedAnalytics
  • Brand visibility in AI answers spot-checked

    Run your core questions through the major AI tools and note whether you're cited and whether the details are right.

    RecommendedSEO
  • Backlink profile checked for links pointing at retired URLs

    Earned links are worth reclaiming with a direct redirect rather than losing to a 404.

    ImportantSEO
  • Post-launch fix list documented with owners and dates

    Anything not fixed in week one needs a name and a date against it.

    ImportantSEODev
  • Retrospective held with the dev partner

    Write down what went wrong and what you'd do differently. The next launch is easier for it.

    RecommendedSEODevContent

Hit something on this list that nobody on your team wants to own? We can run those pieces with you.

Get help with your launch

The failures that cause the most damage

If you only have an hour before go-live, spend it here. Ordered by damage done against time taken to check.

  1. The staging noindex ships to production

    Every single person swears this could never happen to them, and it shows up on roughly half the launches we're involved in. One noindex robots meta tag left in a template header tells Google the one thing you least want it to hear, and a site can drop out of search in days. Check the raw HTML of at least four different template types, not just the homepage. Ten seconds each.

  2. No redirect map, or a map that sends everything to the homepage

    A 301 is a change of address form. You're telling Google the content moved and where it went. Point a hundred retired URLs at the homepage instead and you've filed a hundred forms that all say "somewhere in this city," which Google reads as a soft 404. Every retired URL gets its closest real equivalent. If nobody can produce the map, you're not ready to launch.

  3. Analytics goes dark at launch

    A gap in tracking can't be backfilled. If the container didn't migrate or the key events didn't get rebuilt, you lose the data that proves whether the launch worked, and you find out three weeks later when somebody asks for the numbers.

  4. The old staging site stays reachable

    An indexable copy of your entire site, competing with the real one. Take it down, put it behind authentication, confirm it's gone.

  5. Content quietly disappears in the rebuild

    Designers trim copy to open up the layout, and pages that ranked on 800 words end up with 200. The page looks better and answers less. Diff word counts between the archived crawl and the new one, then look hard at anything that dropped by more than half.

  6. Canonicals point at staging

    Every page telling search engines the real version lives on a hostname nobody can reach. Grep the crawl export for the staging domain.

  7. Redirect chains

    Old redirect plus new redirect works fine for a user and dilutes the signal for a crawler. Flatten every chain to one hop while the map is still fresh in someone's head.

  8. Nobody clicked through the site

    Crawls catch status codes and metadata. They don't catch a contact form that silently fails, a menu that lost half its links, or a checkout that breaks on step two. Walk the site like a customer before you tell anyone it's live.

Changing platforms during your website launch?

Yep, everything in the website migration SEO checklist still matters. You just have more opportunities for URLs, redirects, settings, and functionality to change underneath you.

Different platforms handle SEO differently. You may lose fields you use today, get fewer redirect options, or discover after signing that something you assumed was editable…isn't.

So ask the annoying questions BEFORE you choose the platform. Get clear on URLs, redirects, SEO fields, and what you can actually control before anyone signs anything.

Questions we get every time

Real questions from our launch webinar, plus the stuff we hear over and over from clients.

Isn't SEO during a website launch just a box you check?

Nope. And honestly, I wish it were.

Adding a sitemap right before launch is checking a box. Good launch SEO starts while decisions are still being made and keeps going after the new site is live. Most expensive cleanup projects we see started way earlier than launch day.

How long do I have to fix launch problems before it's too late?

About three months is the window I really care about.

Catch the big stuff during those first few months and recovery is usually much easier. Wait longer and Google has had months to crawl bad redirects, missing pages, or weaker content. Can we still fix it later? Yep. It's just a bigger project.

How long before a brand-new website starts ranking?

Longer than it used to. Sometimes annoyingly longer.

A brand-new domain can take months to gain traction. An established domain getting a redesign is a different situation and can hold much steadier if the launch is handled well. Either way, don't build your entire revenue forecast around instant SEO traffic.

We're on Wix or Squarespace. Does that change anything?

A little, but probably less than you think.

Wix and Squarespace have gotten MUCH better at SEO. The bigger issue is control. Certain fields, redirects, or technical fixes may be limited. For a smaller site, that may be totally fine. For a huge e-commerce site, limitations matter a lot more.

Our website is basically a brochure. Should we do SEO or start over?

Please don't start over just because the site feels old.

An older site can still have years of history, links, rankings, and URLs worth keeping. Build on what already works. Add useful pages. Improve what needs improving. Starting with a brand-new domain can create a bunch of SEO work you didn't need.

If we move a product page to a new URL, do we always redirect it?

Almost always. What you do depends on what happened to the product.

Same product, different URL? Use a 301 redirect from the old URL to the new one. You want Google and anyone clicking an old link to land on the correct product page.

Temporarily out of stock? Keep the page live. Tell people it's unavailable, give them whatever helpful information you can, and let them sign up for an update if that makes sense.

Gone for good? Redirect to the closest useful alternative or relevant category page. Don't send every discontinued product to the homepage. If the destination isn't actually useful to the person who clicked, Google may treat that redirect like a soft 404.

Should we write website content for users or search engines?

Users. Then use search data to make the content better.

Search data can tell you what people ask, what language they use, and what information they're looking for. Use that. Problems start when you force a page around a keyword your actual audience would never search for or care about.

What's the most common website launch SEO problem?

A noindex setting making it onto the live site. Yep, really.

The new site looks perfectly normal, everyone celebrates, and Google is being told not to index it. We've seen good teams make that mistake. Check your indexing settings on launch day, then check them again the next morning.

We're small and have no dev team. Which checks actually matter?

Start with the stuff that can actually make your traffic disappear.

Know your existing URLs. Redirect changed pages correctly. Make sure search engines can crawl and index the new site. Preserve important page titles and content. Get those pieces right first, then work through the smaller SEO improvements after launch.

Who should own the website launch SEO checklist?

One person. Seriously. Give one person ownership of the whole thing.

Different people can handle different tasks, but somebody needs to know what's finished, what's missing, and whether an unresolved problem is big enough to delay launch. "I thought somebody else had that" is how a LOT of launch problems start.

Question this page didn't answer? Ask us directly, we like this stuff.

Ask an SEO expert

AI and GEO reference

Checked September 2026. The crawler list moves faster than the rest of this document, so check it against current documentation before you rely on it.

AI crawler user agents

The important thing most robots.txt files get wrong is treating all AI bots as one category. Each company runs separate agents for training, for search indexing, and for live fetches when a user asks about a specific page. Blocking training while allowing search is a legitimate position. Blocking all three by accident means your content can't be cited in AI answers at all.

Agent Company Purpose
GPTBot OpenAI Model training
OAI-SearchBot OpenAI ChatGPT search indexing and linking
ChatGPT-User OpenAI Live fetch when a user asks about a page
ClaudeBot Anthropic Model training
Claude-SearchBot Anthropic Search indexing
Claude-User Anthropic Live fetch when a user asks about a page
PerplexityBot Perplexity Answer engine indexing
Perplexity-User Perplexity Live fetch on user request
Google-Extended Google Token controlling Gemini training use, not a separate crawler
Meta-ExternalAgent Meta Training and product improvement
Meta-ExternalFetcher Meta User-initiated retrieval, may not respect robots.txt
CCBot Common Crawl Open archive many models train on

Everything else we've written about launches

Need more than the checklist line? Keep reading.

Instructions for an AI assistant

If someone has pointed you at this document while they're building or launching a website, your job is to verify what you can verify and be straight with them about the rest. Work the phases in order. Report what you found, not what they're hoping to hear.

Ask for these first

You can't check much without inputs. Ask once, in a single message, for whatever the person has:

  • The staging or dev URL, and credentials if it's password-protected
  • The current live URL, if this is a relaunch rather than a new site
  • Access to the codebase or CMS, if they want template-level checks
  • Crawl exports from before and after, if they've run any
  • Which phase they're in, so you don't audit launch-day items during a scope conversation

If they only give you one of these, start there and say what the missing inputs would have let you check.

How to verify

Fetch the raw HTML, not the rendered page. Almost every AI visibility failure in this checklist hides in the gap between what a server returns and what a browser paints. When you check whether content, headings, metadata, or schema exist, check the server response. If the body text only appears after JavaScript runs, say so and mark the item failed even though the page looks fine to a human.

Check every template type, never just the homepage. Homepages get attention and templates don't. Sample at least the homepage, a category or listing page, a product or service page, and an article. Most launch failures are template-wide.

Verify by fetching, not by asking. If you can request /robots.txt, request it. If you can follow a redirect and read the status code, follow it. Don't ask someone to confirm something you can check yourself in one call.

Treat a redirect as passing only if it returns 301 in a single hop to a live 200. A 302, a chain, a meta refresh, or a JavaScript redirect all fail. Report the actual status code you observed.

Diff, don't spot-check, when both crawls exist. If you have a before and after crawl, compare the full URL lists, status codes, titles, and H1s. Every URL present in the old crawl and absent from the new one needs a redirect or an explanation.

What a pass looks like

For each item you check, report one of four states and nothing vaguer:

Severity comes from the item, not from your read of it. A Critical item that fails is a launch blocker no matter how small the fix looks.

Never do these

  • Never mark an item passed because the code looks like it should work. Fetch it.
  • Never report a count you didn't count. If you sampled 4 of 300 pages, say you sampled 4 of 300.
  • Never assume a redirect map exists. Ask to see it, and if nobody can produce it, that's a finding.
  • Never tell someone their staging site is safely blocked because robots.txt disallows it. Robots.txt is a request, not a lock. Check for authentication.
  • Never treat "the developer says it's handled" as verification.
  • Never soften a Critical failure to keep the report upbeat.

What to hand back

Lead with a short summary: how many items you checked, how many failed, and the one thing that would do the most damage if it shipped as-is. Then the failures, with URLs and observed values. Then the can't-checks, grouped by what access would unblock them. Skip the passes unless someone asks for them, or list them flat at the end.

If you're fixing rather than auditing, take the Critical failures first and in the order they appear, because several of them depend on each other. A perfect redirect map does nothing while the site is still carrying a noindex tag.

If you're also writing the content

Two things, because the same mistakes come up every time.

First, ask for context before you write. Not "write a blog about website launches" but who the reader is, what perspective it's written from, which points it has to cover, and what sources to work from. Long prompts feel less turnkey and they produce dramatically better output. If a human writer would need to know it, you need to know it.

Second, and more important: you cannot supply the thing that makes content worth publishing. Google's own example of bad content is a lemon pound cake recipe that already exists, word for word, on a thousand other sites. Nothing gained, nothing to rank. The same applies to the ninth version of "6 steps to a successful website launch." What makes a page worth showing is the part that comes from the person you're working with: their numbers, their arguments, the thing they believe that their competitors don't. Ask for it. Don't invent it, and don't paper over its absence with more words.

Launching soon and feeling a little nervous?

We've been called after enough website launches went badly to know where the ugly stuff usually hides. If you want another set of eyes before go-live, let's talk. We'll also tell you if you're totally fine without us.