Ecommerce SEO Migration Checklist: 47 Steps to Protect Your Rankings

Ecommerce site migrations are where rankings go to die. I've seen businesses lose 60-80% of organic traffic overnight because someone skipped a redirect mapping spreadsheet or forgot to update canonical tags on the staging environment.

This is the checklist I use with every ecommerce migration. 47 steps, broken into phases. Miss any of them and you're gambling with revenue.

Phase 1: Pre-Migration Audit (Steps 1-15)

Before you touch a single line of code, you need a complete picture of what you're working with.

Crawl and Index Baseline

1. Full site crawl. Run Screaming Frog or Sitebulb on the current site. Export every URL with status codes, titles, meta descriptions, canonicals, and internal links.
2. Google Search Console export. Download all indexed pages, sitemaps, and coverage reports. This is your baseline.
3. Google Analytics landing page data. Export the last 12 months of organic landing page data. URLs, sessions, conversions, revenue.
4. Backlink profile. Pull your full backlink profile from Ahrefs or Majestic. You need to know which URLs have external links pointing to them.
5. Indexed page count. Run site:yourdomain.com and record the number. Compare with your crawl data to identify any gaps.

URL Mapping

6. Complete URL mapping spreadsheet. Every old URL mapped to its new URL. No exceptions. This is the single most important document in the entire migration.
7. Prioritise by traffic. Sort your URL map by organic traffic. Your top 100 pages need manual review. Automated mappings aren't good enough for pages generating revenue.
8. Handle discontinued products. Map old product URLs to the most relevant alternative product or parent category page. Never 301 to the homepage.
9. Map category structures. If you're restructuring categories, document every old category URL and its new equivalent. Check your ecommerce site architecture plan before mapping.
10. Identify URLs with backlinks. Cross-reference your backlink profile with your URL map. These pages need redirects that preserve link equity. No redirect chains, no 302s.

Technical Baseline

11. Document current robots.txt. Save a copy. You'll need to recreate the same crawl directives on the new platform.
12. Document current XML sitemaps. Note the structure, URL count, and any sitemap index files.
13. Record current page speed metrics. Core Web Vitals for your top 20 landing pages. You need a baseline to compare against post-migration.
14. Screenshot key pages. Take screenshots of your top 50 pages (desktop and mobile). Useful for debugging layout issues post-launch.
15. Document structured data. Catalogue all schema markup. Product, BreadcrumbList, FAQPage, Organisation. These need to be replicated on the new site.

Phase 2: Staging Environment (Steps 16-28)

Content and On-Page

16. Migrate all title tags. Don't let the new platform auto-generate titles. Import your existing, optimised title tags.
17. Migrate all meta descriptions. Same as above. Every custom meta description needs to transfer.
18. Migrate all H1 tags. Verify every page has one H1 and it matches your target keyword.
19. Migrate category descriptions. Category page content often gets lost in migrations. Export and re-import every word.
20. Migrate product descriptions. Verify no product descriptions were truncated or reformatted during import.
21. Migrate image alt text. Alt text frequently gets stripped during platform changes. Audit and reimport.
22. Check internal links. Run a crawl on staging to find any broken internal links caused by URL structure changes.

Technical Setup

23. Implement 301 redirects. Load your entire URL mapping as 301 redirects. Test every single redirect for your top 100 pages manually.
24. Configure canonical tags. Verify every page has the correct canonical URL. Watch for staging URLs accidentally set as canonical.
25. Set up XML sitemaps. Generate new sitemaps with correct URLs. Exclude noindexed pages, redirected URLs, and parameter variations.
26. Configure robots.txt. Replicate necessary crawl directives. Remove any staging-specific blocks before launch.
27. Implement structured data. Rebuild all schema markup. Validate with Google's Rich Results Test.
28. Verify hreflang tags. If you're running an international ecommerce setup, hreflang implementation is critical and frequently breaks during migrations.

Phase 3: Launch Day (Steps 29-37)

