Pre-Launch SEO Checklist: 52 Critical Checks Before Going Live
Moderate 20 min 2026-03-20

Pre-Launch SEO Checklist: 52 Critical Checks Before Going Live

Quick Summary

  • What this covers: Prevent catastrophic indexing issues and ranking failures with comprehensive pre-launch SEO validation. Technical audit framework for new sites.
  • Who it's for: site owners and SEO practitioners
  • Key takeaway: Read the first section for the core framework, then use the specific tactics that match your situation.

Pre-launch SEO audits prevent disasters that take months to fix. A site launching with noindex meta tags on all pages remains invisible in search for weeks before discovery. Incorrect canonical tags consolidate months of content to wrong URLs. Missing robots.txt files block Googlebot from entire sections. These failures occur during 40% of website launches when teams skip systematic validation.

The financial impact compounds daily. An e-commerce site losing 60 days of organic visibility during peak season sacrifices $180K in potential revenue at $3K daily averages. B2B sites delay lead generation 8-12 weeks while fixing indexing issues that pre-launch checks would catch in 4 hours. Systematic pre-launch validation trades 4-8 hours of audit time for months of ranking acceleration.

Technical Infrastructure Validation

SSL certificate installation prevents "Not Secure" warnings that Google penalizes. Modern browsers display security warnings on HTTP sites, increasing bounce rates 42% versus HTTPS equivalents. Verify:

# Test SSL installation
curl -I https://www.example.com | grep "HTTP/"
# Should return: HTTP/2 200

# Check certificate validity
openssl s_client -connect example.com:443 -servername example.com
# Verify: Verification: OK

HTTPS redirect from HTTP to HTTPS versions prevents duplicate content:

# .htaccess redirect
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

Test all HTTP URLs redirect properly. Missing redirects split ranking signals between HTTP and HTTPS versions.

WWW vs. non-WWW consistency prevents duplication. Choose preferred version:

# Redirect non-WWW to WWW
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L]

# OR redirect WWW to non-WWW
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ https://%1/$1 [R=301,L]

Google Search Console requires specifying preferred domain. Ensure redirects match preference.

DNS and Domain Configuration

DNS propagation complete before launch prevents accessibility issues. Check from multiple locations:

# Query DNS from different resolvers
dig @8.8.8.8 example.com
dig @1.1.1.1 example.com

# Verify A record points to correct IP
nslookup example.com

DNS propagation takes 24-48 hours globally. Launch after confirming propagation complete across major resolvers.

Domain age consideration: New domains face "sandbox" periods where rankings develop slowly over 3-6 months. If possible, register domains 3+ months before launch. Aged domains (1+ years) rank faster than week-old domains.

Subdomain vs. subdirectory strategy affects authority transfer. Subdirectories (example.com/blog) inherit domain authority. Subdomains (blog.example.com) build authority separately. Prefer subdirectories unless technical requirements necessitate subdomains.

Indexing Controls Verification

Robots meta tag audit catches accidental noindex directives:

# Scan all pages for noindex
curl -s https://example.com | grep -i "noindex"

# Better: crawl entire site with Screaming Frog
# Filter by: Meta Robots 1 > "noindex"

Common mistake: Developers add noindex during staging, forget removal before launch. Every page should either allow indexing or intentionally block it—no accidents.

Robots.txt validation ensures crawler access:

# Check robots.txt exists and content
curl https://example.com/robots.txt

# Verify critical paths allowed
User-agent: *
Allow: /
Sitemap: https://www.example.com/sitemap.xml

Critical checks:

Google Search Console verification enables monitoring:

  1. Add property (www vs. non-WWW matching redirect strategy)
  2. Verify ownership (HTML file, meta tag, or DNS)
  3. Submit XML sitemap
  4. Set international targeting if applicable

XML Sitemap Generation

Comprehensive sitemap includes all indexable URLs:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/</loc>
    <lastmod>2026-02-08</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://www.example.com/about/</loc>
    <lastmod>2026-02-05</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Sitemap requirements:

