Ecommerce Site Migration SEO: The Complete Checklist to Protect Rankings

16 min read · Ecommerce SEO · Last updated July 2026

Quick answer: A poorly executed site migration can destroy 6-12 months of SEO progress overnight. Protect your rankings with a full URL export before migration, 301 redirects for every changed URL, content parity verification, and daily traffic monitoring for 90 days post-launch.

Introduction

A Shopify-to-custom store migration without proper SEO planning caused a Sydney fashion retailer to lose 73% of their organic traffic in 30 days. It took 11 months to fully recover.

Site migrations are one of the highest-risk SEO events an ecommerce store can undertake. A domain change, platform switch, HTTPS upgrade, URL restructure, or site redesign — any of these done without proper planning can tank rankings that took years to build.

The good news: migration traffic loss is almost always preventable. This guide gives you the complete pre-migration, launch, and post-migration SEO checklist.

What you’ll learn:
– The 5 types of migrations and which carry the highest SEO risk
– Pre-migration steps that take 2-3 weeks but prevent months of recovery
– How to implement and verify 301 redirects correctly
– Post-migration monitoring schedule with specific metrics
– Emergency response if traffic drops 50%+ after launch

Table of Contents

1. The 5 Types of Migrations and Their Risk Levels
2. Pre-Migration Phase: The 3-Week Preparation Checklist
3. URL Mapping — The Most Important Document You’ll Create
4. Redirect Implementation: 301s, Chains, and Common Mistakes
5. Content Parity Check — Every Page Must Have a Match
6. Technical Migration Checklist
7. Launch Day Protocol
8. Post-Migration Monitoring — The 90-Day Watch Schedule
9. Timeline Expectations: Dip, Recovery, and New Baseline
10. Emergency Response: Traffic Drops 50%+
11. Widget: Migration SEO Checklist (Interactive)
12. Widget: Traffic Recovery Timeline Visualizer
13. FAQ

1. The 5 Types of Migrations and Their Risk Levels

Type 1: Domain Change (example.com → newbrand.com)
Risk: Very High. Every page URL changes. All existing backlinks point to the old domain. Google needs to re-evaluate trust and authority for the new domain. Timeline to full recovery: 6-18 months.

Type 2: Platform Change (Magento → Shopify, WooCommerce → BigCommerce)
Risk: High. URL structure almost always changes (e.g., /category/product.html → /products/product). If redirects aren’t mapped carefully, thousands of product URLs can go dark overnight.

Type 3: HTTP to HTTPS
Risk: Low-Medium. Usually straightforward if done correctly. Common mistake: not redirecting all HTTP variants (with/without www) to the canonical HTTPS version.

Type 4: URL Structure Change (restructuring categories)
Risk: Medium-High. Restructuring /mens-clothing/shirts/ to /apparel/mens/shirts/ changes URLs that may have built up significant link equity. Every changed URL needs a 301.

Type 5: Redesign (same platform, same URLs)
Risk: Low if URLs don’t change. Main risk is removing content that was ranking or changing page structure in ways that dilute topical relevance. Still requires content parity verification.

The risk multiplier: Combining migration types massively increases risk. A domain change + platform migration + URL restructure + redesign happening simultaneously (as during a full rebrand) is the highest-risk scenario in ecommerce SEO.

2. Pre-Migration Phase: The 3-Week Preparation Checklist

Week 1: Audit and Capture

Day 1-2: Full site crawl with Screaming Frog (or Sitebulb). Export every URL the crawler finds — including product pages, category pages, tag pages, pagination, and any blog content. This is your source-of-truth URL list.

Day 3-4: Export from Google Search Console. Pull “Coverage” report — export all indexed URLs. Compare with your Screaming Frog export. Any URL in GSC but not in your crawl is an edge case to investigate.

Day 5-7: Export traffic data from GA4 for the past 12 months. Identify your top 100 URLs by organic traffic. These pages are your migration priorities — they must redirect correctly and must have content parity on the new site.

Week 2: Analysis

• Identify all URLs that will change in the migration
• Identify pages that will be discontinued (products removed, categories consolidated)
• Identify pages that will merge (two categories becoming one)
• Flag your top 100 traffic URLs and your top 50 backlinked URLs (from Ahrefs → Best by Links)
• Note all pages with structured data, canonical tags, hreflang, or noindex directives

Week 3: Mapping and Staging

• Build your URL redirect map (old URL → new URL) — this is covered in Section 3
• Set up staging site and verify new URL structure
• Validate all redirects on staging before launch day
• Complete content parity check on staging (Section 5)
• Verify all technical elements on staging (Section 6)

3. URL Mapping — The Most Important Document You’ll Create

Your redirect map is a spreadsheet with at least these columns:

Redirect decision rules:
– Page exists on new site with same content → 301 to new URL
– Page is being removed but category exists → 301 to most relevant category page
– Page is being removed with no relevant replacement → 301 to homepage (last resort)
– Page merges with another page → 301 to merged page
– Page stays identical at same URL → no redirect needed

