What is SEO Preservation (Migration)?

SEO Preservation is the discipline of protecting a website's organic search traffic, indexed URLs, link equity, and keyword rankings during a migration — whether that's a CMS swap, domain change, URL restructure, or full redesign. Google's own documentation warns that migrations can cause temporary ranking drops of 10–30% even when done correctly, and permanent losses when done poorly. The practice involves building a complete redirect map from old URLs to new ones, preserving on-page signals (title tags, headings, internal links), maintaining XML sitemaps, and monitoring crawl behavior post-launch. We've shipped this on 50+ migration projects — moving sites from WordPress to Next.js, Drupal to Astro, and legacy platforms to headless architectures. A typical SEO Preservation plan starts 8–12 weeks before launch and extends monitoring for 90 days after.

How it works

SEO Preservation follows a structured sequence across three phases: pre-migration, launch, and post-migration.

Pre-migration (8–12 weeks out):

Full crawl audit. Use Screaming Frog or Sitebulb to crawl every indexable URL. Export the complete URL list with status codes, canonical tags, and meta data.
Redirect map. Build a 1:1 mapping of every old URL to its new equivalent. This is the single most important artifact. We store ours in a shared Google Sheet with columns for old URL, new URL, redirect type (almost always 301), and verification status.
Baseline metrics. Snapshot Google Search Console data: impressions, clicks, average position per page. Record Ahrefs or Semrush domain rating and backlink counts.
Content parity check. Ensure title tags, H1s, and body content on new pages match or improve on the originals. Changing content and URLs simultaneously is a common mistake.

Launch day:

# Example nginx redirect block from map file
map $request_uri $new_uri {
  /old-blog/post-slug  /blog/post-slug;
  /services/old-name   /services/new-name;
}

server {
  if ($new_uri) {
    return 301 $new_uri;
  }
}

Deploy redirects, submit the updated XML sitemap in Google Search Console, and request indexing for high-priority pages. Remove any noindex tags that were used on staging.

Post-migration (90 days):

Monitor Search Console for crawl errors, 404 spikes, and indexing drops daily for the first two weeks, then weekly. Compare traffic and ranking baselines at 30, 60, and 90 days.

When to use it

Every migration needs an SEO Preservation plan. Full stop. But some scenarios demand more rigor than others.

High priority:

CMS platform changes (e.g., WordPress to Next.js/Astro)
Domain name changes or merging multiple domains
URL structure overhauls (e.g., removing /category/ from paths)
HTTP to HTTPS migrations (less common now, but still happens)
International site restructures (subfolder to subdomain or vice versa)

Lower priority (but still do it):

Visual redesigns where URLs stay the same
Adding new pages without removing old ones

When NOT to skip it:

Never. We've seen agencies treat migration as purely a dev task and watch clients lose 60% of organic traffic overnight. Even a "simple" redesign can break internal linking patterns enough to tank rankings.

SEO Preservation vs alternatives

There's no real "alternative" to SEO Preservation — you either do it or you accept traffic loss. But here's how it relates to adjacent concepts:

Concept	Scope	Relationship to SEO Preservation
Redirect Map	Individual artifact	A component of SEO Preservation — the URL-to-URL mapping document
301 Redirect	Technical mechanism	The HTTP status code used to implement the redirect map
CMS Migration	Project type	The event that triggers SEO Preservation work
Technical SEO Audit	Ongoing practice	Pre-migration audit is one input; post-migration audit validates success
Content Migration	Content transfer	Parallel workstream — moving copy, images, and metadata to the new platform

SEO Preservation is the umbrella process. The redirect map is its most critical deliverable. A CMS migration without SEO Preservation is just a rebuild with amnesia.

Real-world example

A B2B SaaS company migrated from a legacy WordPress multisite to a headless Astro + Sanity CMS setup. The site had 4,200 indexed pages and ~180,000 monthly organic sessions. We started SEO Preservation work 10 weeks before launch: crawled all URLs with Screaming Frog, built a redirect map covering 3,800 URL changes (400 pages kept identical paths), and validated content parity across the top 200 traffic-driving pages. On launch day, we deployed redirects via Vercel's vercel.json config, submitted the new sitemap, and began daily monitoring. At 30 days, organic traffic was down 8%. At 90 days, it had recovered to 102% of the pre-migration baseline — the new site's improved Core Web Vitals (LCP dropped from 3.8s to 1.9s) contributed to the slight gain.

Frequently asked questions about SEO Preservation (Migration)

Is SEO Preservation the same as a redirect map?

No. A redirect map is one deliverable within SEO Preservation, but it's not the whole picture. SEO Preservation also includes content parity checks (ensuring title tags, H1s, and body copy carry over), XML sitemap updates, internal link audits, canonical tag validation, and 90 days of post-launch monitoring. Think of the redirect map as the most important single artifact, but the preservation process wraps around it with planning, validation, and recovery work. Skipping the surrounding steps and only deploying redirects is a common reason migrations still lose traffic.

When did SEO Preservation become standard practice?

The practice formalized around 2012–2014 as Google's algorithms became sophisticated enough that migrations caused measurable ranking disruption. Google published its official site move documentation in 2013 and has updated it multiple times since. The rise of headless CMS architectures around 2019–2021 — where front-end URLs almost always change — made SEO Preservation a non-negotiable part of any agency migration process. By 2024, most serious web agencies included it as a standard deliverable. Our own migration checklist has been through 12 revisions since 2020.

What's the alternative to SEO Preservation during a migration?

There isn't a legitimate alternative — there's only doing it well or doing it poorly. Some teams try to skip preservation work and rely on Google's ability to figure out the new site structure organically. This rarely works. Without 301 redirects, Google treats removed URLs as 404s and drops them from the index within weeks. Link equity from external backlinks evaporates. The closest thing to an 'alternative' is accepting the traffic loss and planning to rebuild organic authority from scratch, which typically takes 6–18 months depending on domain strength. That's not an alternative; it's a consequence.

How long does SEO recovery take after a migration?

With proper SEO Preservation, most sites see a 5–15% traffic dip in the first 2–4 weeks, followed by recovery to baseline within 60–90 days. Google has publicly stated that temporary fluctuations are normal during migrations. Without preservation work, recovery can take 6–18 months — or traffic may never fully return if high-authority backlinks pointed to URLs that now 404. The biggest factor in recovery speed is redirect accuracy: a 1:1 redirect map with correct destinations recovers faster than bulk redirects that send everything to the homepage. We monitor Search Console daily for the first 14 days and weekly through day 90.