The SEO Migration Checklist: How to Redesign or Replatform Without Losing Traffic

Why Preparation Beats Panic During a Site Migration

You are about to redesign, move from WordPress to Shopify, or finally retire that old domain, and somewhere in the back of your head is the question nobody wants to say out loud: what if I lose all my traffic?

Fair worry. Migrations are the single most common cause of sudden, scary drops in organic traffic that I see. But here is the part most people get wrong. A short dip right after launch is normal, even expected, while Google re-crawls and re-maps everything. A permanent collapse is not. The difference between the two is almost always preparation. So here is the SEO migration checklist I actually run, phase by phase, with the mistakes that quietly kill rankings called out along the way.

Not All Migrations Carry the Same Risk

Before you touch anything, figure out what kind of move you are making. The word "migration" covers five very different levels of danger, and treating a simple reskin like a domain change (or the reverse) is how people get hurt.

• Redesign on the same URLs. Lowest risk. The addresses stay put, so you are mostly protecting your on-page content and page speed. Still easy to botch if the new template strips your headings or your copy.
• Platform change (WordPress to Shopify, say). Medium to high. New platforms impose new URL patterns, and Shopify in particular loves to bolt /products/ and /collections/ onto everything. Your redirect map carries the whole thing.
• URL structure change. High. You are moving content to new addresses on the same domain. Every old URL needs a home.
• Domain migration. The highest everyday risk. You are asking Google to transfer trust, history, and rankings from one hostname to another. Domain migration SEO lives or dies on clean 301s and a Change of Address request.
• HTTP to HTTPS. Usually low, and worth doing regardless. Google has treated HTTPS as a ranking signal since 2014. Just redirect every HTTP URL to its HTTPS twin and update internal links.

If you are consolidating a subdomain into your main domain, treat it with domain-change seriousness. It feels small. It is not.

The Pre-Launch Checklist: Do This Before You Build Anything

This is where the real work lives. It is not glamorous. It is also the only part that reliably protects your organic traffic, so do it heads-down and do it completely.

1. Benchmark first. Export your current rankings, top landing pages, and traffic from Google Search Console and your analytics before you change a thing. You cannot tell whether a migration worked if you never wrote down where you started. Good measurement is comparative.
2. Build a full URL inventory. Pull every URL from four sources and merge them: a fresh crawl, Search Console's Pages report, analytics, and your backlink profile. Four sources, because every one of them misses pages the others catch.
3. Map redirects 1:1. Every old URL points to its closest matching new URL. Not the homepage. The closest equivalent page. This map is the heart of any site migration checklist, and it is the thing I build first.
4. Preserve what ranks. Carry over your titles, meta descriptions, H1s and H2s, and the actual body content. Website redesign SEO goes sideways when a new template "cleans up" the copy that was earning the rankings in the first place.

Those four are the backbone: measure, inventory, map, preserve. The last three are housekeeping, the kind of thing that leaves no footprints to sink you later.

5. Carry the schema over. Product, Article, FAQ, Breadcrumb, whatever you have. New platforms rarely reproduce it automatically.
6. Set staging to noindex. Your staging site should be blocked from indexing the entire time it exists. More on why forgetting to lift this is catastrophic in a minute.
7. Test the redirects on staging. Run your redirect rules against the real old-URL list before launch. If you are working in Apache, generating the rules cleanly beats hand-editing a 400-line htaccess file at midnight.

The redirect map is not a launch-day task. It is the thing you build before anyone picks a theme.

Launch Day and the First Eight Weeks

Launch day is mechanical if the prep is done. Work the list in order.

Launch day

1. Push your 301 redirects live. Permanent, not 302. The 301 Moved Permanently status is what tells Google to pass signals and swap the indexed URL.
2. Remove the noindex from the live site. Check this twice.
3. Update and submit your XML sitemap with only the new, final URLs.
4. For a domain move, file Change of Address in Search Console. Google's own site move documentation is the authoritative playbook here, and it is worth reading in full before you flip the switch.
5. Verify robots.txt is not blocking anything it should not.
6. Update internal links to point at final URLs directly, not through a redirect. Links that hop through a 301 waste crawl budget and slow things down.
7. Spot-check your top ten pages by hand. Load them. Confirm the redirect, the content, the title.

Weeks one through eight

Migrations recover over weeks, not hours. Watch, do not panic.

• Monitor Search Console's coverage and crawl stats for spikes in errors.
• Pull a 404 report and fix every stray one. A proper custom 404 page softens the ones you miss, but the goal is to miss none.
• Compare rankings and traffic against your benchmark, under the same conditions.
• Hunt down redirect chains (A to B to C) and flatten them to single hops. You can confirm each one resolves cleanly with a quick status check, and validate the new sitemap with a sitemap validator so Google is reading exactly the URLs you intend.
• Keep the old domain and its redirects live long term. Google's John Mueller has said to hold redirects for at least a year. I keep mine longer, because backlinks do not expire on a schedule.

The Mistakes That Actually Kill Traffic

I have watched these play out across real domain and Shopify migrations, and they are depressingly consistent. None of them are exotic. All of them are avoidable.

• Redirecting everything to the homepage. The classic. It feels tidy and it destroys your rankings, because Google treats a bulk redirect to one unrelated page as a soft 404 and passes almost nothing. One-to-one or nothing.
• Dropping content in the redesign. Those "thin" old blog posts you deleted were often the ones quietly ranking for long-tail terms. Audit before you prune.
• Losing internal links. New templates love to shed contextual links inside the body copy. That internal structure was feeding authority through your site.
• Forgetting images and PDFs. Image URLs and downloadable files need redirects too. They rank, they earn traffic, and they get stranded constantly.
• Launching with staging noindex still on. The one that empties a site from the index overnight. Lift it on launch day and verify it is gone.

How Google reads your 301s underpins all of this, and the official redirects and Search guidance is short enough to read twice.

When to Bring in an SEO, and the Mindset That Saves You

Here is the timing that matters most, so I will say it plainly: bring in an SEO before the redirect map is built, not after the traffic drops. Once rankings have fallen and the old URLs are gone, you are doing forensic recovery instead of prevention, and recovery is slower, uglier, and never fully complete.

The mindset shift is simple. A migration is not a design project with some SEO bolted on at the end. It is an SEO project that happens to involve a new design. Get the inventory, the redirect map, and the content preservation right, and a redesign or replatform costs you a brief dip and nothing permanent. That is not luck. It is just physics.

Your Next Step

Starting your inventory is the best thing you can do today. Run a site audit to see every URL and issue you are carrying into the move, then build your redirect map from that list before anyone touches a theme. Prep early, and the migration takes care of itself.