Finding URLs you might miss:
– Faceted navigation URLs that are indexed (check GSC Coverage report)
– Old product pages for discontinued products that still have backlinks
– Blog post pages that accumulated traffic over time
– XML sitemap URLs that aren’t in your crawl (orphaned but indexed)

Volume reality check: A 10,000-product Magento store migrating to Shopify might have 15,000-25,000 URL redirects to map. This typically takes 2-4 weeks for a thorough mapping. Budget accordingly.

4. Redirect Implementation: 301s, Chains, and Common Mistakes

301 vs 302: Always use 301 (permanent) redirects for migration. 302 (temporary) redirects don’t pass link equity. Google may return to serving the old URL if it sees a 302 — don’t risk it.

Redirect chains: A redirect chain occurs when URL A → URL B → URL C. Every hop in the chain loses some link equity and slows page load. Clean chains so every old URL redirects directly to the final destination URL. If your old site already had some 301s and you’re migrating again, audit for chains before launching.

Common redirect mistakes:

1. Redirecting to homepage en masse. Redirecting 5,000 old product URLs to the homepage tells Google these pages have no relevant replacement. Google devalues these as “soft 404s” within weeks.

2. Implementing 302 instead of 301. A single server configuration error can switch all redirects to 302. Verify with a tool like httpstatus.io after launch.

3. Missing trailing slash consistency. /mens-shoes and /mens-shoes/ are technically different URLs. Implement a consistent rule (with or without trailing slash) and redirect the other variant.

4. Not redirecting paginated URLs. /collections/shoes?page=2 URLs might have indexed in Google. Map these too — redirect to the main category URL.

5. Forgetting the www vs non-www canonicalization. Your old site might have served both http://www.example.com and http://example.com. Your new site must handle both and redirect all non-canonical variants to one canonical version.

Testing redirects at scale: Use Screaming Frog’s redirect checker to crawl your old URL list and verify each one returns a 301 to the correct new URL. Do this on launch day before announcing the migration to Google.

5. Content Parity Check — Every Page Must Have a Match

Content parity means the new version of each page has all the content (or more) that the old version had. Google’s indexing of your new site should find pages that are equal or better to the old versions.

For category pages:
– Same or expanded category description text
– Same or more product count (if you’re listing fewer products, explain why with filters)
– Same or improved navigation structure
– All canonical tags present and correct

For product pages:
– Full product description (not just manufacturer spec)
– Same product images (migration often strips images from descriptions)
– Same structured data (Product schema with price, availability, reviews)
– Same reviews (check that your migration preserved user review data)
– Same related products section

For blog/informational pages:
– Full article content preserved
– Images not broken (CDN or image hosting changes often break old image URLs)
– Internal links updated to new URL structure (old links create redirect chains internally)
– Author and date information preserved (E-E-A-T signals)

The migration content audit process:
1. Crawl the staging site
2. For your top 100 traffic pages: manually compare old vs new side by side
3. For remaining pages: word count comparison (new page should be ≥ old page word count)
4. Image count comparison (new page should have same or more images)
5. Structured data validation (Google’s Rich Results Test on staging URLs)

6. Technical Migration Checklist

These technical elements must be verified on the new site before launch:

Crawlability:
– [ ] robots.txt on new site does NOT block Googlebot
– [ ] Staging site’s robots.txt DID block Googlebot (to prevent premature indexing)
– [ ] XML sitemap updated with all new URLs
– [ ] Sitemap submitted to GSC after launch

Canonical and hreflang:
– [ ] Self-referencing canonicals on all pages
– [ ] hreflang tags updated if applicable (URLs changed = hreflang URLs must change)
– [ ] No canonical pointing to old domain

Structured data:
– [ ] Product schema on all product pages (validate 5+ with Rich Results Test)
– [ ] Breadcrumb schema matches new URL structure
– [ ] Organization/store schema on homepage with new domain

Site speed and Core Web Vitals:
– [ ] Page speed tested in staging (PageSpeed Insights for mobile and desktop)
– [ ] No new render-blocking resources introduced by new theme/platform
– [ ] Images served in WebP format with lazy loading
– [ ] LCP under 2.5s, CLS under 0.1, INP under 200ms

Internal linking:
– [ ] All internal links updated to new URL structure (critical — old internal links create redirect chains)
– [ ] Navigation links updated
– [ ] Footer links updated
– [ ] Breadcrumb links updated

7. Launch Day Protocol

2 hours before launch:
– Final verification of redirect map with httpstatus.io on staging
– Screenshot of current GSC coverage numbers (baseline)
– Screenshot of current GA4 organic traffic (baseline)
– Confirm staging robots.txt blocks crawlers

At launch:
– Update DNS / go live
– Verify live site loads correctly (SSL, homepage, 5 category pages, 5 product pages)
– Run redirect test on 20 critical old URLs — confirm 301 → correct new URL
– Update robots.txt on live site to allow crawling
– Submit new XML sitemap to GSC
– Request indexing for homepage and top 10 priority pages in GSC URL Inspection

2 hours after launch:
– Run a quick Screaming Frog crawl of top 50 old URLs to verify all redirect to 301
– Check server error logs for any 5xx errors
– Verify Google Analytics is receiving data on the new site

