Pre-Launch SEO Checklist: 12 Things Before You Go Live

Why pre-launch SEO matters more than post-launch SEO

Every item on this list is fixable after launch. The difference is cost: fixing a missing sitemap before Google's first crawl takes five minutes. Fixing it after Google has already indexed a broken version of your site — wrong canonicals, thin meta descriptions, a stray noindex left over from staging — means undoing a first impression Google already formed. Some of that damage (a slow start building domain trust, pages indexed under the wrong URL) takes months to fully recover from.

Fifteen minutes before you flip the switch is worth more than fifteen hours after.

The 12-point checklist

1. Remove any staging noindex tag

This is the single most common launch-day mistake. Dev and staging environments almost always run with <meta name="robots" content="noindex"> to keep Google from indexing the work-in-progress version. If that tag ships to production, your live site is invisible to Google — and nobody notices until traffic doesn't show up weeks later. Check your production HTML source for this line specifically, on launch day, after deploy.

2. Generate and submit sitemap.xml

Every real, indexable URL should be listed. See how to generate a sitemap if you don't have one yet, then submit it in Google Search Console the day you go live — don't wait for Google to find it organically.

3. Write a correct robots.txt

Make sure you're not accidentally blocking your entire site (a leftover Disallow: / from staging is the robots.txt equivalent of mistake #1), and that you are blocking admin panels, checkout flows, and internal search results. Full walkthrough: robots.txt guide.

4. Unique title tags and meta descriptions on every page

Not a template that just swaps in the page name — an actual title and description written for what that specific page is about. See meta tags explained for the character limits and format that convert best in the search results.

5. Schema markup for your key page types

Homepage, product pages, blog posts, FAQ pages — each should carry the JSON-LD schema type that matches its content. This is what unlocks rich results (star ratings, FAQ dropdowns, sitelinks) later. See the schema markup guide for which type fits which page.

6. Resolve canonical URLs — pick www or non-www, and stick to it

Decide once whether your canonical domain is www.yoursite.com or yoursite.com, set a 301 redirect from the other, and make sure every page's <link rel="canonical"> tag points to the same version consistently. Mixed signals here split ranking authority between two URLs that should be treated as one.

7. Open Graph and Twitter Card tags with a real image

Test how your homepage and a couple of key pages look when shared on Slack, X, or LinkedIn before launch — not after someone screenshots a broken preview card. You need og:title, og:description, and a 1200×630 og:image at minimum.

8. Alt text on every image

Especially your hero images and anything product-related — these are the images most likely to drive Google Images traffic once indexed, and the ones most commonly shipped with blank or filename-based alt attributes. Skim the alt text guide if you're not sure what "good" looks like.

9. If this is a redesign or migration, map every old URL to its new one

If you're relaunching an existing site rather than starting fresh, every URL that existed before needs a 301 redirect to its new equivalent — or you lose whatever rankings and backlinks that old URL had built up. Skipping this is the most expensive mistake on this list, and the easiest to avoid with a simple spreadsheet: old URL → new URL → redirect status, checked one by one before launch.

10. Set up and verify Google Search Console

Do this on day one, not week three — GSC only shows you data from the point you start collecting it, so every day you delay is a day of blind spots you can't retroactively fill in. Full walkthrough: Google Search Console setup guide.

11. Install and test analytics

Install GA4 (or your analytics tool of choice) and actually test it — load a page in an incognito window and confirm the event shows up in real-time reports. A silently broken analytics install means weeks of missing data before anyone notices traffic numbers look wrong.

12. Run a mobile and page-speed check

Google evaluates your site primarily on its mobile version (mobile-first indexing), and Core Web Vitals are a direct ranking factor. Check both before launch — a slow, broken-on-mobile page speed check discovered post-launch means you're fixing it while it's already live and potentially indexed with poor scores attached.

The checklist as a table

#	Item	Output
1	Remove staging noindex	Live crawlability
2	Sitemap	sitemap.xml
3	robots.txt	robots.txt
4	Meta titles & descriptions	meta-tags.html
5	Schema markup	schema-markup.html
6	Canonical URLs resolved	301s + canonical tags
7	Open Graph / Twitter tags	og-tags.html
8	Alt text	alt-text.json
9	301 redirect map (migrations only)	Redirect rules
10	Google Search Console	Verified property
11	Analytics	Tested GA4 events
12	Mobile & speed check	Core Web Vitals pass

Items 2, 3, 4, 5, 7, and 8 — six of the twelve — are files that Peak Visibility generates in one pass: paste your URL (once it's live, even on a temporary domain) and get sitemap.xml, robots.txt, meta-tags.html, schema-markup.html, og-tags.html, and alt-text.json as a downloadable ZIP in under 3 minutes. That leaves items 1, 6, 9, 10, 11, and 12 as the manual, launch-specific checks nothing can fully automate for you.

FAQ

How long before launch should I start this checklist?

The file-generation items (sitemap, robots.txt, meta tags, schema, OG tags, alt text) can be prepared against a staging URL and deployed at launch. The verification items (GSC, analytics, mobile/speed check, noindex removal) can only be confirmed once the site is actually live — plan to do those in the first hour after launch, not the first week.

What's the single most common mistake on this list?

Leaving a staging noindex tag in the production deploy. It's invisible unless you specifically check page source, and it silently makes your entire launch a non-event from Google's perspective.

Do I need all 12 items for a small site?

Item 9 (redirect mapping) only applies if you're migrating an existing site — skip it for a true from-scratch launch. Everything else applies regardless of site size; a 5-page site needs correct meta tags and a sitemap just as much as a 500-page one.

What if I've already launched without doing this?

Work through the list now — none of it is launch-day-only. The cost difference is speed of recovery, not whether recovery is possible. Start with item 1 (noindex check) since that's the one that can make everything else moot.