Site Migration SEO: How to Preserve Rankings Through a Replatform

Replatforming is where ecommerce SEO goes to die. Stores that spent years building organic traffic frequently lose 20-40% of it in the months after switching from, say, Magento to Shopify Plus. Sometimes the traffic comes back. Sometimes it doesn't.

The good news: most of this loss is preventable. Replatforms that follow a discipline of URL preservation, 301 mapping, and post-launch monitoring often see zero or minimal traffic loss. Here's the playbook.

Pre-Migration (4-8 Weeks Before Launch)

1. Crawl the existing site comprehensively

Before you change anything, crawl your current site with a full URL inventory. You need every indexed URL, every URL that receives organic traffic, every URL with backlinks. Combine: sitemap export, Search Console URL inspection API or bulk export, and Ahrefs/Semrush top pages report for historical traffic data.

2. Identify high-value URLs

Not all URLs are equal. A product page getting 500 organic visits per month matters more than one getting 2. A URL with 40 referring domains matters more than one with 0. Tag each URL with: organic traffic, backlink count, revenue attribution (from analytics), and rank for its target keyword.

3. Plan your URL structure on the new platform

Where possible, keep identical URLs. Shopify → Shopify migrations are easiest (same URL structure). Cross-platform migrations (Magento → Shopify, WooCommerce → BigCommerce) usually require URL changes because each platform has different conventions for product URLs, collection URLs, and pagination.

4. Build the 301 redirect map

For every URL on the old site that can't be preserved, map it to its equivalent on the new site. Product pages → their equivalent product pages. Category pages → equivalent collection pages. Blog posts → equivalent posts. Edge cases: discontinued products map to the parent category, retired categories map to a related category, content no longer on the site maps to the most related page (not the homepage).

Technical Checklist (Launch Day)

5. Deploy all 301 redirects

Every old URL must return a 301 to the new URL on launch day. Not a 302. Not a 307. 301 is the only redirect that transfers PageRank. Verify every redirect in the map returns 301 status and that the destination URL returns 200.

6. Avoid redirect chains

Old URL → 301 → New URL. Not: Old URL → 301 → Intermediate → 301 → New URL. Every additional hop drops a percentage of link equity and increases latency.

7. Preserve your sitemap structure

Submit your updated sitemap to Search Console immediately. Keep the old sitemap URL returning a 301 to the new sitemap location.

8. Preserve canonical tags, hreflang, and meta robots

If your old site had canonical tags pointing to the primary product URL, the new site needs equivalent canonicals. Same for hreflang if you run multiple languages. Don't lose these in the rebuild.

9. Validate structured data

Your new platform's schema implementation is almost certainly different from your old one. Run Google's Rich Results Test on a sampling of product pages, collection pages, and blog posts immediately after launch. Fix any validation errors before Google's crawler finds them.

10. Set up real user monitoring on day 1

Core Web Vitals data in Search Console is a 28-day trailing window. If your new platform has worse CWV than your old one, you won't see the ranking impact for weeks. Install real user monitoring (CrUX API, Plausible, or similar) on launch day so you can see performance regressions immediately.

Post-Launch (First 4 Weeks)

11. Monitor crawl errors daily

Search Console will flood with new errors after a migration. 404s from URLs that didn't get mapped, redirect chains, server errors from increased load. Check daily for the first two weeks and fix immediately.

12. Track rankings on top URLs

Track the 100 highest-traffic URLs daily for the first month. Small dips are normal. Large sustained drops (>20% on a high-traffic URL after week 2) indicate something is wrong.

13. Request indexing on high-value URLs

Use Search Console's URL Inspection tool to request indexing of your top 50-100 URLs. Google's crawler will get to them eventually, but manual submission can cut re-indexing time from weeks to days.

14. Monitor Core Web Vitals

If your new platform is slower than your old one, you'll see it in CrUX data within 4 weeks. Have a performance optimization plan ready to deploy if needed.

15. Don't panic-change things

Traffic will fluctuate post-migration. Google needs 4-8 weeks to fully recrawl and re-rank after major site changes. Resist the urge to make additional changes during this period — they'll confuse the picture.

Common Migration Pitfalls

• Changing URLs for "cleaner SEO" — resist this. "URL structure best practices" never outweighs the ranking stability of preserving existing URLs.
• Not migrating the blog — a blog archive can be 40% of your organic traffic. Always migrate it with 301s.
• Losing hreflang on international sites — if you drop hreflang during migration, Google may start indexing the wrong country/language page.
• Forgetting image URLs — image search is a real traffic source. Redirect image URLs too, or at least preserve filenames.
• Dropping legacy redirects — if you had redirects from a previous migration, preserve them. Old URL → medium-old URL → current URL is fine; old URL → 404 is not.

After the Migration Settles

Run a StoreVitals scan two weeks after launch, four weeks after, and eight weeks after. Compare scores: your new site should match or exceed your old one's scores on all 5 pillars (SEO, Security, Performance, Accessibility, Content Quality). If any pillar regressed, address it systematically rather than waiting for rankings to drop.