SEO Migration Guide – How to Re-platform your website CMS Without Losing Traffic

tl;dr: You can’t promise management zero traffic loss on a migration. You can protect the pages that make money, stagger the risky changes, and launch with new content that soaks up the volatility. Here’s how I do it.

Overview – CMS Migration

This one comes up on r/SEO almost every week. The most recent version, from u/EntrepreneurJolly231, went roughly like this:

Organic is close to half our online revenue, so management wants no traffic drop at all.

I’ve run more migrations than I can count. Replatforms, URL restructures, domain moves, CMS swaps. The good news: a few tweaks to your plan and you should be fine. The bad news: “no drop at all” is a business goal, not an SEO guarantee. Your job is to make the case for which pages actually matter, then protect those like your bonus depends on it. (It might.)

Step 1: Find your money pages with a SERP report

Before you touch a single URL, build a SERP report. Not a vanity rank tracker with 2,000 keywords. A short list of the terms that pay the bills.

Pick keywords that score high on both of these:

  • Intent. Commercial and transactional queries: “buy”, “pricing”, “near me”, “best X for Y”, product and category names.
  • CPC. Advertisers don’t pay high CPCs for keywords that don’t convert. A high CPC is a free signal that the keyword makes money.

Where both overlap, you’ve found your money keywords. Map each one to the page that ranks for it. Those pages are your migration watchlist. Benchmark their positions, clicks and conversions now, so you have a baseline when management asks “what happened?” the week after launch.

Step 2: Stagger the migration if URLs are changing

If your URLs are staying put, great. If they’re changing, don’t flip the whole site in one day.

A staggered (iterative) migration moves the site in phases. Each phase is small enough that you can:

  • See cause and effect. If rankings drop, you know which batch did it.
  • Roll back. One section is far easier to undo than an entire site.
  • Pause. If something weird happens, you stop and fix it before the next batch.

A one-day “big bang” migration mixes every possible issue into one giant blob. Then you spend a month guessing which one caused the drop.

Good to know about Site Migrations

Why do some sites’ traffic go up and some down? Weblinkr explains:

Zero-click pages (and why rankings often go up)

Open Search Console and count the pages with 0 clicks in the last 28 days. My working rule: 0 clicks in 28 days = little to no authority.

Here’s why that matters. Google recrawls and refreshes pages roughly in line with their authority. Low-authority pages get visited rarely, and small edits often aren’t enough to trigger a proper re-evaluation. So they sit there, stale, never re-indexed.

A platform migration changes that. The template, HTML and internal links all change at once, which is usually a big enough change to get those pages recrawled and re-evaluated.

And your site’s topical authority has almost certainly grown since those pages were last indexed. So when Google finally takes a fresh look, a lot of them rank better than before. That’s why sites often climb after a replatform. It’s a welcome surprise, but it’s not magic.

The catch: cannibalization and ranking waves

Those newly revived pages don’t land in an empty SERP. Pages that weren’t ranking (or weren’t competing for the same queries) can suddenly start fighting your money pages. That’s cannibalization, and it’s the main reason you keep your SERP report open every day after launch.

To reduce the risk:

  1. Force re-indexing early. Push your low-authority pages through recrawl before the main migration, so it happens as its own event.
  2. Watch it in isolation. If cannibalization shows up, you’ll see it clearly, instead of buried under a hundred other launch-day changes.
  3. Fix before you move on. Consolidate, redirect or re-target the overlapping pages, then start the next phase.

Expect fluctuations either way. The changes roll through the site like a wave: pages swap positions, rankings rise and drop, and every change has knock-on effects elsewhere. This is normal. Panicking and reverting things mid-wave usually makes it worse.

Protect your SEO Authority

Internal links carry authority, just like external ones. Everyone obsesses over backlinks during a migration and forgets that a new nav, footer or template can quietly cut off half the internal links to a page. Crawl the old site and the staging site, then compare internal links to your money pages.

Hold back your most-linked pages. Here’s a simple hedge: don’t change pages with lots of backlinks in the first phase. Push them out two or three weeks, once everything else has settled. If something breaks, it won’t be the pages carrying your link equity.

Publish HTML sitemaps ahead of time. I’m not talking about XML sitemaps. I mean real, crawlable HTML pages that link to your content. They spread authority and context across the site and give Google a clean path to your ranking pages. Depending on site size, that might be one sitemap or ten. Put them live before the migration, so they’re already doing their job when the changes land.

Fix 404s and broken links now. Don’t carry old mess into a new platform. Clear as many as you can before launch, so the only errors you see afterwards are new ones.

Pro tip: have launch-day content ready

This is the one most people miss. Plan a batch of low-to-medium KD content and publish it right after you go live. Low keyword difficulty means these pages can rank quickly. So while Google is recrawling the site and recalculating your authority, you’re picking up new keywords and new positions. Those gains offset the swings on your existing pages. Your overall visibility line stays flatter. And flat lines keep management calm.

Or try the 5-min PAA Hack from Edward Sturm

The Complate SEO CMS Migration Checklist

  • Build a SERP report of high-intent, high-CPC money keywords and benchmark them
  • Map each money keyword to its ranking page
  • Plan a staggered migration if URLs are changing
  • Count pages with 0 clicks in the last 28 days
  • Force re-indexing of low-authority pages before the main migration
  • Watch for cannibalization after each phase
  • Compare internal links to money pages, old site vs. new
  • Hold back heavily backlinked pages for 2 to 3 weeks
  • Publish HTML sitemaps ahead of launch
  • Fix 404s and broken links
  • Queue low/medium KD content for launch day

Printable SEO CMS Migration Checklist

he SEO Migration Checklist
# When Task Why it matters Done
1 Before migration Build a SERP report of high-intent, high-CPC money keywords and benchmark them Gives you a baseline for the pages that actually make money ☐
2 Before migration Map each money keyword to its ranking page Turns your keyword list into a page watchlist ☐
3 Before migration Plan a staggered migration if URLs are changing Lets you see cause and effect, pause, and roll back ☐
4 Before migration Count pages with 0 clicks in the last 28 days 0 clicks in 28 days = little to no authority ☐
5 Before migration Force re-indexing of low-authority pages Isolates re-indexing from the main migration ☐
6 Before migration Compare internal links to money pages, old site vs. new Internal links carry authority, just like external ones ☐
7 Before migration Publish HTML sitemaps Spreads authority and context to your ranking pages ☐
8 Before migration Fix 404s and broken links Don’t carry old mess into a new platform ☐
9 Launch day Publish queued low/medium KD content New rankings offset the swings while Google recrawls ☐
10 After each phase Watch for cannibalization Revived pages can start competing with your money pages ☐
11 2–3 weeks after launch Migrate heavily backlinked pages Protects your link equity until the site has settled ☐

Got a migration coming up? Bring your questions to r/SEO.

Hope that helps!