Multilingual SEO: Hreflang, Shopify and Localization

Multilingual SEO is the work of making each language version of your site rank in the searches made in that language: separate URLs for every language, hreflang annotations that link the versions together, and content that is localized for each market instead of machine-translated and left alone. Get those three right and Google can show French shoppers your French pages and German shoppers your German pages, instead of guessing.

This playbook is for e-commerce and Shopify brands expanding beyond one language. You'll get Google's own rules for multilingual sites, a URL structure decision table, hreflang done correctly (with the mistakes that break it), what Shopify Markets and Translate & Adapt handle for you, and a step-by-step launch plan.

What multilingual SEO is (and how it differs)

Google draws a clear line between two kinds of international sites. A multilingual site offers content in more than one language, such as a Canadian store with English and French versions. A multi-regional site explicitly targets users in different countries, such as a brand that ships to both the US and Canada. Many stores are both: separate US and Canadian versions, with English and French on the Canadian side.

The difference matters because Google matches them differently. For language, Google Search tries to find pages that match the language of the searcher. For region, it tries to find the right locale page. Your setup needs to send both signals clearly, which is what the rest of this guide covers. If your main question is which countries to enter and how to prioritize them, start with our international SEO strategy guide, then come back here for the build.

Why it is worth doing

Shoppers strongly prefer to buy in their own language. In CSA Research's "Can't Read, Won't Buy" B2C survey of 8,709 consumers in 29 countries, 76% said they prefer to buy products with information in their own language, and 40% said they will never buy from websites in other languages.

The supply side is also lopsided. W3Techs data for October 27, 2026 shows English is the content language of 49.5% of websites whose language it can detect, with Spanish at 6.1% and German at 5.9%. Non-English searches often have fewer strong, well-localized e-commerce pages competing for them.

How Google handles multilingual sites

Google's documentation on multi-regional and multilingual sites sets out a few rules that shape every decision you make. These are the ones e-commerce teams most often get wrong.

• Use a different URL for each language. Google recommends separate URLs per language version rather than switching the language with cookies or browser settings. If you change content dynamically, Google may not find and crawl all your versions, because Googlebot usually crawls from the US and sends requests without an Accept-Language header.
• Google detects language from visible content. Google says it uses the visible content of the page to determine its language, not code-level signals such as the lang attribute or the URL. Use one language for the content and navigation of each page and avoid side-by-side translations.
• Don't force redirects by language. Google advises against automatically redirecting users to another language version based on what you think their language is, because it can stop users and search engines from reaching every version. Link to the other language versions instead.
• Don't rely on IP detection. Google calls IP location analysis difficult and generally unreliable, and notes that most of its crawls originate from the US.
• Translated pages aren't duplicates. Google's hreflang documentation says localized versions are only treated as duplicates if the main content remains untranslated.

Choose your multilingual URL structure

Before you translate a single product, decide where each language will live. Google lists four options. Shopify's international SEO documentation describes the same choices for Markets and recommends subfolders for most stores.

Note that language and country are different things. A subfolder like /fr/ can mean French for everyone, while /fr-ca/ means French for Canada. Decide whether you are targeting a language, a country, or a language within a country, and name your folders to match. You can use localized words in the URL slug itself (for example /es/products/zapatos); Google says that is fine as long as you use UTF-8 encoding.

Hreflang tags: how they work

Hreflang annotations tell Google that a set of pages are localized versions of the same content, so it can show each searcher the right one. Google doesn't use hreflang to detect a page's language; it uses it to understand which pages are alternates of each other and who each one is for.

The rules that make hreflang work

• Pick one method. You can add hreflang as <link> elements in the HTML head, as HTTP headers or in your XML sitemap. Google says the three are equivalent, and using more than one brings no benefit.
• Every version lists every version, including itself. The set of hreflang links is identical on every page in the group.
• Links must be reciprocal. If two pages don't both point to each other, Google ignores the tags.
• Use full URLs. Alternate URLs must be fully qualified, including https, not relative paths.
• Use valid codes. The value is an ISO 639-1 language code, optionally followed by an ISO 3166-1 Alpha 2 region code, such as fr or fr-CA.
• Add x-default. The x-default value tells Google where to send searchers whose language doesn't match any version, usually your main site or a country selector.

A product sold in US English, UK English and German would carry this block in the head of all three pages:

