Pre-Launch Website Audit Checklist: Catch SEO Issues Before They Go Live

The most expensive time to find an SEO issue is the week after launch. The cheapest is two weeks before. This checklist is specifically for the pre-launch audit window — what to verify in staging or on the production domain shortly before go-live, in roughly the order it makes sense to verify it. It is not a comprehensive technical SEO guide and it deliberately ignores everything that can only be tested live.

Verify staging is blocked from indexing

Before any audit work begins, confirm the staging environment is robots-blocked and noindexed. Run a search for site:staging.yourdomain.com and confirm zero results. The number of launched sites that quietly indexed their entire staging environment for months before anyone noticed is depressingly high.

Audit the URL structure

Walk the planned URL structure end-to-end before launch. Decide on trailing slashes (one or the other, consistently). Decide on lowercase enforcement. Decide on which legacy URLs need redirects from the old site. The cost of changing URL structure post-launch is high enough that this conversation should happen before content is loaded.

Map redirects from the old site

Every URL that has external links or ranks today needs a redirect destination on the new site. The map should be a spreadsheet with three columns: old URL, new URL, type of redirect (301 in almost all cases). Build it from a full crawl of the live site plus a Search Console export of pages that have impressions. Pay particular attention to URLs that rank for high-value queries but get low overall traffic — these are the ones that get forgotten because they do not show up in Google Analytics.

Validate canonical tags

Every page in staging should have a canonical tag pointing to its production URL. Half the time this is wrong because it was templated from staging hostnames. A quick crawl with canonical extraction will catch this in one pass.

Check meta titles and descriptions for templates gone wrong

If your CMS templates titles from {product_name} | Site Name, run through 20 random pages and make sure none of them produce empty results, duplicates, or character-length issues. The same applies to meta descriptions — many launches ship with default descriptions on hundreds of pages because the template never got product-specific data.

Verify the sitemap

The sitemap should list every page you want indexed and exclude everything you do not. Common errors: including pagination URLs, including filter URLs, including thin tag archives. A pre-launch sitemap audit is a 15-minute job that prevents months of crawl-budget waste.

Test structured data

Pick one example of each template type — product, article, category — and run them through the Rich Results Test. Most schema errors are syntactic and would otherwise be caught only after Google indexes the pages and Search Console flags them, by which time you have lost the rich-result opportunity for the launch.

Performance baseline

Run Lighthouse on the staging build and capture the scores. Save them. You will want a before-and-after comparison the first time Core Web Vitals show up in Search Console post-launch, and the baseline is the only way to know if launch performance matched staging performance.

Internal linking density check

Pre-launch is when fixing the internal link graph is cheap — you just edit the templates. Post-launch you are editing pages individually. Make sure every important page is reachable from the navigation in three clicks, that breadcrumbs work, and that high-value pages have at least three relevant internal links pointing to them from elsewhere on the site.

The day-zero post-launch monitor

The audit does not actually end at launch. Set up a continuous site audit to run from day one, configured to alert you on any net new issues in the first 30 days. Most launch problems surface in the first month, and a monitor catches them while the cause is still fresh.

A clean pre-launch audit does not guarantee a clean post-launch experience, but it eliminates the dumb, predictable failure modes and lets you focus the first week on the genuinely tricky issues. For teams running UtilitySEO or similar, the pre-launch crawl is included in the standard workflow — there is no separate "launch checklist" feature to learn.