8. Post-Migration Monitoring — The 90-Day Watch Schedule

Days 1-7 (daily monitoring):
– GSC Coverage: Watch for spike in “Not found (404)” errors
– GSC Crawl Stats: Verify Googlebot is crawling the new site
– GA4 Organic Sessions: Compare day-over-day (expect initial volatility)
– Server errors: Check logs or server-side monitoring for 5xx errors

Weeks 2-4 (every 3 days):
– GSC Performance: Clicks, impressions, position — compare week-over-week
– GSC Index Coverage: Monitor indexing progress of new URLs
– Check if important product/category pages are appearing in Google (spot-check 20 URLs)
– Validate that old URLs no longer appear in search results (they should redirect)

Weeks 5-12 (weekly):
– Full organic traffic comparison (this week vs same week prior year, and vs pre-migration baseline)
– Crawl budget analysis: is Googlebot crawling the most important pages first?
– Backlink check: verify major backlinks now point correctly to new URLs (Ahrefs alerts)
– Core Web Vitals: check CrUX data in GSC if available for new domain

9. Timeline Expectations: Dip, Recovery, and New Baseline

What to expect after a well-executed migration:

• Days 0-14: Volatility. Traffic may drop 10-30% as Google processes the redirect graph. This is normal.
• Weeks 2-6: Gradual recovery as Google recrawls, processes redirects, and re-ranks new URLs. Rankings fluctuate significantly.
• Weeks 6-12: Stabilization. Most correctly-redirected URLs regain their pre-migration positions.
• Months 3-6: Full recovery. For domain changes, this can extend to 12-18 months.

The traffic dip equation:
– Well-executed migration (comprehensive redirects, content parity, quick crawling): -10 to -20% initial dip, recovery in 6-12 weeks
– Average execution (most redirects, some content gaps): -30 to -50% dip, recovery in 3-6 months
– Poor execution (missing redirects, content loss, slow crawling): -60%+ dip, recovery takes 6-18 months

10. Emergency Response: Traffic Drops 50%+

If traffic drops more than 50% within 2 weeks of migration, act immediately:

Step 1: Diagnose — Check GSC Coverage for 404 errors. Export all “Not found” URLs. These are pages that should have redirected but didn’t.

Step 2: Triage — Cross-reference 404 URLs against your redirect map. Find the gaps.

Step 3: Fix — Implement missing redirects immediately. Every hour a redirect is missing costs you link equity.

Step 4: Submit — Submit affected pages for recrawling in GSC URL Inspection.

Step 5: Communicate — Don’t try to hide a bad migration. Contact your major backlink sources and request they update links directly to new URLs — this bypasses redirects and recovers equity faster.

Common emergency causes:
– Server-level robots.txt blocking crawlers (check immediately)
– Domain DNS not fully propagated (some users hitting old server)
– Incorrect redirect rules (302 instead of 301, or redirecting to wrong pages)
– New site returning 500 errors intermittently

Widget 1: Migration SEO Checklist

Widget 2: Traffic Recovery Timeline Visualizer

FAQ

Q: Should I migrate during peak season?
Never. Avoid migrations during your highest-traffic months. For most ecommerce stores, that means avoiding November-December (holiday), or any month that accounts for 15%+ of annual revenue. Schedule migrations in your lowest-traffic quarter.

Q: My old domain expired and I didn’t set up redirects. What now?
This is severe. Immediately acquire the domain if still available. Implement 301 redirects as quickly as possible. Contact your major backlink sources and ask them to update links directly to the new domain. Recovery can take 12-24 months.

Q: How long should I keep 301 redirects running after migration?
Permanently, or at minimum 2 years. Old URLs exist in backlinks, bookmarks, social shares, and cached pages. Removing redirects too early re-creates the 404 problem. If you’re paying for redirect management (some platforms charge per redirect), prioritize your top-200 traffic URLs and keep those indefinitely.

Q: Does migrating from HTTP to HTTPS require redirects?
Yes — you need to 301 redirect all HTTP URLs (both www and non-www) to their HTTPS equivalents. HTTP→HTTPS migrations are generally low-risk when done correctly, but Google still needs to process the change, which takes 2-6 weeks.

Q: My new platform generates different URL slugs (e.g., /product/ prefix). Do all of those need redirects?
Every URL that changes needs a 301. Yes, even if the difference is just adding /product/ before the slug. Google treats these as distinct URLs with no ranking history.

Conclusion

Site migrations are one of the highest-stakes decisions in ecommerce SEO. The stores that navigate them successfully treat migration as a project with a dedicated pre-launch phase, comprehensive URL mapping, and 90 days of post-launch monitoring.

The investment in proper migration planning is minimal compared to the cost of 6-12 months of traffic loss. Spend the 3 weeks upfront. Your rankings will thank you.

Ready to Grow Your Ecommerce Store?

We build ecommerce SEO systems — from product schema to category architecture to Shopping integration. → Request an Ecommerce SEO Audit

Written by the Ignited Nepal ecommerce team. ignitednepal.com