Why most WooCommerce to Shopify migrations lose traffic

Most WooCommerce to Shopify migrations lose between 20 and 40 percent of organic traffic in the first 90 days. It isn't a Shopify problem. It's a process problem. SEO is treated as a post-launch cleanup task rather than a pre-launch constraint, and by the time rankings start sliding, the crawl debt has already piled up.

This guide covers the migration in the order it actually needs to happen, for established stores with real volume. If your WooCommerce site does $500K or more in annual revenue, you can't wing the SEO handoff. You have backlinks carrying link equity, URLs ranking for commercial terms, and structured data Google has spent months or years indexing. All of it can be carried over — but only if you build the plan before you touch anything.

Why WooCommerce URLs create problems on Shopify

The URL structure divergence between the two platforms is the first place migrations get messy, and it's completely predictable.

WooCommerce, built on WordPress, gives you full control over permalinks. A product URL might be `/product/mens-running-shoes/` and a category page `/product-category/running/shoes/`. Shopify forces the `/products/`, `/collections/` and `/pages/` prefixes that you can't remove. That means `/product/mens-running-shoes/` becomes `/products/mens-running-shoes` and `/product-category/running/shoes/` becomes `/collections/shoes`. Neither URL survives without a 301 redirect.

The compounding problem is Shopify's dual URL structure for products. When a product is accessed through a collection, Shopify displays a contextual path like `/collections/collection/products/product-handle`, but the canonical URL is still `/products/product-handle`. Your redirect map has to account for both patterns, because inbound links and indexed pages can point at either one.

Faceted navigation is another common source of index fragmentation. WooCommerce sites that used query parameters for filters need to review how filters are implemented on Shopify — some apps create parameterized URLs that get crawled and indexed. Audit the WooCommerce filter configuration before migrating and decide how you want Shopify to handle them.