Sitemap submission via Search Console and robots.txt:

  1. Upload sitemap.xml to root directory
  2. Add to robots.txt: Sitemap: https://www.example.com/sitemap.xml
  3. Submit via Search Console Sitemaps tool
  4. Monitor for errors (404s, blocked URLs, redirects)

URL Structure and Redirects

Clean URL format follows SEO best practices:

Good: https://example.com/products/blue-widget
Bad:  https://example.com/products.php?id=123&cat=widgets

301 redirects for redesigns preserve authority from old URLs:

# Redirect old URL structure to new
Redirect 301 /old-page.html https://example.com/new-page/
Redirect 301 /products.php?id=123 https://example.com/products/widget-123/

Create comprehensive redirect mapping:

  1. Export URLs from old site
  2. Map to equivalent new URLs
  3. Implement 301 redirects
  4. Test sample URLs verify redirects
  5. Monitor 404 errors post-launch

Trailing slash consistency prevents duplicate content:

# Redirect without trailing slash to with slash
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ https://example.com/$1/ [R=301,L]

# OR redirect with slash to without
RewriteCond %{REQUEST_URI} (.*)/$
RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]

Choose one format. Google treats /products and /products/ as separate URLs without redirects.

Canonical Tag Implementation

Self-referencing canonicals on all pages prevent accidental duplication:

<link rel="canonical" href="https://www.example.com/page-url/" />

Canonical rules:

Parameter handling for filtered/sorted views:

<!-- Base product page -->
<link rel="canonical" href="https://example.com/products/widget/" />

<!-- Sorted view canonicalizes to base -->
<!-- URL: /products/widget/?sort=price -->
<link rel="canonical" href="https://example.com/products/widget/" />

Mobile Optimization Verification

Viewport meta tag presence on all templates:

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=5">

Missing viewport tags cause mobile rendering failures—pages render at desktop widths requiring pinch-zoom.

Mobile-friendly test via Google's tool:

Responsive design validation across device types:

Mobile page speed meets Core Web Vitals:

Run PageSpeed Insights on mobile for 10+ important pages. Address critical issues before launch.

Mobile-First Indexing Readiness

Content parity between mobile and desktop:

Common failure: Desktop shows 2,000 words, mobile hides 1,200 words in accordions. Google indexes mobile version, losing 60% of content signals.

Structured data consistency across mobile and desktop:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Blue Widget",
  "offers": {
    "@type": "Offer",
    "price": "99.99"
  }
}

Validate both mobile and desktop versions include identical schema markup.

On-Page SEO Elements

Title tag optimization for all pages:

<title>Blue Widgets - Professional Grade Tools | Acme Industries</title>

Meta description on all pages:

<meta name="description" content="Shop professional-grade blue widgets with lifetime warranties. Free shipping on orders over $50. Industry-leading quality since 1985.">

Heading structure hierarchy:

Image optimization:

Internal Linking Architecture

Logical site hierarchy:

Anchor text optimization:

Orphan page detection:

# Crawl site with Screaming Frog
# Check "Orphan Pages" report
# Ensure no important pages lack internal links

Every page needs at least one internal link from another page. Orphan pages rely solely on sitemaps for discovery—weaker indexing signal.

Page Speed Optimization

Core Web Vitals targets:

Image optimization checklist:

JavaScript optimization:

CSS optimization:

Caching configuration:

# Browser caching headers
<IfModule mod_expires.c>
  ExpiresActive On
  ExpiresByType image/jpg "access plus 1 year"
  ExpiresByType text/css "access plus 1 month"
  ExpiresByType application/javascript "access plus 1 month"
</IfModule>

Performance Testing

Lighthouse audit on key pages:

Target 90+ performance scores. Address blocking issues:

WebPageTest from multiple locations:

Structured Data Implementation

Organization schema on homepage:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Industries",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://facebook.com/acmeindustries",
    "https://twitter.com/acmeindustries"
  ]
}

Breadcrumb schema on all pages:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem",
    "position": 1,
    "name": "Home",
    "item": "https://www.example.com"
  },{
    "@type": "ListItem",
    "position": 2,
    "name": "Products",
    "item": "https://www.example.com/products"
  }]
}

