This SOP provides a prioritized framework for launching a new website. It aggregates best practices from technical SEO, site architecture, and on-page optimization into a sequential execution list spanning Pre-Launch preparation, Launch Day execution, and Post-Launch monitoring.
Knowledge Base
📝 Context Summary
This SOP provides a prioritized framework for launching a new website. It aggregates best practices from technical SEO, site architecture, and on-page optimization into a sequential execution list spanning Pre-Launch preparation, Launch Day execution, and Post-Launch monitoring.
SOP: New Site Launch SEO Checklist
1. Overview
Launching a new website without a structured checklist is a primary cause of organic visibility failure. The technical decisions made in the first 30 days determine how quickly search engines discover, crawl, and index content.
This SOP sequences critical tasks across three phases: Pre-Launch (Foundation), Launch Day (Execution), and Post-Launch (Validation).
Epistemic Marker — Heuristic: Timelines below are standard for mid-sized sites. Complex enterprise migrations may require extended lead times.
2. Phase 1: Pre-Launch (2–4 Weeks Before Go-Live)
The Pre-Launch phase establishes the technical and strategic foundation. Errors here compound after launch.
2.1 Technical Infrastructure
Reference: Crawlability & Indexation
The pipeline is Crawl → Render → Index. Ensure bots can access the site.
- [ ] Clean Domain: Verify the domain has no spam history (use Ahrefs/Google Transparency Report).
- [ ] Enforce HTTPS: Ensure valid SSL and force 301 redirects from HTTP to HTTPS.
- [ ] Robots.txt: Allow crawling of public content. Note:
Disallowdoes NOT prevent indexing; usenoindextags for that. - [ ] XML Sitemap: Generate a clean sitemap excluding
noindex, redirects, and 404s. - [ ] Canonical Tags: Ensure every page has a self-referencing
rel="canonical"tag. (Ref: Site Migrations)
Reference: Page Speed & Core Web Vitals
Performance must be built-in, not retrofitted.
- [ ] Metrics: Target LCP < 2.5s, INP < 200ms, CLS < 0.1.
- [ ] Optimization: Compress images (WebP/AVIF), defer non-critical JS, and utilize a CDN.
2.2 Site Architecture & Content
Reference: Internal Linking & Keyword Research
Define the structure before writing content.
- [ ] Pillar-Cluster Map: Ensure pillars link to clusters, and clusters link back.
- [ ] Click Depth: Key pages must be within 3 clicks of the homepage.
- [ ] Intent Mapping: Assign every keyword an intent type (Info/Comm/Trans) and target URL.
- [ ] URL Hygiene: Use lowercase, hyphen-separated, descriptive URLs. No parameters.
2.3 On-Page & Data
Reference: Title Tags & Schema
Metadata is the first interaction with both users and AI agents.
- [ ] Title Tags: Front-load keywords, < 60 chars, 100% unique.
- [ ] Meta Descriptions: Active voice, implied CTA, < 160 chars.
- [ ] Structured Data: Implement JSON-LD for
Organization,WebSite, andArticle/Product.
2.4 Staging Audit (Crucial)
Crawl the staging site to verify:
– [ ] No broken internal links (404s).
– [ ] No redirect chains > 2 hops.
– [ ] Critical: Verify noindex tags are present on Staging but planned for removal on Production.
3. Phase 2: Launch Day Execution
Launch day is for execution, not experimentation. Verify these within 24 hours of go-live.
| Task | Detail |
|---|---|
Verify noindex Removal |
Critical Failure Point. Confirm no site-wide noindex remains in <head> or HTTP headers. |
| Submit Sitemaps | Submit production XML sitemap to Google Search Console and Bing Webmaster Tools. |
| Request Indexing | Manually request indexing for Homepage and Pillar pages via GSC Inspection Tool. |
| Verify Analytics | Confirm GA4/Tag Manager is firing. Broken tracking means lost baseline data. |
| Test Schema | Run priority pages through Google’s Rich Results Test. |
| Mobile Check | Verify rendering on mobile. Google uses mobile-first indexing. |
4. Phase 3: Post-Launch Monitoring (Days 1–90)
Transition from setup to validation.
4.1 Week 1: Crawl Validation
- Monitor GSC: Check “Pages” report for “Discovered – currently not indexed” spikes.
- Server Logs: Verify Googlebot is actively requesting pages.
- Fix 404s: Resolve any broken links immediately.
4.2 Weeks 2–4: Baselines
- Keyword Impressions: Monitor GSC Performance. Rankings will fluctuate (Sandbox effect).
- CWV Field Data: Check GSC Core Web Vitals report once data populates.
- Orphan Check: Re-crawl to ensure no pages were orphaned during launch.
4.3 Days 30–90: Growth
- Publishing: Begin regular cluster content updates to signal freshness.
- Link Building: Initiate digital PR or outreach to build initial domain authority.
- CTR Optimization: Refine titles/metas for high-impression/low-click pages.
5. Common Launch Failures
| Failure | Consequence | Prevention |
|---|---|---|
Staging noindex left on Prod |
Zero pages indexed. Complete invisibility. | Automate post-deploy check. |
| No XML Sitemap | Delayed discovery by weeks. | Submit immediately on launch. |
| Broken Canonicals | Indexing staging URLs or ignoring pages. | Crawl production within 24h. |
| No Redirect Plan | Loss of legacy link equity (if migration). | Test 301 map pre-launch. |
| Missing Analytics | No data for critical launch period. | QA tags in staging. |
6. Key Takeaways
- The Launch is a System: It is not a single event but a cycle spanning Pre-Launch preparation, Launch Day execution, and 90 days of Post-Launch monitoring.
- Technical Access is Foundational: If search engines cannot crawl, render, and index the site (Rule 2.1), no amount of content or link building will produce results.
- Architecture Before Content: Define the pillar-cluster structure and keyword-intent map before writing a single page to avoid costly restructuring later.
- Data Integrity: Ensure analytics and tracking are verified immediately upon launch to establish a reliable performance baseline.
Related Resources
- Technical Foundation: Crawlability & Indexation and Page Speed Optimization
- Site Architecture: Internal Linking Guide and Search Intent Mapping
- On-Page Execution: Title Tags & Meta Descriptions and Schema & Structured Data
- Content Strategy: Content Optimization Guide
- Crawlability
- Pillar-Cluster Architecture
- Schema Markup
- Staging Environment
Table of Contents
Knowledge
How To
Trending
- Crawlability
- Pillar-Cluster Architecture
- Schema Markup
- Staging Environment