Shopify Multilingual Store: Setup, SEO, and Hreflang Done Right

Your store is live. You’re getting traffic from Germany and France - people land, browse, leave. Conversion from those markets is 0.4% versus 3.1% from English-speaking visitors. In 95% of cases the reason is one thing: the store is in English, and the buyer wants to shop in their language.

CSA Research found that 76% of consumers prefer to buy products with information in their native language. 40% won’t buy from a foreign-language site at all - regardless of price or product quality. That’s not a preference, that’s a hard wall where money stops.

For Shopify store owners, multilingual isn’t “nice to have” anymore. It’s a technical task with a specific ROI: Shopify reports an average 13% conversion lift when shoppers see a store in their language, and stores launching 3+ languages see 25% revenue growth within 12 months.

But there’s a catch. Set up languages incorrectly and you don’t get SEO traffic - you get cannibalization between language versions, duplicate content, and Google penalties. Here’s how to do it right.

Translation vs. localization: two different tasks with different outcomes¶

Translation is converting text from one language to another. Localization is making the store look and feel native to a buyer in another country.

The difference in practice:

Stores that only translate often wonder - “but we translated everything” - and don’t understand why conversion isn’t moving. Google ranks them, people arrive, but don’t buy. Because translation is the entry ticket, not the guarantee of sales.

This guide is about how to set up languages technically correctly (Shopify Markets + hreflang + URL structure) and make it actually drive sales rather than just converting text.

Shopify Markets: what it is and why it’s the starting point¶

Shopify Markets is the built-in international selling tool. It manages regions, currencies, languages, and local pricing. Available on all Shopify plans.

Critical distinction: Markets and translation are not the same thing.

Markets does: configure regions and currencies, automatically create subfolders (/de/, /fr/), generate hreflang tags, manage different pricing per market.

Markets does NOT do: translate content. After adding a language through Markets, you have “empty buckets” with the right URL structure - but the content is still English. Someone needs to fill it.

To fill it: either Shopify Translate & Adapt (built-in, free) or a third-party app.

How to add a language through Markets¶

1. Admin → Settings → Markets
2. Add market → select country or region
3. In market settings - Additional languages → Add language
4. Shopify automatically creates the URL subfolder (e.g., yourstore.com/de/) and adds hreflang tags
5. Then go to Translate & Adapt or a third-party app and fill in translations

One thing most people miss: if content in a language version isn’t translated, Shopify shows the buyer the original (English) text inside the localized template. The URL is /de/, but the text is English. For SEO that’s duplicate content, for the buyer it’s a broken experience.

URL structure for SEO: subfolders, subdomains, or ccTLD?¶

This technical decision has long-term consequences. Changing it later is painful because you’re moving SEO authority.

Three options and their implications¶

Subfolders: yourstore.com/de/ - ✅ Share main domain authority - new market doesn’t start from zero - ✅ Shopify Markets generates them automatically - ✅ Single domain - less administrative overhead - ⚠️ Weaker regional signal than ccTLD

Subdomains: de.yourstore.com - ✅ Alternative without buying new domains - ⚠️ Google partly treats as a separate site, authority transfer is less efficient - ⚠️ Needs independent SEO optimization

ccTLD: yourstore.de - ✅ Strongest regional targeting signal - ✅ Increases trust with local buyers - ❌ Need to buy and manage separate domains - ❌ Each domain starts SEO from zero - takes time to build authority

Recommendation: for most Shopify stores, subfolders are the best choice. They’re automatically generated by Shopify Markets, efficiently pass authority, and don’t require extra costs. Consider ccTLD only if you have a large, established market and resources for a dedicated SEO campaign per domain.

Hreflang: what it is, how Shopify generates it, and where mistakes happen¶

Hreflang is an HTML attribute that tells Google: “this page is for French users, here’s a version for French-speaking Belgians, and here’s one for Swiss users.” Without it, the search engine guesses which version to show - and often gets it wrong.

Correct hreflang looks like this (in the <head> of every page):

<link rel="alternate" hreflang="de" href="https://yourstore.com/de/" />
<link rel="alternate" hreflang="fr" href="https://yourstore.com/fr/" />
<link rel="alternate" hreflang="en" href="https://yourstore.com/" />
<link rel="alternate" hreflang="x-default" href="https://yourstore.com/" />

