SiteAuditLint checklist library
What this checklist covers
A website launch SEO checklist makes sure a new site goes live crawlable and indexable, with staging blocks removed, canonicals and sitemaps on the production domain, redirects from legacy URLs, analytics installed, and Search Console verified.
It is organized into 16 sections: Before Launch, URLs, Titles and Meta, H1s, Canonicals, Internal Links, Robots.txt, XML Sitemap, Redirects, HTTPS, Structured Data, Analytics and Tracking, Search Console, AI Crawler Accessibility, Launch Day and First Week Monitoring. Each check lists exactly what to verify and a priority, so you can work through the highest impact items first.
For background on the concepts behind these checks, see Pre-launch website checklist, SEO fundamentals course, Desktop SEO crawler.
Testing method: For how to prove staging blocks will not ship and make a go or no-go call, see pre-deployment SEO testing.
Who it is for:
Download the website launch seo checklist
Use the interactive version below, or download it to share with your team, attach to tickets, or work through offline.
Website Launch SEO Checklist
Work through each check
0 of 20 checks complete
Before Launch
URLs
Titles and Meta
H1s
Canonicals
Internal Links
Robots.txt
XML Sitemap
Redirects
HTTPS
Structured Data
Analytics and Tracking
Search Console
AI Crawler Accessibility
Launch Day
First Week Monitoring
Progress is saved in this browser only.
Detailed explanations
Each section below explains what to check, why it matters, the problems you will usually find, how to fix them, and how to confirm the fix.
Before Launch
What to check:
- Remove staging blocks. Staging noindex and password rules are removed for production.
- Run pre-launch crawl. Staging crawl shows no critical errors.
Why it matters: Launches often ship staging settings to production. A single forgotten noindex or Disallow can keep a new site out of search for weeks.
Common problems:
- Staging noindex left on production
- Robots.txt still disallowing everything
- Canonicals pointing to the staging domain
- Analytics not installed
How to fix it: Use a launch runbook that removes staging protections, swaps domains in canonicals and sitemaps, and verifies tracking.
How to verify: Crawl production immediately after launch and compare against the final staging crawl.
Learn more: Pre-launch website checklist, Run your first audit, Noindex issues.
How SiteAuditLint helps: it checks before launch across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
URLs
On this checklist: finalize URL structure. Explained in full in the On-Page SEO Checklist.
Titles and Meta
On this checklist: check titles; check meta descriptions. Explained in full in the On-Page SEO Checklist.
H1s
On this checklist: check H1s. Explained in full in the On-Page SEO Checklist.
Canonicals
On this checklist: check canonicals. Explained in full in the Indexability Checklist.
Internal Links
On this checklist: check internal links. Explained in full in the On-Page SEO Checklist.
Robots.txt
On this checklist: publish production robots.txt. Explained in full in the Robots.txt Checklist.
XML Sitemap
On this checklist: generate sitemap. Explained in full in the Technical SEO Checklist.
Redirects
On this checklist: set up legacy redirects. Explained in full in the Technical SEO Checklist.
HTTPS
On this checklist: check HTTPS. Explained in full in the Technical SEO Checklist.
Structured Data
On this checklist: validate schema. Explained in full in the On-Page SEO Checklist.
Analytics and Tracking
What to check:
- Install analytics. Analytics and tag manager fire on all templates.
Why it matters: Without tracking you cannot measure the impact of launches, migrations, or fixes. Missing tags after a deployment create gaps that cannot be backfilled.
Common problems:
- Analytics missing on new templates
- Duplicate tags inflating sessions
- Conversion events lost after a redesign
- Search Console not verified on the new domain
How to fix it: Deploy analytics through a tag manager across all templates, verify Search Console, and test conversion events before launch.
How to verify: Use tag assistant and real time reports to confirm tags fire on each template and that conversions record.
Learn more: Tracking and analytics audit, Tracking pixel audit, Tracking missing on page issue, SEO KPIs lesson.
How SiteAuditLint helps: it checks analytics and tracking across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Search Console
What to check:
- Verify Search Console. Property verified and sitemap submitted.
Why it matters: Without tracking you cannot measure the impact of launches, migrations, or fixes. See the earlier section on this topic for common problems.
How to verify: Use tag assistant and real time reports to confirm tags fire on each template and that conversions record.
How SiteAuditLint helps: it checks search console across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
AI Crawler Accessibility
On this checklist: check AI crawler rules. Explained in full in the Technical SEO Checklist.
Launch Day
What to check:
- Crawl production. Production crawl matches pre-launch crawl.
- Spot check key pages. Homepage and money pages render and return 200.
Why it matters: Launches often ship staging settings to production. See the earlier section on this topic for common problems.
How to verify: Crawl production immediately after launch and compare against the final staging crawl.
How SiteAuditLint helps: it checks launch day across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
First Week Monitoring
What to check:
- Monitor indexing. Search Console coverage trends upward.
- Monitor 404s. New 404s are fixed or redirected.
Why it matters: SEO issues often appear days after a change, as search engines recrawl. Ongoing monitoring catches drops in indexing and traffic before they become expensive.
Common problems:
- No baseline to compare against
- Traffic drops noticed weeks late
- New 404s from old backlinks going unfixed
- Index coverage declining unnoticed
How to fix it: Schedule recurring crawls, set alerts for indexability and status code changes, and review Search Console coverage and performance weekly.
How to verify: Compare scheduled crawl results and Search Console trends against the pre change baseline.
Learn more: Scheduled SEO audits, Slack SEO alerts, Site health score.
How SiteAuditLint helps: it checks first week monitoring across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Common mistakes
Leaving staging noindex or Disallow: / in production
Canonical tags still pointing to the staging domain
No redirects from the old site's URLs
Launching without analytics or Search Console
Not crawling production immediately after go live
When to run the checklist
- Two weeks before launch, on staging
- On launch day
- In the first week after launch
- When launching a new section or subdomain
How to verify fixes
Save a baseline crawl before you change anything. Fix high-priority and template-level issues first, since one template fix resolves many URLs, then re-crawl with the same start URL and settings and compare the two audits with audit comparison. Finally, confirm important pages in Search Console with URL Inspection. See how to prioritize audit findings.
SiteAuditLint workflow
Most checks in this list run automatically in a SiteAuditLint crawl. Use audit comparison to diff crawls and scheduled audits to monitor for regressions.
All SEO checklists
See the full checklist library, with a guide to choosing the right checklist for each job.