You did everything right. You researched platforms, compared features, mapped out your product catalog, and made the call: it was time to move from WordPress (WooCommerce) to Shopify. Faster checkout. Better app ecosystem. Less maintenance overhead. The migration made complete sense.
Then, six weeks later, your organic traffic from Germany dropped 38%. Your French-language product pages disappeared from Google. Your rankings for key terms in Australia and the UK — terms you'd spent two years building — simply vanished. Revenue from international markets, once a growing share of your business, quietly collapsed.
This is not a rare story. It plays out every month across ecommerce businesses that make the WordPress-to-Shopify leap without understanding one critical reality: international ecommerce is structurally different from domestic ecommerce, and Shopify handles that complexity very differently from WordPress.
The migration itself wasn't the mistake. The mistake was treating it as a like-for-like platform switch rather than a complete technical restructuring of how your store communicates with search engines across multiple countries, languages, and currencies.
This article breaks down exactly why this happens — the specific technical failure points that cost international stores their revenue — and what you can do about it, whether you're planning a migration or already dealing with the fallout from one. If you're still in the planning phase and need a step-by-step walkthrough of the migration process itself, our complete WordPress to Shopify migration guide covers the full process from backup to launch.
Why International Stores Are Different from Domestic Ones
Before diving into what goes wrong, it helps to understand what makes international ecommerce uniquely fragile during a platform migration.
A domestic store operating in a single country, in one language, with one currency, has a relatively simple SEO footprint. There's one URL structure. One set of rankings. One audience. When you migrate that store, you're moving a single thread.
An international store is moving a web.
Consider what a mid-sized international ecommerce store typically runs:
- Product pages in three to six languages
- Regional URLs structured as subdomains (
de.yourstore.com), subdirectories (yourstore.com/de/), or separate country-code top-level domains (yourstore.de) - Hreflang tags that tell Google which version of a page to serve to which audience
- Currency rules, tax configurations, and pricing tiers tied to specific regions
- Thousands of backlinks pointing to region-specific URLs
- Years of accumulated search authority built in each market independently
Every one of these elements is load-bearing. When you migrate platforms, each one has to be carefully re-established in the new environment. Miss one, and you don't just lose a page — you lose a market.
The problem is that most migration guides treat "international" as a feature you can turn on after the fact. It isn't. For stores that have already built international search equity, it's infrastructure that has to be rebuilt, in sequence, before you ever go live on Shopify.
The 5 Reasons International Stores Lose Revenue After Migration
Reason 1: Hreflang Tags Break or Disappear Entirely
Hreflang is the HTML attribute that tells search engines: "this page exists in multiple languages and regions — here's the right version for each audience." Without it, Google has to guess which version of your page to show to users in different countries. It often guesses wrong, or worse, it treats your translated pages as duplicate content and filters them from results entirely.
WordPress handles hreflang through plugins like WPML, Polylang, or Yoast SEO Premium, which automatically generate and maintain hreflang tags across your entire site. These tools are mature, widely tested, and deeply integrated into the WordPress content model.
Shopify's native hreflang support, delivered through the Shopify Markets feature and its default theme framework, is functional — but it is not automatic.
It doesn't simply pick up where your WordPress plugin left off. It requires deliberate configuration of your markets, languages, and URL structure, and if you're using a custom theme or a third-party app for multilingual content, hreflang generation may need to be handled separately through that app or through manual liquid template modifications.
What happens in practice: stores migrate, launch on Shopify, and discover that their hreflang tags are either completely absent, pointing to non-existent URLs, or structured incorrectly. Google de-indexes the regional variants. Traffic from those markets collapses.
Reason 2: URL Structure Changes Destroy Link Equity
Search engine authority isn't stored in your platform — it's stored in your URLs. Every backlink pointing to yourstore.com/de/category/product/ is a vote for that specific address. When you migrate to Shopify and that URL becomes yourstore.com/de/collections/category/products/product, every one of those votes points to a dead address.
Shopify has a fixed URL structure. Unlike WordPress, where you have near-complete control over URL patterns, Shopify enforces its own conventions:
- Products live under
/products/ - Collections live under
/collections/ - Blog posts live under
/blogs/ - Pages live under
/pages/
This means that virtually every product URL from a WooCommerce store will change on migration. For a domestic store, this is manageable with a clean 301 redirect map. For an international store with regional URL variants multiplied across six languages, this becomes a massive redirect engineering problem — one that many migration projects underestimate or skip entirely.
When redirects are missing or misconfigured, the accumulated link equity from years of international SEO work doesn't transfer. It evaporates. And unlike a Google penalty, which you can appeal, link equity that walks out the door simply doesn't come back quickly.
Reason 3: Multilingual Content Is Lost or Restructured Incorrectly
Multilingual content in WordPress lives inside the CMS itself — typically managed by WPML or Polylang, which attach translated versions of posts and products to their original language counterparts as a structured relationship within the database.
Shopify's content model works differently. Product translations in Shopify live within the storefront translations system, accessed through the Translate & Adapt app or third-party alternatives like Langify or Weglot. The underlying data structure is not interchangeable with WordPress's approach.
During migration, translated content frequently gets lost, flattened, or attached to the wrong products. In some cases, only the default language content migrates and translated variants have to be re-entered manually. In others, the translations migrate but without the correct language associations, causing Shopify to serve the wrong language to the wrong region.
The SEO consequence is severe. Those translated product pages had their own search rankings, their own indexed content, their own traffic. When the content structure breaks, those pages either return errors, serve the wrong language, or simply don't exist anymore — and every ranking tied to them goes with them.
Reason 4: Currency and Pricing Configurations Fail for Specific Regions
Revenue loss from international migrations isn't always about SEO. Sometimes users find your store just fine — and then leave because the pricing experience is broken.
WooCommerce currency handling is highly customizable through plugins like WooCommerce Multi-Currency, which can display prices in local currencies, apply region-specific pricing rules, and integrate with local payment gateways. These configurations can be intricate and deeply tailored to specific markets.
Shopify Payments and Shopify Markets support multi-currency natively, but the way they handle rounding, conversion rates, and market-specific pricing does not map directly from WooCommerce configurations. Stores that had custom pricing for specific markets — where a product is priced at €49 in Germany regardless of the EUR/USD exchange rate, for example — may find that Shopify's dynamic currency conversion produces prices that feel off or inconsistent to returning customers.
Beyond perception, broken currency configurations can disrupt checkout completion rates in specific markets, generate incorrect tax calculations, or cause payment failures with regional gateways that weren't properly reconfigured. The result shows up not as an SEO problem but as a sudden drop in conversion rate from specific geographic segments.
Reason 5: 301 Redirects Are Incomplete or Misconfigured for International URLs
A 301 redirect tells search engines and browsers that a page has permanently moved to a new address. It transfers the original page's search authority to the new URL. For migrations, 301 redirects are the mechanism by which you preserve your SEO equity.
International stores have to build and test redirect maps that account not just for the standard product and category pages, but for every language variant of every page. A store with 500 products in five languages needs a redirect map that handles 2,500 product URL combinations — plus categories, tags, and static pages in each language.
In practice, most migration redirect maps are built for the default language and then extended to cover international variants as a secondary step, often under time pressure. The result is a redirect map with gaps: some regional URLs redirect correctly, others redirect to the wrong language version, and others return 404 errors.
The damage from missing international redirects compounds over time. Search engines re-crawl your old URLs, find 404s, and remove those pages from their index. The backlinks and authority those pages carried go unattributed. International rankings that took years to build disappear within a single crawl cycle.
What Makes These Problems Worse (and Harder to Detect)
Any one of the five issues above would be damaging on its own. In combination, they create a failure cascade — and the most dangerous part is how long it takes to become visible.
SEO drops are delayed by 30 to 90 days. Search engines don't re-crawl and re-index your entire site the moment you go live on a new platform. Googlebot works through a crawl schedule based on site authority and page count. For a large international store, it may take four to twelve weeks before Google has fully processed your new URL structure, registered the missing redirects, and updated its index accordingly. This means you can migrate in January, celebrate a smooth launch, and only see the international traffic drop in March — by which point the cause-and-effect relationship is less obvious.
Analytics gaps during migration mask true performance. Google Analytics, Meta Pixel, and other tracking setups often need to be re-implemented on Shopify from scratch.
If there are gaps in tracking — even a few days you lose the baseline data that would let you compare pre- and post-migration performance accurately. Stores sometimes interpret incomplete analytics as stable performance, when in fact traffic is already declining in markets they've stopped tracking correctly.
Shopify's default international settings aren't production-ready for complex stores. Shopify Markets works well for stores setting up international selling from scratch.
For stores migrating an already-established international presence, the defaults often require substantial customization. The subdirectory structure Shopify uses by default (/en-gb/, /de/) may not match the structure your existing pages are indexed under, and there's no automated mapping between your old URL conventions and Shopify's.
Third-party multilingual apps don't always interoperate cleanly. The choice between Shopify's native Translate & Adapt, Weglot, Langify, and other multilingual apps introduces its own set of hreflang behaviors, URL structures, and SEO implications. Stores that pick an app without first auditing how it generates hreflang tags and handles canonical URLs frequently discover incompatibilities after launch.
How to Migrate Without Losing International Revenue
The good news is that all of these problems are preventable with the right pre-migration process. None of them are inevitable — they're the product of treating international SEO as an afterthought rather than a migration prerequisite.
Step 1: Pre-Migration Audit — Crawl and Document Everything
Before touching a single setting in Shopify, run a full crawl of your existing WordPress site using a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit. Export every URL that is currently indexed, including all language variants. Document the hreflang tags on every key page. Export your existing 301 redirect rules. Note the exact URL structure for products, categories, and static pages in each language.
This crawl data is your migration source of truth. Without it, you're rebuilding from memory.
Step 2: Map Old URLs to New Shopify URLs
Create a comprehensive redirect map that covers every URL in your crawl export — not just the default language. For each old URL, identify what the new Shopify URL will be and create the corresponding 301 redirect entry.
Shopify allows bulk redirect uploads via CSV through the URL Redirects section of the admin. For large stores, use a spreadsheet to manage the mapping and import it in batches, verifying each batch before the next.
Pay particular attention to international URL variants. If your old site used /de/produkte/product-name/ and Shopify will serve it under /de/products/product-name/, every German product URL needs its own redirect entry.
Step 3: Set Up Hreflang Correctly Before Launch
Decide on your international URL structure in Shopify before you configure your markets. Shopify Markets supports subfolders by default (e.g., yourstore.com/de/). If your existing site used subdomains or ccTLDs, evaluate whether it's worth maintaining that structure through a custom domain setup or whether migrating to subfolders makes more sense long-term.
Once your URL structure is decided, configure your hreflang tags through your chosen method — Shopify's native Translate & Adapt, a third-party multilingual app, or manual liquid template implementation. After configuration, validate your hreflang implementation using Google Search Console's International Targeting report or a tool like hreflang.org before you go live.
Step 4: Migrate and Validate Multilingual Content
Don't assume that your translated content migrated correctly. After migrating product and page content, audit a representative sample of translated pages in each language. Check that the correct translation is served when accessing the page via the correct regional URL. Check that the hreflang tags reference the correct language-region combinations. Check that translated metadata (title tags, meta descriptions) migrated alongside the content.
For stores using third-party multilingual apps, consult the app's official migration documentation — most have specific guidance for importing content from WPML or Polylang exports.
Step 5: Configure Currency and Pricing for Each Market
Recreate your market-specific pricing rules in Shopify Markets. If your WooCommerce setup used fixed local currency pricing rather than dynamic conversion, configure Shopify Markets to use manual market-specific prices rather than automatic currency conversion. Verify that checkout completes correctly for a test order in each major market before launch.
Step 6: Post-Migration Monitoring
After launch, monitor the following for at least 90 days:
- Google Search Console coverage and indexing status, filtered by country
- Organic traffic by country segment in Google Analytics
- Rankings for your top 20 to 30 keywords in each international market
- Crawl errors and 404 rates for international URL patterns
- Conversion rate by country, segmented from your pre-migration baseline
Set up alerts in Search Console for sharp drops in indexed pages or manual actions. A fast response to emerging problems — a missing redirect batch, a misconfigured hreflang tag — can limit the ranking damage before it becomes entrenched.
What Recovery Looks Like (and How Long It Takes)
If you've already migrated and you're reading this because your international traffic has dropped, the path forward is the same as the prevention checklist above — just in a more urgent sequence.
Start with the crawl audit. Identify which international pages are returning 404s and which are missing redirects, then implement those redirects immediately. Fix hreflang configuration next, since incorrect or missing hreflang tags are often the fastest issue to resolve and can have a meaningful impact within one to two crawl cycles.
Realistically, full recovery from a migration-related international SEO drop takes three to six months for most stores — assuming the underlying issues are identified and fixed within the first four to eight weeks.
The recovery is not linear: you'll typically see stabilization first (the drop stops getting worse), followed by a gradual recovery of rankings and traffic over the following months as Google recrawls, re-indexes, and re-evaluates your pages.
For stores that lost significant link equity due to missing redirects, recovery is slower. Links pointing to 404 pages don't automatically reactivate when you add a redirect months later — Google needs to recrawl the referring pages, follow the redirect, and update its authority attribution.
This is why getting redirects right before launch, rather than patching them after, is so important.
The question of whether to revert to WordPress is one that comes up but rarely makes sense after the fact. The costs and risks of a second migration — and the additional SEO disruption it would cause — typically outweigh the costs of fixing the issues on Shopify.
The exception is a store where Shopify's structural limitations (particularly around URL architecture) are fundamentally incompatible with the international SEO strategy — in that case, a more honest assessment of long-term fit is warranted.
You've fully recovered when organic traffic from international markets has returned to within 10% of pre-migration levels across your primary countries, your key international rankings have stabilized at or above their pre-migration positions, and your conversion rate by country shows no persistent anomalies introduced by the migration.
Conclusion: Migration Shouldn't Mean Starting Over Internationally
Shopify is a capable platform for international ecommerce. Thousands of stores run successful global operations on it. The problem was never Shopify — it's the assumption that a platform migration is a neutral technical event, and that your international search equity will simply transfer along with your product catalog.
It won't, unless you deliberately rebuild it.
The stores that migrate successfully treat international SEO as infrastructure — a set of systems (hreflang configuration, URL structure, redirect architecture, multilingual content management) that has to be engineered, tested, and validated as part of the migration itself, not bolted on afterward.
The stores that lose revenue treat it as a feature to configure post-launch, discover the damage weeks later, and spend months clawing back rankings they already owned.
The gap between these two outcomes isn't technical expertise — it's prioritization. International SEO has to be on the migration checklist from day one, not the day after go-live.
If you're planning a migration, start with the pre-migration audit described in this article before you write a single Shopify redirect rule. If you've already migrated, start the audit today — every week of delay is another crawl cycle of lost ground.
Have questions about your specific migration situation? A technical SEO audit before or after migration can identify the exact gaps in your international setup and prioritize the fixes that will recover revenue fastest.
Top comments (0)