Ecommerce Site Migration SEO Checklist: Don't Lose Your Rankings

Platform migrations are some of the highest-stakes events in ecommerce. Move from Magento to Shopify, WooCommerce to BigCommerce, or even a major theme redesign — one missed step can wipe out years of organic traffic overnight. Google has confirmed that every migration carries inherent risk, but a methodical approach minimizes the damage.

This checklist covers everything from pre-migration planning to post-launch monitoring. Follow it step-by-step.

Before the Migration

1. Crawl and Document Your Current Site

Before touching anything, create a complete snapshot of your current state. Crawl every URL, record all title tags, meta descriptions, canonical tags, and internal link structures. Export your sitemap. This becomes your baseline — everything post-migration gets compared against it.

2. Export Your URL Map

Create a complete spreadsheet mapping every old URL to its new URL. This includes product pages, category pages, blog posts, policy pages, and any custom landing pages. This map drives your redirect plan. Miss a URL and you create a 404 that Google will index.

3. Identify Your Top Traffic Pages

Pull your Google Analytics and Search Console data. Identify the top 100 pages by organic traffic and the top 50 by backlink count. These pages get extra attention — verify their redirects, meta tags, and content are preserved exactly. Losing a page that drives 500 visits/month is more damaging than losing one that drives 5.

4. Benchmark Your Current Metrics

Record your current organic traffic, top keyword rankings, Core Web Vitals scores, and conversion rates. You need these numbers to detect regression after launch. Without a baseline, you can't distinguish normal fluctuation from migration damage.

5. Plan Your 301 Redirect Map

Every old URL that changes must have a 301 redirect to its new equivalent. Not a 302 (temporary) — a 301 (permanent). Google passes roughly 95-99% of link equity through a 301. Use your URL map from step 2. Test redirects in staging before going live.

During the Migration

6. Implement All 301 Redirects First

Before flipping DNS or going live, have every redirect in place and tested. Use server-level redirects (not JavaScript redirects) for maximum SEO benefit. Verify that redirect chains don't exceed 2 hops — consolidate any chains into direct redirects.

7. Preserve Meta Tags and Structured Data

Title tags, meta descriptions, Open Graph tags, and JSON-LD structured data must match or improve upon the old versions. Don't let the new platform auto-generate generic titles. Manually map your top 100 pages' meta tags. For the rest, ensure your template generates equivalent output.

8. Keep Your URL Structure as Similar as Possible

If your old product URLs were /products/blue-widget and your new platform uses /shop/blue-widget, that's a URL change that requires a redirect. The closer your new URL structure matches the old one, the fewer redirects you need and the less risk you carry. Some platforms let you customize URL patterns — use this.

9. Migrate Internal Links

Don't rely on redirects for internal navigation. Update all internal links in your content, navigation, and footer to point to the new URLs directly. Redirects add latency and signal to Google that the link is stale. Internal links should always point to the canonical, final URL.

10. Update Your Sitemap

Generate a new sitemap.xml with all new URLs and submit it to Google Search Console immediately after launch. Also keep the old sitemap available temporarily — Google will use it to discover the redirects and update its index faster.

After the Migration

11. Submit New Sitemap to Search Console

Go to Google Search Console → Sitemaps → Submit your new sitemap URL. Also use the "Request Indexing" feature on your most important pages to accelerate re-crawling. Google typically takes 1-4 weeks to fully re-index a migrated site.

12. Monitor 404 Errors Daily

Check Search Console's Coverage report and your server logs for 404 errors. Every 404 is a missed redirect — fix them immediately. The first two weeks after migration are critical. New 404s appearing means your redirect map had gaps.

13. Track Rankings and Traffic Weekly

Compare your post-migration organic traffic against your baseline. A temporary dip of 10-20% is normal and typically recovers within 2-4 weeks. A sustained drop of 30%+ after 4 weeks indicates a problem — usually missing redirects, changed meta tags, or canonical issues.

14. Run a Full Health Scan

After migration, run a comprehensive health scan to catch any issues the manual checklist missed. Check for broken links, missing images, security header changes, and accessibility regressions. Automated tools catch things that manual reviews miss.

Common Migration Mistakes

• Using 302 redirects instead of 301s — 302s don't pass full link equity
• Forgetting image URLs — if your image hosting changes, all image URLs in Google Image Search break
• Not redirecting pagination pages — /category?page=2 often gets forgotten
• Changing robots.txt too aggressively — accidentally blocking sections of the new site
• Losing hreflang tags — international stores must preserve language/region signals

StoreVitals can run a full health scan on your new store immediately after migration, catching broken links, missing meta tags, redirect chains, and 15+ other issues. Run a free migration audit to verify your migration didn't leave anything behind.