The Shopify Migration SEO Checklist: Replatforming With Zero Traffic Loss

Replatforming to Shopify is usually the right call. Moving a store is also the single easiest way to wipe out years of SEO in an afternoon. Migrations commonly lose 10–30% of organic traffic when redirects and content are mishandled, and some never recover.

The traffic doesn't disappear because of Shopify. It disappears because of missing redirects, missing content and nobody saving a "before" picture to compare against. This website migration SEO checklist is the process we use for moves from WooCommerce, Magento, BigCommerce, Salesforce Commerce Cloud and Amazon-first setups to Shopify.

Phase 1: Benchmark before you touch anything#

You can only prove a migration worked if you saved the before picture. Do this at least four weeks before launch.

1. Crawl the old site. Every indexable URL, with status code, title, meta description, H1, canonical and word count. Save the file; the old site won't exist later.
2. Export Search Console data. Pages and queries for the longest period available, plus current index coverage.
3. Pull revenue by landing page. From your analytics, list organic landing pages by revenue. These are the pages you can't afford to lose.
4. Export backlinks. From Ahrefs or Semrush, every URL with external links pointing to it.
5. Track rankings. Your top 100 to 500 keywords, tracked daily from now until three months after launch.
6. Record AI visibility. Run your core buyer prompts in ChatGPT and Google AI Mode and note where you appear.

Phase 2: Understand Shopify's URL structure#

Shopify uses fixed URL prefixes, and you can't change them. Almost every URL on your old site will change, so redirects aren't optional.

Three consequences:

• Hierarchy flattens. Nested categories become flat collections. Plan collection handles so they still describe the category, like dining-tables rather than tables-2.
• Handles must be unique. If two old products share a slug in different categories, one gets a new handle. Catch collisions in the map, not after launch.
• Duplicate paths appear. Shopify can serve products at /collections/x/products/y as well as /products/y. Canonicals handle it, but your theme's internal links should point to the canonical URL. See our guide to Shopify duplicate content.

Phase 3: Build the URL map#

The URL map is the most important document in the migration. It's a spreadsheet with one row per old URL:

Rules for the map:

1. Every old URL with traffic, links or revenue gets a row. Include URLs found in Search Console and backlink tools as well as the crawl. Old campaign pages and discontinued products often carry links.
2. Redirect to the closest equivalent. A discontinued product goes to its replacement or its collection, not the homepage. Mass homepage redirects are commonly treated as soft 404s, and the value of those pages is lost.
3. Keep content where the rankings are. If an old category page ranks, its Shopify collection needs the same (or better) intro copy above the product grid.
4. Decide on faceted URLs deliberately. Old filter URLs with query strings usually shouldn't be mapped one by one. Our post on faceted navigation covers what to keep indexable.

Phase 4: Redirects the Shopify way#

Shopify's redirect system has rules that trip up teams coming from Apache or Nginx.

• Redirects only fire on 404s. Shopify redirects work only from URLs that return "Page not found." If a live page exists at the old path, the redirect never triggers. This bites when a product or page is recreated at a path you meant to redirect.
• Fixed paths are protected. You can't redirect a live /products/ or /collections/ URL; you'd have to remove or rename the resource first.
• There's a cap. Shopify allows up to 100,000 URL redirects per store, or 20,000,000 on Shopify Plus. A Magento store with a large catalog and years of URL history can exceed 100,000 once every variant and old category path is included. Prioritize by traffic and links, or plan for Shopify Plus.
• Query strings are unreliable. Shopify notes that redirects from URLs with query strings might not work as expected. Map the clean URL, and handle the rest with canonical pages and patience.
• Import by CSV. Shopify imports redirects in bulk from a CSV with "Redirect from" and "Redirect to" columns. Use relative paths.
• No chains. If an old URL was already redirected on the old platform, point the original straight to the final Shopify URL. Google suggests avoiding long chains of redirects.

Redirect from,Redirect to
/furniture/tables/walnut-dining-table.html,/products/walnut-dining-table
/furniture/tables.html,/collections/tables
/furniture/tables/dining/,/collections/dining-tables
/blog/how-to-choose-a-table/,/blogs/news/how-to-choose-a-table
/about-us/,/pages/about-us

For very large or pattern-based redirect sets, see our guide to Shopify redirects at scale.

