SOP: New Site Launch SEO Checklist

SOP: New Site Launch SEO Checklist

1. Overview

Launching without a structured checklist is a leading cause of organic-visibility failure. The technical decisions made in the first weeks determine how quickly search engines discover, crawl, and index the site.

This SOP sequences critical tasks across three phases: Pre-Launch (foundation), Launch Day (execution), and Post-Launch (validation).

Heuristic: The timelines below suit mid-sized sites. Complex enterprise migrations may need extended lead times.

2. Phase 1 — Pre-Launch (2–4 weeks before go-live)

Establish the technical and strategic foundation. Errors here compound after launch.

2.1 Technical infrastructure

Reference: Crawlability & Indexation. The pipeline is Crawl → Render → Index — make sure bots can reach the site.

  • [ ] Clean domain: verify no spam history (Ahrefs / Google Transparency Report).
  • [ ] Enforce HTTPS: valid SSL, with 301 redirects from HTTP to HTTPS.
  • [ ] Robots.txt: allow crawling of public content. Disallow does not prevent indexing — use noindex for that.
  • [ ] XML sitemap: generate a clean sitemap excluding noindex pages, redirects, and 404s.
  • [ ] Canonical tags: every page has a self-referencing rel="canonical".

Reference: Page Speed & Core Web Vitals. Performance must be built in, not retrofitted.

  • [ ] Targets: LCP < 2.5s, INP < 200ms, CLS < 0.1.
  • [ ] Optimization: compress images (WebP/AVIF), defer non-critical JS, use a CDN.

2.2 Site architecture & content

Reference: Internal Linking & Keyword Research. Define the structure before writing content.

  • [ ] Pillar-cluster map: pillars link to clusters, and clusters link back.
  • [ ] Click depth: key pages within 3 clicks of the homepage.
  • [ ] Intent mapping: assign every keyword an intent type (Info / Comm / Trans) and a target URL.
  • [ ] URL hygiene: 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 answer engines.

  • [ ] Title tags: front-load keywords, < 60 chars, 100% unique.
  • [ ] Meta descriptions: active voice, implied CTA, < 160 chars.
  • [ ] Structured data: JSON-LD for Organization, WebSite, and Article/Product.

2.4 Staging audit (crucial)

Crawl the staging site to verify:

  • [ ] No broken internal links (404s).
  • [ ] No redirect chains longer than 2 hops.
  • [ ] noindex tags present on staging but flagged for removal on production.

3. Phase 2 — Launch Day

Launch day is for execution, not experimentation. Verify 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 the production XML sitemap to Google Search Console and Bing Webmaster Tools.
Request indexing Manually request indexing for the homepage and pillar pages via the 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 — indexing is mobile-first.

4. Phase 3 — Post-Launch Monitoring (days 1–90)

Transition from setup to validation.

4.1 Week 1 — crawl validation

  • Monitor GSC: watch the Pages report for “Discovered – currently not indexed” spikes.
  • Server logs: confirm Googlebot is actively requesting pages.
  • Fix 404s: resolve broken links immediately.

4.2 Weeks 2–4 — baselines

  • Impressions: monitor GSC Performance; rankings will fluctuate early on.
  • CWV field data: check the 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 updates to signal freshness.
  • Link building: start digital PR or outreach to build initial authority.
  • CTR optimization: refine titles and metas for high-impression, low-click pages.

5. Common launch failures

Failure Consequence Prevention
Staging noindex left on production Zero pages indexed; total invisibility. Automate a post-deploy check.
No XML sitemap Discovery delayed by weeks. Submit immediately on launch.
Broken canonicals Staging URLs indexed, or pages ignored. Crawl production within 24h.
No redirect plan Loss of legacy link equity (on migrations). Test the 301 map pre-launch.
Missing analytics No data for the critical launch window. QA tags in staging.

6. Key takeaways

  1. The launch is a system — not a single event, but a cycle spanning Pre-Launch prep, Launch Day execution, and 90 days of monitoring.
  2. Technical access is foundational — if engines cannot crawl, render, and index the site (2.1), no amount of content or link building will help.
  3. Architecture before content — define the pillar-cluster structure and keyword-intent map before writing a page, to avoid costly restructuring.
  4. Data integrity — verify analytics and tracking immediately at launch to establish a reliable baseline.
This entry was posted in . Bookmark the permalink.
Adam Bernard