Shopify Migration SEO Checklist — Move Off WooCommerce, Magento or BigCommerce Without Losing Rankings

A replatform to Shopify rewrites every URL on your store. Product URLs, category URLs, blog URLs, all of them change, because Shopify enforces its own path structure and there is no setting to switch it off. That one fact sits behind almost every “we moved to Shopify and organic traffic died” call I get. This is the exact checklist I run on migration projects, from the pre-migration crawl to the 90-day post-launch review, with the Shopify-specific traps spelled out.

Why migrations lose rankings (the actual mechanics)

Google does not penalize you for replatforming. There is no migration filter and no algorithmic suspicion of Shopify. Stores lose rankings after a migration because specific, identifiable signals break during the move, and each one is preventable if you know to look for it.

URL changes without redirects are the big one. Google ranks documents at URLs. When the URL changes and nothing tells Google where the document went, the old URL starts returning 404, its accumulated equity has nowhere to flow, and the new URL starts from close to zero. Every backlink you earned over the years now points at a dead page. A single missing redirect on a category page that drove 30 percent of your revenue is enough to make the whole project look like a disaster.

Internal link loss is the quiet one. Your old store had thousands of internal links: menu links, in-content links between blog posts and products, related-product blocks, footer links. Automated imports move the documents but rarely rewrite the links inside them. I have crawled freshly migrated stores where every in-content link still pointed at the old domain or at old paths that bounce through a redirect. Internal links are how Google understands which pages you consider important. Lose them and your crawl priority and topical structure collapse at the same time.

Redirect chains compound the damage. Many stores have already migrated once before, and the old site contains redirects from an even older structure. If you redirect old to older to new, every hop adds latency, leaks signal consolidation, and increases the chance Google gives up following the chain. Chains of three or more hops are common on second migrations and they are pure self-inflicted damage.

Canonical drift is the subtle one. Your old platform declared canonicals one way. Shopify declares them another way, and during a half-configured cutover it is easy to ship pages whose canonical points at the old domain, at the myshopify.com preview domain, or at a parameterized variant of themselves. Google trusts canonicals as a strong hint. Point them at the wrong place during the exact window Google is recrawling everything and you are telling it to index the wrong site.

None of these are exotic. All of them are findable with a crawler and a spreadsheet, which is why the checklist starts before anyone touches Shopify.

Step 1: crawl and benchmark the old site before you touch anything

You cannot verify a migration against a site that no longer exists. The pre-migration snapshot is the master record everything else gets checked against, and it has to happen while the old store is still live.

Run a full crawl of the current site with Screaming Frog. The free tier covers 500 URLs, which is enough for small stores; beyond that you need the paid license. Export every indexable URL with its title, meta description, H1, status code, canonical URL, word count and inbound internal link count. The internal link count matters later: it tells you which pages your own site considers important, so you can rebuild that hierarchy on Shopify instead of guessing.

Then snapshot Google Search Console. Export the Performance report at the maximum 16-month date range, broken out by page, and sort by clicks. This list is your protection priority: the top 50 URLs by clicks get hand-verified redirects and hand-verified on-page parity, no exceptions, because they are where the revenue lives. Export the queries report too, so you can compare post-launch rankings against a real baseline instead of memory.

Record current rankings for your money keywords in whatever rank tracker you use, and keep the export. Screenshots work if you track nothing today. The point is a dated baseline, because eight weeks after launch you will be arguing with yourself about whether position 6 used to be position 4.

Export your backlinks. The GSC Links report is free and adequate; Ahrefs or Semrush add anchor text and authority data on top. You need to know which URLs have external links pointing at them, because those URLs must redirect cleanly even if they are old blog posts nobody reads anymore. External equity is the hardest signal to rebuild and the easiest to preserve.

This benchmark phase is the same discipline I apply in a standalone Shopify technical SEO audit, and if you want to run the crawl process on your current store first, my guide to auditing your Shopify SEO yourself walks through the full setup. Finally, put an annotation in your analytics on cutover day. Future you will thank present you.

What actually changes: URL structure on Shopify versus everyone else