Phase 5: Content and technical parity#

A redirect sends Google to the new page. The new page still has to deserve the ranking.

Content

• Carry over titles, meta descriptions and H1s for every page with rankings, then improve them.
• Migrate collection intro copy and product descriptions in full. Don't let a theme's short-description layout truncate them.
• Import reviews with dates and ratings, so product pages keep their social proof and review schema.
• Move the blog with images and internal links rewritten to new URLs.

Technical

• Structured data. Product, Offer, Review and BreadcrumbList on the new theme. Validate before launch. Our schema markup service covers what Shopify themes miss.
• International. If you sell in several countries, set up Shopify Markets and check hreflang output before launch. Moving from separate country domains is its own project.
• robots.txt. Shopify's default is sensible. If you edit robots.txt.liquid, don't carry over old platform rules that no longer match any URL.
• Speed. A theme heavy with apps can undo the speed gains that justified the move. Test key templates before launch.
• Internal links. Update menus, footers and in-content links to point at final URLs, not redirects.
• AI search. Check that robots.txt allows OAI-SearchBot, and look at the Agentic sales channel so product data flows to AI channels from day one.

Phase 6: Launch day#

1. Remove the storefront password and confirm the new site is indexable (no leftover noindex from staging).
2. Import the redirect CSV and spot-check the top 100 URLs by revenue.
3. Crawl the old URL list against the live site. Every row should be one 301 hop to a 200 page.
4. Submit the new sitemap in Search Console and Bing Webmaster Tools.
5. If the domain changes, use Search Console's Change of Address tool. Google says it's only needed when moving between domains or subdomains.
6. Check Merchant Center: the feed should point to new product URLs with matching prices.
7. Test checkout, analytics and conversion tracking end to end.

Phase 7: The first 90 days#

Keep the redirects in place for the long term. Google says to keep them for as long as possible, generally at least a year, and on Shopify there's rarely a reason to remove them at all. Update your most valuable backlinks at the source where you can.

Platform-specific traps#

• WooCommerce: tag and attribute archives that ranked, and ?add-to-cart= URLs that got indexed. See WooCommerce to Shopify.
• Magento: deep category paths, .html suffixes and store-view URLs for each language. See Magento to Shopify.
• BigCommerce: faceted URLs with long query strings, which Shopify's redirects may not handle. Map the clean category URLs.
• Amazon-first brands: there's no old site to redirect, but your Amazon listing copy, reviews and brand searches are assets. Build Shopify collections around the keywords your Amazon listings already win. See Amazon to Shopify.

• Salesforce Commerce Cloud: locale folders and pipeline-style URLs, often with thousands of legacy paths. Redirect budgets and international setup need planning together. See SFCC to Shopify.

Mistakes we see most often#

Most migration traffic losses trace back to a short list.

1. Redirecting everything to the homepage. Fast to set up, and it throws away the relevance of every old page.
2. Mapping from the crawl alone. Crawls miss orphaned pages that still have backlinks and traffic. Merge crawl, Search Console and backlink exports.
3. Dropping collection copy. The new theme looks clean because the category intro text never came across. Rankings for category terms slide over the following weeks.
4. Recreating pages at old paths. A new Shopify page at a path you meant to redirect stops the redirect from firing.
5. Leaving staging settings on. A leftover noindex or password page after launch is rare, and catastrophic when it happens.
6. Changing everything at once. New platform, new domain, new URL structure, new navigation and new product names in one launch makes problems impossible to diagnose. Change what you must, and save the rest for after the dust settles.
7. Stopping monitoring after a week. Some losses only show once Google has recrawled deeper pages, weeks after launch.

If your store also needs deeper fixes after the move, such as crawl waste, duplicate URLs or slow templates, that's technical SEO work best scheduled for the month after launch, once the redirects have settled.

The migration checklist, condensed#

1. Crawl, export and benchmark everything.
2. Map every URL with traffic, links or revenue.
3. Match content and metadata page for page.
4. Import redirects respecting Shopify's 404-only rule and limits.
5. Validate schema, hreflang, speed and internal links.
6. Launch with a checklist, not a feeling.
7. Monitor daily for a week and weekly for three months.

Done this way, a migration is a chance to fix years of technical debt, not a traffic risk. If you're planning a move, the Shopify SEO checklist is a good companion for the post-launch tune-up.