Blog URLs also change. WordPress posts live at `/blog/post-slug/` or a custom path. Shopify moves them to `/blogs/news/post-slug`. If your content drives meaningful organic traffic, those pages need redirects just like your products and collections. See the [official Shopify migration documentation](https://help.shopify.com/en/manual/migrating-to-shopify/migrating-from-woocommerce) for the full redirect-configuration flow.

The pre-migration SEO audit: export before you touch anything

This step is not skippable. It takes a few hours and prevents months of recovery work.

Google Search Console exports

Download three reports before you do anything to your live WooCommerce site. The first is the Performance report filtered to the last 12 months, sorted by clicks, exported as CSV — this tells you exactly which URLs are driving traffic today. The second is the Coverage report showing every indexed URL and existing errors. The third is the Links report showing which URLs have the most inbound links. These three files are your source of truth for the migration.

Screaming Frog crawl

Crawl your entire live WooCommerce site before migration kicks off. Export every URL with its status code, title tag, meta description, H1, canonical tag and internal link counts. For large catalogs, filter down to URLs that are indexed and receiving traffic. The combination of the GSC performance export and the Screaming Frog crawl gives you a complete picture of what needs to survive the migration.

Structured-data inventory

If you've been using Yoast SEO, Rank Math or WooCommerce's own product schema, document which schema types are present. Product, BreadcrumbList, Review and Organization schema all need equivalents on Shopify. Shopify ships basic Product, Organization and Breadcrumb schema in most modern themes, whereas WooCommerce relies on plugins to inject it. The good news is you're moving to a platform that handles it natively. The risk is assuming it happens automatically without verifying.

The plugin-to-app translation problem

Every WooCommerce plugin you rely on has a Shopify equivalent. Whether that equivalent is as good, costs more, or introduces gaps is something you need to decide before committing to the migration calendar.

Yoast SEO

On WooCommerce, Yoast SEO Premium runs about $118.80/year per site, with the WooCommerce-specific add-on adding another $79/year on top of Premium — roughly $198 annually for WooCommerce SEO coverage. On Shopify, Yoast SEO for Shopify costs $19/month ($228/year) and covers meta optimization, schema and sitemap control. It does NOT include the redirect manager available in the WordPress version. On Shopify, redirects are managed natively under Content → Menus → URL Redirects, or via Matrixify for bulk operations. It's a workflow change, not a capability loss.

WooCommerce Subscriptions

WooCommerce Subscriptions does not map cleanly to Shopify. You'll need to re-integrate active subscribers via Recharge or Skio, which typically involves customer communication and some manual cleanup. Recharge has a documented migration tool that handles subscription state and re-verifies payment tokens through Shopify Payments. Most subscriptions migrate without customer intervention, but a percentage — usually 5 to 15 percent — require a payment update because the source token can't be re-verified. Plan that communication proactively. A subscription interruption that surprises customers triggers cancellations that have nothing to do with your product.

Advanced Custom Fields

WooCommerce stores built with ACF or custom product meta have a clear path. Matrixify connects directly to the WooCommerce API, which means custom fields migrate into Shopify metafields without manual reformatting. The critical step is mapping ACF field names to their Shopify metafield equivalents before running the import, so theme templates can reference them correctly at launch.

Review plugins

Product reviews don't migrate natively. You'll need a third-party review app on Shopify — Judge.me, Loox or Yotpo — plus a CSV export from your WooCommerce review plugin. This is the step most commonly skipped in self-managed migrations. Reviews are both a conversion asset and a structured-data source. If they're going to disappear in the migration, build the rebuild time into the project plan.

Catalog migration with Matrixify

For any store with more than a few hundred products, variable products, custom fields or complex attributes, Matrixify is the right tool. Before running a real import, Matrixify offers a Dry Run mode that processes your file and flags errors without writing anything to the store. For a catalog at $500K+ revenue scale, running that dry run is not optional.

Matrixify's direct connection to the WooCommerce API is the key differentiator. It migrates WooCommerce custom fields into Shopify metafields in a single step, preserving data that would otherwise require manual rebuild. It also handles images via URL, generates 301 redirects as a migration artifact, and transfers meta titles and meta descriptions — meaning the redirect map and SEO metadata can be processed together rather than in separate passes.

Shopify's native importer is another story. It works fine for simple stores with limited products and no complex structure. For larger catalogs with variable products, metafields and order history, it's too opaque. It can skip items without clear error messages, a risk not worth taking for an established business. Matrixify gives you a line-by-line error log and a spreadsheet record of everything imported, so you can verify the data before your store goes live.

Variable products require specific attention during the mapping phase. As of October 2025, Shopify raised the variant-per-product limit from 100 to 2,048 across all plans — including Basic, Shopify and Advanced — without requiring Shopify Plus. The three-options-per-product maximum, however, remains a hard cap across all plans. If your WooCommerce catalog includes products with more than three option dimensions (size, color, material, length and fit on a single product), that constraint still applies and needs a workaround before migration day: split products, a custom-options app, or line-item properties.

301 redirect strategy for large catalogs

A redirect map isn't optional and it isn't post-launch cleanup. It's infrastructure, and it must be complete before the DNS cutover happens.

The redirect map is a two-column CSV: the old WooCommerce path on the left, the new Shopify path on the right. Build it from your Screaming Frog export and your GSC performance data. Prioritize in this order: the top 20 percent of pages by click volume, every page with more than five referring domains, every canonical product and collection URL, and every blog post with indexed traffic.

Skip the redirects and you'll lose 20 to 40 percent of organic traffic in the first 30 days. That's what happens when link equity accumulated over years of WooCommerce operation has no path to transfer to the new domain structure.

For large catalogs, Shopify supports CSV import of redirects directly from admin: Content → Menus → View URL Redirects, then bulk-import. For catalogs with thousands of redirects, Matrixify handles the upload more reliably than the native importer.

Pattern-based redirects matter too. If your WooCommerce category structure was `/product-category/boots/ankle-boots/`, every URL in that hierarchy needs to map to its Shopify collection equivalent. A single missed subcategory can leave dozens of product pages returning 404s.

For the full redirect-mapping methodology, see our detailed guide on [Shopify 301 redirects](/resources/shopify-301-redirects). The summary: build the map before launch, validate it after DNS cutover, monitor it for the first 60 days.

Post-launch monitoring: what to watch and for how long

Migration doesn't end at launch. It ends when the GSC coverage report is clean and ranking recovery is stable. That usually takes four to eight weeks.

Week 1

Submit your new Shopify XML sitemap to Google Search Console immediately after DNS cutover. Shopify generates it automatically at `yourdomain.com/sitemap.xml`. Crawl the live Shopify site with Screaming Frog the same day and compare the indexed URL count against your WooCommerce baseline. Every 404 you find is a redirect that needs to be added.

Weeks 2–4

Monitor the GSC Coverage report daily for the first two weeks. Watch for two patterns: new 404 errors appearing as Google re-crawls the site, and valid pages showing coverage errors. The first means gaps in the redirect map. The second usually means canonical-tag issues.

Shopify adds canonical tags automatically pointing to `/products/product-handle`, but Go Fish Digital and Amsive research indicates Google ignores those canonical tags in 30 to 40 percent of cases when collection URLs receive internal links that contradict the canonical signal. That means your internal link structure matters after launch — not just the redirect map. Audit your theme navigation and collection page links to make sure they point at the canonical product URL, not the contextual collection variant.

Weeks 4–8

Ranking recovery follows a predictable curve if redirects are clean. Most rankings recover within four to eight weeks. If specific pages haven't recovered after six weeks, investigate in this order: confirm the redirect resolves correctly, confirm the canonical tag is present and correct on the Shopify page, then use the URL Inspection tool in GSC to verify the page has been re-crawled.

A migration we ran for a US health-accessories brand with 4,000+ SKUs saw organic sessions return to baseline within 38 days of launch. The redirect map was built during the pre-migration audit phase — not assembled reactively after 404s started appearing. Every redirect was validated with Screaming Frog before DNS cutover. That sequence is the difference.

Closing the gap

WooCommerce to Shopify migration has a reputation for being risky for SEO. That reputation has been earned by migrations done without a pre-migration audit, without a complete redirect map, and without a post-launch monitoring window. Done in the right order, with the right tools, and with an honest assessment of plugin-to-app gaps, the SEO risk is manageable.

At [Shugert](/services), we've been running Shopify migrations for DTC brands since 2016 — 30+ complete migrations across stores in the US, LATAM and Spain. If you're evaluating a move from WooCommerce and want a realistic assessment of what the SEO work looks like for your specific catalog, our [Shopify Plus migration masterclass](/resources/shopify-plus-migration-masterclass) and our [services page](/services) cover how we structure that work from day one.