Product schema for e-commerce:

Article schema for blog posts:

Validation: Test all schema with Google Rich Results Test and Schema Markup Validator.

Analytics and Tracking Setup

Google Analytics 4 implementation:

Google Search Console setup complete:

Conversion tracking verified:

Tag Manager (optional but recommended):

Security and Legal Compliance

Privacy policy page created:

Terms of service for e-commerce/SaaS:

SSL certificate valid and properly configured:

GDPR compliance for EU visitors:

Pre-Launch Testing Protocol

Staging site indexing block:

<!-- Ensure this exists on staging, NOT production -->
<meta name="robots" content="noindex, nofollow">

Browser testing:

Device testing:

Link validation:

# Use broken link checker
wget --spider -r -o crawler.log https://example.com

# Or use online tool: brokenlinkcheck.com

Form testing:

Launch Day Checklist

Remove staging blocks:

Search Console submission:

Social media setup:

Monitoring setup:

FAQ

How long before Google indexes a new site?

New sites typically see initial indexing within 3-7 days after sitemap submission. However, comprehensive indexing of all pages takes 2-4 weeks. Established domains launching new sections index faster (1-3 days) than brand new domains. Submitting URLs via Search Console URL Inspection tool expedites individual page indexing to 24-48 hours.

Should I launch with minimal content or wait for full inventory?

Launch with at least 20-30 pages of quality content. Thin sites (5-10 pages) struggle gaining traction. E-commerce sites should launch with 50+ products minimum. Each week of delay costs potential ranking progress—Google needs time building authority. Launch with viable inventory, add more post-launch. Delaying 6 months for perfect inventory wastes 6 months of aging advantage.

Can I launch without a blog or is it required?

Blogs aren't required for rankings but accelerate authority building. Service-based businesses benefit significantly from content marketing. E-commerce sites less so if product pages provide comprehensive information. Prioritize launching core pages (services, products, about, contact) first. Add blog 1-2 months post-launch once traffic patterns stabilize. Never delay launch waiting for blog content.

What happens if I launch with technical SEO issues?

Recovery time varies by severity. Noindex on all pages: fix immediately, 2-3 weeks for reindexing. Incorrect canonicals: 4-6 weeks sorting duplicate content. Broken redirects: 1-2 weeks after fixes. Severe issues delay ranking momentum 8-12 weeks versus clean launches. Prevention via pre-launch audit eliminates these delays. Fixing takes same effort whether pre-launch or post-launch, but post-launch costs ranking opportunity.

Should I wait for perfect PageSpeed scores before launching?

No. Target passing Core Web Vitals (LCP <2.5s, FID <100ms, CLS <0.1) rather than perfect scores. Score 70-80 with passing CWV sufficient for launch. Delaying launch for 95+ scores provides minimal benefit. Post-launch optimization continues—launch when CWV passes and no blocking technical issues exist. Month-long optimization marathons for perfect scores waste valuable aging time.

When This Fix Isn't Your Priority

Skip this for now if:

Frequently Asked Questions

How long does this fix take to implement?

Most fixes in this article can be implemented in under an hour. Some require a staging environment for testing before deploying to production. The article flags which changes are safe to deploy immediately versus which need QA review first.

Will this fix work on WordPress, Shopify, and custom sites?

The underlying SEO principles are platform-agnostic. Implementation details differ — WordPress uses plugins and theme files, Shopify uses Liquid templates, custom sites use direct code changes. The article focuses on the what and why; platform-specific how-to links are provided where available.

How do I verify the fix actually worked?

Each fix includes a verification step. For most technical SEO changes: check Google Search Console coverage report 48-72 hours after deployment, validate with a live URL inspection, and monitor the affected pages in your crawl tool. Ranking impact typically surfaces within 1-4 weeks depending on crawl frequency.

This is one piece of the system.

Built by Victor Romo (@b2bvic) — I build AI memory systems for businesses.

See The Full System View Repo
← All Fixes