29. Remove staging noindex tags. This sounds obvious, but I've seen live sites running for weeks with noindex because someone forgot to flip the switch.
30. Verify DNS propagation. Confirm the domain resolves to the new server from multiple locations.
31. Force HTTPS. Ensure all URLs redirect to HTTPS. No mixed content warnings.
32. Test redirect chains. Spot-check 50+ redirects. Look for chains (old URL > intermediate URL > new URL) and fix them to single-hop 301s.
33. Submit new sitemap to Search Console. Upload immediately after launch. Request indexing for your top 20 pages.
34. Verify Search Console property. If your URL structure changed (e.g., subdomain to subfolder), you may need a new Search Console property.
35. Test all tracking codes. GA4, Google Tag Manager, conversion tracking. A migration is useless if you can't measure the results.
36. Test site search. Internal search is often overlooked. Make sure it works on the new platform.
37. Mobile check. Browse the new site on actual mobile devices. Not just Chrome DevTools. Real phones.

Phase 4: Post-Migration Monitoring (Steps 38-47)

38. Daily Search Console checks (week 1). Watch for crawl errors, coverage drops, and indexing issues.
39. Compare indexed page counts. Your indexed page count should stabilise within 2-4 weeks. A significant drop means redirects or canonicals are broken.
40. Monitor organic traffic daily. Compare against your pre-migration baseline. Some fluctuation is normal for 2-4 weeks.
41. Check Core Web Vitals. Compare against your pre-migration baseline. Platform changes often introduce performance regressions.
42. Audit 404 errors. Search Console will surface crawl errors within days. Fix any missing redirects immediately.
43. Verify backlink landing pages. Spot-check your top backlinked URLs to confirm they redirect correctly to relevant new pages.
44. Monitor rankings for top keywords. Track your top 50 keywords daily for the first month.
45. Check rendered pages. Use Google's URL Inspection tool to verify JavaScript rendering is working correctly on product and category pages.
46. Review server logs. Check Googlebot crawl patterns. Are they finding and crawling your important pages?
47. Set a 90-day review date. Full comparison of organic traffic, rankings, indexed pages, and Core Web Vitals against your pre-migration baseline.

Platform-Specific Gotchas

Shopify to Shopify Plus

URL structures usually stay the same, but watch for collection handle changes and Shopify's forced /collections/ and /products/ prefixes. Shopify's automatic redirects are limited. Bulk import your 301s via the admin or a redirect app.

WooCommerce to Shopify

The biggest risk is URL structure changes. WooCommerce allows custom permalink structures; Shopify enforces its own. Every URL will change. Your redirect mapping needs to be airtight. Check your Shopify SEO checklist before launch.

Magento to Any Platform

Magento's layered navigation creates thousands of indexed faceted URLs. When migrating away, you need to account for all those indexed filter pages in your redirect map, or explicitly noindex and deindex them before migration.

Frequently Asked Questions

How long does it take for organic traffic to recover after a migration?

A well-executed migration typically shows recovery within 4-8 weeks. Some sites recover faster, some take up to 12 weeks. If traffic hasn't recovered after 3 months, something is fundamentally broken. Usually redirects, canonicals, or missing content.

Should I migrate content and platform at the same time or separately?

Always separate them if you can. Migrate the platform first with identical content and URLs where possible. Once traffic stabilises, then restructure content. Changing two variables simultaneously makes it impossible to diagnose problems.

What's the most common ecommerce migration mistake?

Incomplete redirect mapping. Every time. Teams map the top 100 pages manually and automate the rest with pattern-based rules. But edge cases. Discontinued products, old blog URLs, renamed categories. Fall through the cracks and create hundreds of 404 errors that bleed link equity.

Can I do a migration without losing any traffic?

Realistically, expect a 10-20% temporary dip even with perfect execution. Google needs time to recrawl, reprocess redirects, and reassess the new site. The goal is minimising the dip and accelerating recovery, not eliminating fluctuation entirely.