Shopify is opinionated about URLs. Products live under /products/, category pages under /collections/, static pages under /pages/, and blog posts under /blogs/ followed by the blog handle, which is “news” by default. You cannot remove these prefixes. No app removes them, no theme removes them, and every forum thread promising a workaround ends in a hacky JavaScript rewrite that breaks canonicals. Accept the structure and plan the redirects.

Here is how the four platforms compare for the same catalog:

Two practical notes on this table. WooCommerce and Magento structures are configurable, so crawl what your site actually serves rather than trusting defaults. And Magento layered navigation produces parameter URLs like ?color=5&size=2 that have no Shopify equivalent at all, which becomes important in the redirect section below.

There is one more Shopify quirk worth knowing before you build the map. Shopify generates collection-scoped product URLs like /collections/widgets/products/blue-widget when a visitor clicks through from a collection page. These canonicalize correctly to /products/blue-widget by default, so they are not a duplicate-content emergency, but your redirect map should always target the clean /products/ form, never the collection-scoped one.

If you are partway through planning a migration and want a second pair of eyes on your URL mapping before cutover, I review migration plans on a free 30-minute call. Bringing me a half-built spreadsheet is fine. Catching a mapping mistake before launch costs nothing; catching it in week three costs rankings.

Step 2: build the redirect map

The redirect map is a two-column spreadsheet: every old URL on the left, its exact new Shopify URL on the right. It is the single deliverable that decides whether this migration preserves your rankings, and it deserves more hours than any other line on the project plan.

Start from the Screaming Frog export, not from your platform’s product list. The crawl contains what actually exists and what Google actually sees, including orphaned pages, legacy landing pages and old blog posts the CMS export will miss.

Map one to one. The old product page maps to its new product page. The old category maps to the matching collection. If you are keeping slugs identical, and you should wherever Shopify’s handle rules allow it, most of the map is a formula: extract the slug, prepend the new prefix. Products with matched SKUs or handles can be paired with a lookup. Then hand-verify the top 50 traffic URLs from your GSC export row by row, because a formula error on your best-selling collection is the most expensive typo you will ever make.

Three rules I never break when mapping:

• Never bulk-redirect leftovers to the homepage. Google treats irrelevant redirects as soft 404s and the equity evaporates anyway. Map to the closest relevant page, or let genuinely dead URLs return 404.
• Collapse chains. If the old site already redirects /widgets/ to /product-category/widgets/, point /widgets/ directly at /collections/widgets so no hop survives the migration.
• Redirect old pagination to the base page. /product-category/widgets/page/2/ goes to /collections/widgets, because Shopify paginates with ?page=2 and a paginated redirect target adds nothing.

Getting redirects into Shopify, and what Shopify can’t redirect

Shopify has a native redirect engine and it is genuinely good at the one thing it does: exact-match 301s. In the admin, go to Online Store, then Navigation, then View URL redirects. You can add redirects one at a time, but for a migration you import a CSV with exactly two columns:

Redirect from,Redirect to
/product/organic-lavender-soap/,/products/organic-lavender-soap
/product-category/bath-body/,/collections/bath-body
/product-category/bath-body/page/2/,/collections/bath-body
/about-us/,/pages/about-us
/2024/03/lavender-growing-guide/,/blogs/news/lavender-growing-guide

Upload it via the Import button on the URL Redirects screen. Shopify processes the file and emails you a summary that flags rejected rows. Read that email. Rejected rows are silent ranking losses if you ignore them.

Now the limits, because this is where migrations from Magento and parameter-heavy WooCommerce setups get hurt:

• Exact match only. There is no regex, there are no wildcards, and there is no rule builder. You cannot write “redirect everything under /product-category/ to /collections/”. You expand every real URL into its own row instead, which is fine, because your crawl already enumerated every real URL.
• Query strings cannot be matching conditions. Shopify ignores parameters when matching redirects. WordPress shortlinks like /?p=123 and Magento layered-navigation URLs cannot be handled natively. If those parameter URLs have meaningful traffic or links, handle them upstream at the edge. Cloudflare Bulk Redirects on the free plan handles thousands of static rules plus pattern matching before the request ever reaches Shopify, and that is my standard workaround.
• Reserved prefixes are refused outright. Shopify will not create redirects from paths starting with /apps, /application, /cart, /carts, /orders, /shop or /services. Notice /shop in that list: the default WooCommerce shop page cannot be redirected inside Shopify at all. Handle it at the edge. Every WooCommerce migration hits this one.
• Redirects only fire on a would-be 404. If you import a redirect from a path that still resolves to a live page on the new store, it silently does nothing until that page is removed or unpublished.

You do not need a redirect app for any of this. The native engine plus an edge layer covers every migration I have run, and most redirect apps simply wrap the same native API with a monthly fee. I tested the popular ones in my Shopify SEO apps roundup if you want the specifics.

Domains, www and canonicals at cutover

Shopify handles domain-level redirects well if you configure one setting correctly. In Settings, then Domains, set a single primary domain. Shopify then 301-redirects every other connected domain and the www or non-www variant to the primary automatically, and issues the SSL certificate. Pick whichever variant your old site used so external links keep resolving with one hop, and verify the redirect resolves in one hop after DNS propagates.

The myshopify.com domain takes care of itself: once a primary custom domain is set, the storefront on yourstore.myshopify.com redirects to it, so the preview domain does not get indexed. What does get stores in trouble is sequencing, like removing the development password before the redirect map is imported, or leaving the password on after DNS has switched. The runbook below fixes the order.

Canonical checks are a fifteen-minute job that I have seen skipped on five-figure migration projects. After cutover, view source on a product page, a collection page, a paginated collection, a blog post and the homepage. Every canonical should be an absolute URL on your primary domain pointing at the page itself. Watch for three specific failures: canonicals still referencing the old domain because someone hard-coded them in a theme customization, ?variant= URLs canonicalizing somewhere unexpected, and apps injecting a second canonical tag on top of the theme’s. One page, one canonical tag, pointing at itself on the primary domain.

This is the stage where most owners realize the migration is bigger than the developer quoted. If you would rather have a specialist own the SEO side while your dev team builds the theme, that is exactly what my flat $1,500 per month Shopify SEO plan covers. No contracts, founder-led, and migrations are the projects where it pays for itself fastest. Or start with a free consultation and I will tell you honestly whether your migration needs me at all.

On-page parity: make the new page recognizably the same document

Redirects tell Google where the document moved. Parity convinces Google it is the same document. The biggest unforced error I see is treating migration as a chance to rewrite everything: new titles, new descriptions, restructured content, fresh images. Each change might be an improvement in isolation, but stacking them on top of a URL change means Google is evaluating a new document at a new address, and your rankings reset accordingly. Migrate first, verify stability, then improve one variable at a time.

Title tags and meta descriptions carry over exactly as they were for every URL in your GSC top-pages export. Your crawl export has the old values; Shopify’s product and page admin takes them in the search engine listing fields. For stores over a few hundred SKUs I do this via CSV import or the bulk editor rather than by hand.

Body content moves intact: same copy, same heading structure, same FAQ blocks. Word count deltas show up in a before-and-after crawl comparison, which is how I catch description fields the importer truncated.

Images need their filenames and alt text carried over, not just the pixels. Shopify’s CDN serves whatever filename you upload, so upload the original descriptive filenames rather than letting an importer rename everything to image-1.jpg, and migrate alt text explicitly. Image search traffic is real for ecommerce and it dies quietly in migrations because nobody owns it.

Structured data needs a parity check, not an assumption. Crawl both versions with structured data extraction switched on and compare. Most Shopify themes output basic Product schema, but review aggregates, brand, GTIN and price-validity details that your old plugins emitted often vanish. Losing review stars in your snippets during the recrawl window compounds the dip.

Internal links are the rebuild job. Imported blog content arrives with in-content links pointing at old paths, or at the old domain in absolute form. Run a find-and-replace pass against your redirect map so internal links point directly at final Shopify URLs with no redirect hop, then rebuild menus and collection cross-links to mirror the old hierarchy your crawl documented.