<link rel="alternate" hreflang="en-US" href="https://example.com/products/boot" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/products/boot" />
<link rel="alternate" hreflang="de" href="https://example.com/de/products/stiefel" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/boot" />

Because every version lists every other version, hreflang grows quickly as you add markets. Each page carries one line per version plus x-default, and the totals across a catalog add up fast.

That growth is why hand-coded hreflang breaks on large catalogs, and why a platform that generates the tags from your market settings is usually the safer choice.

Common hreflang mistakes and fixes

Google's hreflang documentation lists the most common mistakes. Here they are as a diagnostic grid, plus two conflicts that commonly break hreflang on e-commerce sites.

To spot these, view the rendered source of a few product and collection pages in each language and check that every alternate URL returns a 200 status. Our redirect checker helps confirm alternates don't redirect, and the sitemap checker shows whether your language URLs are in the sitemap. For canonical conflicts, see our guide to canonical tags.

Multilingual SEO on Shopify

Shopify handles more of this than most platforms. Everything below is confirmed in Shopify's Help Center documentation (International SEO for markets, International domains, Requirements for selling in multiple languages and Translate & Adapt); we did not test it on a live store for this guide.

• Automatic hreflang. When you assign a domain, subdomain or subfolder to a market with a language, Shopify adds hreflang tags to every page, plus an x-default tag that points to your primary domain. Tags are only generated for markets with a distinct URL. You can turn automatic tags off under Online Store, then Preferences, if a theme or app manages them, but Shopify warns that this can hurt SEO without a replacement.
• Self-referencing canonicals. Each market version, such as /products/shirt and /fr/products/shirt, gets its own canonical plus hreflang linking the set.
• International sitemaps. Sitemaps include every market URL with hreflang annotations, and update when you add a market.
• Crawlers aren't redirected. If you use automatic redirection, shoppers are redirected but known search engine crawlers get the URL they requested.
• Custom domain required. International domains and subfolders can't be built from the myshopify.com domain.

Shopify also notes that product, article and blog tags can't be translated, legal policies can't be auto-translated, and custom themes need to use the routes Liquid object for internal links so language URLs work. For the rest of your store's SEO setup, our Shopify SEO checklist covers the basics.

Localization beats translation

Hreflang gets the right page in front of the right searcher. Whether it ranks and sells depends on the content. Shopify's own SEO documentation puts it plainly: word-for-word translation is a good start, but adapting content for each market can improve rankings further.

Do keyword research separately for each language, starting from your highest-revenue collections and products. Search behavior rarely translates word for word: a shopper in Germany or Mexico may use a different product name, a different modifier or a local brand term. The CSA survey above found 73% of consumers want product reviews in their own language at a minimum, so translated or local reviews are worth the effort on product pages. Check translated titles with our title tag checker, since some languages run much longer than English.

How to launch a multilingual store, step by step

1. Pick markets from data. Use GA4 and Search Console country reports to find where you already get traffic and orders, then confirm shipping, payments and returns work there.
2. Choose language and region targets. Decide for each market whether you're targeting a language (de) or a language in a country (de-AT). Don't create region versions that are identical copies.
3. Set your URL structure. On Shopify, start with subfolders unless you have a strong reason for country domains. Set up a custom domain first.
4. Research keywords per language. Map local terms to your top collections and products before translating.
5. Translate, then localize. Use Translate & Adapt or a compatible app for the first pass, then have a native speaker review product pages, collections, navigation, titles and meta descriptions. Translate URL handles for priority pages.
6. Configure hreflang once. Let Shopify generate tags, or turn them off and use a single theme or app source. Never both.
7. Add a language selector. Make every version reachable through plain links so users and crawlers can switch, and don't force redirects.
8. Validate and submit. Spot-check hreflang, canonicals and status codes on each template, confirm the sitemap includes every language, and submit it in Search Console.
9. Measure by market. Track impressions, clicks and revenue by country and language, and expand to the next market only when the first one is indexed and earning.

Getting started with multilingual SEO

The order matters: structure first, then hreflang, then localized content, then measurement. Skipping the first two and translating everything at once is the fastest way to end up with pages Google can't sort out. If you run Shopify, the platform handles hreflang, canonicals and sitemaps for you, so your effort should go into keyword research and localization for each market.

If you want help planning an expansion, our e-commerce SEO and technical SEO teams work with Shopify brands selling across markets. Get in touch for a free plan.