What Shopify Markets does automatically: generates these tags for each language version when you use the built-in language infrastructure. If you’ve added languages through Markets - this is already handled.

But automation doesn’t protect against configuration mistakes. According to Search Engine Journal, the most common issues:

Mistake 1: missing reciprocal links¶

If the French version references the English one through hreflang, but the English version doesn’t link back to the French one - Google ignores the entire cluster. Rule: every language version must link to ALL other versions, including itself.

Mistake 2: server-side geolocation redirects break indexing¶

Googlebot crawls primarily from US IPs. If your server automatically redirects “US IP → English version,” Googlebot only sees English and can’t index other language versions. Location-based redirects should be implemented client-side (JavaScript), not server-side.

Mistake 3: wrong language codes¶

“uk” means Ukrainian, not United Kingdom. For the UK the correct code is “en-gb,” not “uk.” A wrong code and Google associates your page with the wrong market. Full code list: IANA Language Subtag Registry.

Mistake 4: canonical tag conflicts with hreflang¶

If the French version has a canonical pointing to English - that’s a conflicting signal, and hreflang typically loses. Each language version needs canonical pointing to itself.

How to verify¶

After setup - check Google Search Console → International targeting → Language. Hreflang configuration errors show up clearly there.

Keywords: why you can’t just translate from English¶

This is the biggest mistake Shopify store owners make when entering new markets. They translate English keywords and think they’re done.

But a buyer in Spain doesn’t search for the same things as a buyer in Mexico - even though both speak Spanish. And a buyer in France uses completely different terms than the literal translation of an English query.

Concrete example: “running shoes” has 60,500 monthly searches. The literal French translation “chaussures de course” isn’t what French shoppers actually type into Google. More natural variants - “chaussures running” or “basket running” - and both volume and competition look completely different.

How to do keyword research for a new market¶

1. Google Keyword Planner: set language and country filters, search by topic not by translation
2. Ahrefs or Semrush: filter by country, look at what competitors are actually ranking for
3. Google Autocomplete: type the beginning of a query in the target language - autocomplete shows real search phrases
4. Native speaker: ask someone from the target market “how would you search for this product in Google” - the answer is often surprising

As Shopify notes in their multilingual SEO guide, even for a single language, search demand can differ dramatically between countries - “paella” has 127,000 monthly searches in the US, 43,000 in Spain, and only 9,400 in Argentina.

Rule: one keyword research per language and market, not one for everything. More work, but this is exactly where competitive advantage lives.

Meta title and description for each language version¶

Shopify defaults to pulling the product name and description into meta tags if you don’t optimize them manually. For SEO that means long, unfocused meta titles and descriptions with no target keyword.

For each language version, meta title and description need to:

1. Be localized - not machine-translated but genuinely adapted with local keywords
2. Hit the right length - title under 60 characters, description under 160
3. Include the focus keyword - what people actually search for in that market, not the English keyword translated

Both Shopify Translate & Adapt and Weglot have dedicated SEO content fields (meta title, meta description) per language version. Don’t skip this step - it directly affects organic CTR.

Translation tool comparison for Shopify¶

Three main options with real pros and cons:

Shopify Translate & Adapt (free)¶

What it does: - Translates any store content (products, collections, pages, checkout) - Free and built into Shopify admin - Supports up to 2 languages without additional apps - Automatic translation via Shopify’s translation API

Limitations: - 2-language limit on free plan - No automatic translation of new content - every new product needs manual translation - Weak SEO content management - No visual editor

Best for: stores with 1-2 languages and bandwidth for regular manual translation.

Weglot (€15-79+/month)¶

What it does: - Automatically translates all new content on publish - 100+ languages - Built-in SEO (automatic meta tag translation, sitemap) - Visual translation editor directly on the live page - Global substitution rules (so brand names don’t get translated)

Pricing: - Starter: free (1 language, 2,000 words) - basically a trial - Business: from €15/month (1 language, more words) - Pro: from €29/month (3 languages, 200,000 words) - Plus and Enterprise: from €79/month

Important: Weglot counts words that are translated and served - large catalogs can hit plan limits faster than expected.

Best for: stores with 3+ languages, large catalogs, and automation needs.

Langify (~$17.50/month)¶

What it does: - Manual translation with detailed control - Flat monthly price (predictable budget even as catalog grows) - Optional: pay-per-word auto-translation packages