Cutover-day runbook

This is the order of operations I run on launch day. The sequence exists because every step protects the one after it.

1. Freeze content changes on the old site 48 hours out, and run a final delta crawl to catch URLs created since your benchmark crawl.
2. Lower your DNS TTL to 300 seconds the day before, so the switch propagates fast and rollback stays possible.
3. Import the full redirect CSV into Shopify and configure edge rules before touching DNS. Redirects must exist before traffic arrives, not after.
4. Confirm the primary domain setting, and confirm checkout, forms and apps work on the Shopify side behind the password page.
5. Switch DNS, then remove the store password.
6. Immediately verify robots.txt is not blocking crawlers and that /sitemap.xml resolves and lists final URLs.
7. Submit the sitemap in Search Console. Keep the old GSC property forever. If the domain changed, verify the new property and file the Change of Address.
8. Hand-test your top 50 URLs from the old site and watch each 301 resolve in a single hop to the right destination.
9. Crawl the new live site in full and fix anything returning 404 or chaining.
10. Add the analytics annotation and go to bed at a reasonable hour, because the next 90 days are where the real work is.

Post-launch: the 90 days that decide what you keep

Google does not re-evaluate your site overnight. It recrawls URL by URL, follows your redirects, consolidates signals and settles. Your job in this window is to find breakage faster than Google does.

Watch the Page Indexing report in Search Console weekly. The “Not found (404)” and “Page with redirect” trends tell you whether the map is holding. New 404s get a redirect or a deliberate decision to let them die, logged either way.

Log 404s on the store itself, because GSC reports lag by days and sample heavily. I drop a tiny logger into theme.liquid that beacons every 404 hit to a Google Apps Script web app feeding a spreadsheet, which gives me same-day visibility, including the query strings Shopify’s own reporting does not show:

{% if request.page_type == '404' %}
<script>
  (function () {
    var hit = [
      Date.now(),
      window.location.pathname + window.location.search,
      document.referrer || 'direct'
    ].join('|');
    navigator.sendBeacon(
      'https://script.google.com/macros/s/YOUR_DEPLOYMENT_ID/exec',
      hit
    );
  })();
</script>
{% endif %}

Wire the receiving Apps Script to append rows to a sheet and you have a free, real-time miss list. Sort it by frequency every Monday and redirect the top offenders.

Ping IndexNow with your changed URLs to accelerate Bing and the engines that share its index. Google ignores IndexNow, so for Google the sitemap resubmission and natural recrawl are the path; for Bing, and for the AI answer engines that lean on Bing’s index, the ping measurably shortens the lag. While you are in that territory, check what your new store serves to AI crawlers, because a migration is the natural moment to fix it. My llms.txt for Shopify deep dive covers why the auto-generated file Shopify ships needs an override.

Then hold three formal checkpoints:

• 30 days: full crawl, GSC coverage review, top-50 ranking comparison against your baseline export, 404 log triage. Expect noise; rankings wobble while consolidation happens, and est. a 10 to 20 percent traffic dip in the first weeks is normal and recovers.
• 60 days: rankings should be at or near baseline for protected URLs. Anything still down two or more positions gets individual investigation, and the cause is usually a parity gap or a chained redirect.
• 90 days: final comparison against the benchmark, document the deltas, and only now start the improvement projects you postponed, because the migration variable is finally isolated.

That is the checklist. None of it is glamorous, and all of it is the difference between a migration nobody notices and a quarter of lost revenue.

FAQ

Planning a migration? Don’t gamble your rankings on it

I have spent 10+ years building and fixing WordPress and Shopify stores, and migration rescues are the most avoidable projects I take on. The checklist above is everything I run, in the order I run it. If you want to see how I approach store SEO beyond migrations, my Shopify SEO hub has the full picture.

If you would rather hand the whole thing to someone who has done it before, Book a free 30-min call → or reach me directly at +91 97297 12388 or on WhatsApp. I will look at your migration plan on the call and tell you exactly where the risk is, whether you hire me or not.