# Multilingual Shopify Migration: Keep Localized Pages Connected

> Moving a multilingual store to Shopify? Map localized URLs, preserve language equivalents, and verify redirects, canonical tags, hreflang and Markets.

- Author: [Francesco Guiducci](https://ifgdigital.com/en/francesco-guiducci/)
- Published: 2026-11-19 · Updated: 2026-11-19
- Topic: [Migrations and platform choice](https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/topic/migrazioni/)
- Language: English · Italian version: https://ifgdigital.com/ifgwebdesign/ecommerce/blog/migrazione-shopify-multilingua-hreflang/
- Reading time: 6 min
- URL: https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/multilingual-shopify-migration-localized-urls-hreflang/

**Direct answer:** migrating a multilingual store to Shopify means preserving the relationships between content, language, market and URL—not simply translating the new theme. A shop can appear ready in its main language while an established international product page loses its redirect, its equivalent destination or its correct search signals.

A reliable migration starts with an inventory of existing localized URLs, then tests each important market independently. The goal is to move real pages and their users to the most relevant new destinations without fabricating translations or search-engine annotations.

## Start with a language-and-market inventory

A language is not a market. English-language content might serve several countries, but those markets can have different prices, currencies, shipping eligibility or product availability. Conversely, two localized pages may share a language while having separate commercial roles.

Record the current domain, subdomain or subfolder for each storefront. Sample product and collection pages, editorial articles, customer-facing policies and landing pages—not only the homepages. For every significant URL, capture its language, target market, new equivalent, planned redirect, expected canonical and any available translated counterparts.

Use actual evidence from the existing site. A translation field in an export does not establish that its page was publicly accessible, indexable or commercially valid before the move.

Shopify's [international SEO documentation](https://help.shopify.com/en/manual/markets/seo) describes how market domains and languages interact with search-facing URLs. Check the configured storefront rather than assuming one URL pattern fits all stores.

## Decide which URL structure to preserve

An existing store may use example.com/fr/, fr.example.com or an independent country domain. Shopify supports multiple international-domain structures, but selecting one should follow the merchant's market model, operational constraints and existing search footprint.

Avoid redesigning every URL structure during the platform switch without a specific reason. Combining a new platform, new domain, reorganized categories and rewritten content makes it harder to identify the cause of lost traffic or broken journeys.

For languages shared across several markets, decide whether a single page is genuinely the right canonical destination or whether separate regional experiences exist. A market configuration is not a reason to generate multiple empty or near-identical pages.

## Build a redirect map by locale, not just by product

The redirect workbook should have an explicit source and target for each important localized page. If a former French product page has a working French replacement, redirect it to that replacement, not to the Italian product or the global homepage.

Do not assume redirects automatically cover translated subfolders or every historical domain. Check the rules supported by the actual Shopify configuration and any upstream routing involved. A redirect target must exist and provide relevant content; multiple hops and accidental cross-language redirects are failures worth catching before launch.

Google's [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) emphasizes mapping old URLs to appropriate new ones. For retired products or untranslated content, record an explicit decision. A generic homepage redirect may hide a missing translation rather than resolve it.

## Canonical and hreflang solve different problems

A canonical URL expresses which address should be treated as representative where duplicate or very similar URLs exist. Hreflang identifies corresponding language or regional versions of a page. Neither should be used to claim that a translation exists when it does not.

Google expects localized alternates to point to real equivalents, with consistent reciprocal references. Check rendered HTML and HTTP responses on both sides. An Italian article and its English original can reference each other; an Italian-only article must not emit a fictional English alternate.

A common migration error is to canonicalize every translated page to the Italian version to simplify SEO. That discards the distinction between genuinely localized content and duplicates. Evaluate each page and the site's indexing strategy instead.

Shopify can generate international SEO signals based on configured Markets and languages. Avoid layering hand-written hreflang on top without testing what the platform already outputs. Refer to [Google's localized-version rules](https://developers.google.com/search/docs/specialty/international/localized-versions) for the reciprocal relationship and fully qualified URL requirements.

## Treat availability separately from translation

A product description translated into French does not prove that the product is available for purchase in France. Before launch, verify catalog availability, currency, market-specific pricing, taxes, shipping methods and checkout restrictions for the markets that matter.

The same distinction applies to navigation: a translated collection title is not enough if its products, filters or links lead customers into the wrong market. Check whether an item has been intentionally excluded from a market rather than treating every unavailable URL as an import defect.

For editorial content, verify that important guides and policies survived the move. A product export alone does not preserve the complete library of localized articles or every link pointing to them.

## A practical URL × language × market test matrix

Keep the acceptance matrix compact enough to audit. These are example cases, not results from a specific merchant migration.

| Source case | Required acceptance evidence |
| --- | --- |
| Italian product URL | Italian replacement works, is indexable where intended, and has the correct canonical |
| French product URL | Relevant French destination works, with correct language, availability and currency |
| Shared-language regional page | Domain and intended market behavior match the configured canonical strategy |
| Translated editorial article | Both localized pages return 200 and reference real reciprocal alternates |
| Page with no translated equivalent | Explicit handling recorded; no false hreflang and no arbitrary homepage redirect |
| Historical URL with incoming links | Appropriate permanent redirect with no broken destination or unnecessary chain |

The matrix should track outcomes and exceptions. A matching count of products before and after import is not enough: it tells you little about language-specific links, search metadata or checkout eligibility.

## Validate on mobile and across actual markets

Run acceptance tests for the priority locales on the public hostname and, before cutover, in a production-equivalent preview where possible. Cover homepage, navigation, collections, product pages, article pages, cart and checkout. Test the language selector from within an article: it should open the equivalent page when one exists and offer a sensible fallback—not pretend that the original is a translation.

For SEO, inspect the rendered title and description, robots directives, canonical, reciprocal hreflang, sitemap entries, permanent redirects and HTTP status. Verify the page's own language and the destination of every alternate. Use a mobile viewport as well as desktop: a language selector that works in a header on a wide screen may fail behind a mobile menu.

After launch, monitor international sections separately in Search Console. A successful homepage request does not establish that all localized content can still be discovered or indexed. A submitted indexing request is not proof of indexing.

## Plan the cutover and the exceptions

Include locale-specific checks in the [Shopify go-live and order-continuity runbook](https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/shopify-migration-go-live-orders-cutover-checklist/). A market that can browse products but cannot complete checkout is a launch issue even if all its redirects are correct. Likewise, a perfect checkout does not make missing localized pages acceptable.

Define who owns each exception: missing translation, mismatched market availability, broken redirect, incorrect canonical or conflicting alternate annotations. Some issues can be repaired after launch, but critical search or purchase paths should have explicit stop criteria.

The objective is not to manufacture one-to-one translations for every historical URL. It is to maintain accurate relationships between the pages that genuinely exist and make the fate of each important legacy path traceable.

For the full project scope, see the [Shopify migration service](https://ifgdigital.com/en/ifgwebdesign/ecommerce/shopify-migration/). Technical planning and migration delivery are handled directly by Francesco Guiducci.

## Planning your Shopify migration

Continue with [301 Redirects During a Shopify Migration: URL Mapping and Tests](https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/shopify-migration-301-redirects-url-map-and-tests/). See the [Devoti Sailing](https://ifgdigital.com/en/ifgwebdesign/ecommerce/case-studies/devoti-sailing/) case study for a move from WordPress to Shopify that included migrating content. If you are ready to discuss your store, [share your migration requirements](https://ifgdigital.com/en/lp/shopify-migration/).