Limitations: - Manual-first approach - more setup time - Less automation than Weglot - Less active product development

Best for: stores where translation accuracy matters more than speed.

Comparison table¶

What to translate first: content priority¶

No need to translate everything at once. The right order:

Required before launch: - Product titles and descriptions (top 20 by revenue) - Navigation (menus, categories) - Checkout (payment steps, order confirmation) - Meta title and description for top pages - About page and contacts

Important (within first month): - Full product catalog - Homepage - Blog posts with the most traffic - Shipping and returns pages

Can wait: - Old blog posts - Customer reviews - Archived content

As practitioners at shopifydev.eu recommend, the hybrid strategy works best: auto-translate the full catalog for a quick start, then manually review or have a native speaker edit the top 20 pages by traffic and revenue.

Common mistakes that tank multilingual SEO¶

1. Launching a language version with no content Shopify Markets created /de/ - good. But if it has English text - Google indexes a duplicate and penalizes both versions. Content first, then open for indexing.

2. Server-side geolocation redirects If the server automatically redirects by IP, Googlebot (usually from a US IP) never sees other language versions. A language switcher should be accessible, but not a forced redirect.

3. One content set for all markets of one language Spanish-speaking markets aren’t uniform: Spain, Mexico, Argentina, Colombia - different search demand, terminology, payment preferences. Budget permitting, separate research per market.

4. Machine-translated homepage copy without human review Auto-translation delivers 90-95% accuracy on factual content but often produces marketing copy that doesn’t convert - awkward phrasing, wrong tone, culturally off-key sentences. Top pages need a native speaker, no exceptions.

5. Not configuring the sitemap for language versions Shopify auto-generates a sitemap, but verify all language versions are included and correctly submitted in Google Search Console.

Practical launch plan: steps in order¶

Whether you’re starting from scratch or adding markets to a live store:

Step 1: Identify priority markets Check Google Search Console and Shopify Analytics - where is organic traffic already coming from? Where are you seeing orders or cart abandonment from foreign buyers? Go there first.

Step 2: Keyword research per market For top product categories and pages - fresh research in Ahrefs or Google Keyword Planner, filtered by language and country. Not translation, fresh research.

Step 3: Configure Shopify Markets Admin → Settings → Markets → Add market. Add language for the market. Shopify automatically creates URL subfolders and hreflang.

Step 4: Install a translation app Translate & Adapt for 1-2 languages with time for manual work. Weglot for 3+ languages or when automation is needed.

Step 5: Translate in priority order Start with checkout and navigation, then top products, then the rest. Simultaneously - adapt meta title and description with local keywords.

Step 6: Verify hreflang and technical SEO Google Search Console → International targeting. Confirm no errors. Confirm canonical tags don’t conflict with hreflang.

Step 7: Track results GA4: set up segments by language and country. Compare conversion rates across language versions. Lower conversion in one version signals a translation problem, a UX issue, or missing local payment methods.

FAQ¶

Does Shopify automatically add hreflang when I add a language?¶

Yes, if you add languages through Shopify Markets - hreflang is generated automatically. But if you use a third-party app or a custom theme, verify that the tags are present and correct.

Can I set different prices for different language versions?¶

Yes, through Shopify Markets you can configure market-specific pricing (currency-specific pricing). This lets you set psychologically appropriate prices (€49 instead of €47.23 after conversion).

What is x-default in hreflang?¶

x-default is the attribute for the “default version” when a user’s language doesn’t match any of your configured language versions. Typically this is the English version or the homepage. Without x-default, Google doesn’t know what to show users whose language isn’t covered.

Do language versions affect load speed?¶

Subfolders (yourstore.com/de/) don’t affect speed - it’s just URL structure. But some translation apps add JavaScript that can slightly slow page loads. Weglot, for example, loads translations via CDN which minimizes impact on Core Web Vitals.

Should I translate the blog for SEO?¶

Yes, but only posts with actual search demand in the target language. Not every English blog post needs translating - do keyword research first and write (or translate) only topics where there’s organic demand in that language.

Where to find native speakers for translation review?¶

Fiverr, ProZ.com, Upwork - for one-off tasks. Or partnership with a local agency for larger scale. For critical pages (checkout, homepage) - native speaker only. For the rest of the catalog - automation with selective review.