Technical SEO & GEO

How to Plan an SEO-Safe 5,000+ URL Migration

Use 19 non-traffic SEO key results across 4 gated phases. Protect rankings, indexation, redirects, and AI Overview visibility during a CMS move.

Published Updated 3 min read

Many enterprise CMS migrations fail because teams only check organic traffic after launch. Before a 5,000+ URL move to Adobe Experience Manager (AEM) for a national FMCG brand, I built a gated technical SEO migration plan with 19 non-traffic key results across 4 phases. That structure protected 82.5% branded share of voice, as detailed in the Danone AQUA case study.

Why Non-Traffic OKRs Protect Enterprise Migrations

Organic traffic is a lagging signal. By the time GA4 shows a 30% drop, Googlebot has already crawled broken 301 chains, wrong canonical tags, or empty client-side shells. Non-traffic key results act as pass or fail release gates that engineers and writers can verify before cutover.

AEM Technical Risks to Check Before Launch

  • AEM Dispatcher caching: confirm Dispatcher does not cache 404 responses, redirect loops, or missing trailing slashes.
  • Apache Sling URL mapping: map legacy paths to clean canonical URLs without exposing /content/brand/en/ internal repository paths.
  • DAM asset paths: preserve image filenames, alt text fields, and WebP delivery so image search equity does not reset.
  • Server-side HTML rendering: confirm primary copy, internal links, and JSON-LD render in raw HTML without waiting for client scripts.

The 19 Non-Traffic Key Results Across 4 Gated Phases

Phase 1: Baseline and URL Inventory (5 Key Results)

  • KR 1: 100% of indexed URLs, sitemap URLs, and top GA4 landing pages exported into one master inventory.
  • KR 2: 100% of top 200 revenue and traffic URLs mapped to exact 1-to-1 destination paths.
  • KR 3: Branded share of voice benchmark locked (target 70%+, held at 82.5%).
  • KR 4: Baseline crawl of titles, meta descriptions, H1s, canonicals, and JSON-LD archived for diffing.
  • KR 5: Core Web Vitals baseline (LCP, INP, CLS) recorded per page template.

Phase 2: Staging Parity Gate (5 Key Results)

  • KR 6: 0 redirect chains or loops across all 5,000+ redirect rules (100% one-hop 301 pass rate).
  • KR 7: 100% of staging templates render self-referencing HTTPS canonicals with consistent trailing slashes.
  • KR 8: 0 accidental noindex tags or robots.txt blocks left in production config templates.
  • KR 9: Automated XML sitemaps exclude 404, 301, and noindex URLs.
  • KR 10: 100% JSON-LD schema parity verified with zero syntax errors.

Phase 3: Cutover and 48-Hour Indexation Gate (5 Key Results)

  • KR 11: 0 HTTP 5xx server errors on robots.txt, sitemaps, and top 500 landing pages.
  • KR 12: New XML sitemaps submitted in Google Search Console and Bing Webmaster Tools within 2 hours of launch.
  • KR 13: 98%+ of legacy URLs resolve in one 301 hop with zero soft-404 spikes.
  • KR 14: Internal link crawl confirms 0 broken internal links pointing to old paths.
  • KR 15: Mobile and desktop Core Web Vitals stay within Good thresholds after Dispatcher cache warm-up.

Phase 4: Transactional and AI Search Growth (4 Key Results)

  • KR 16: Indexation parity reaches 95%+ of target canonical URLs within 30 days.
  • KR 17: Priority promo and product clusters updated with clear answer-first headings and internal links.
  • KR 18: Brand AI Overviews retained across all core brand queries (7 of 7 won).
  • KR 19: AI share of voice tracked monthly across Google AI Overviews, ChatGPT, and Perplexity.

Frequently asked questions

Why track non-traffic key results during a site migration?

Non-traffic checks catch broken redirects, wrong canonicals, and missing schema before rankings and organic visits drop.

How does AI search visibility (GEO) fit into a migration?

Clean static HTML, valid schema, and clear headings help Google AI Overviews, ChatGPT, and Perplexity keep citing your pages after the platform move.

Written by · Indonesia (Hybrid / Remote)

Tito Azizul Faiz

SEO and GEO strategist who builds Search Console tools. Creator of gsc-extended.