Shopify Multilingual SEO: How to Rank in Every Language
Here's a mistake that costs merchants thousands in lost traffic: they translate every product on their store, hit publish — and still don't rank in a single foreign-language search.
Translation makes your store readable in another language. Multilingual SEO makes it findable. They're not the same thing, and skipping the second one means your beautiful translations sit on page 5 where no one sees them.
This guide covers what it actually takes to rank a Shopify store in multiple languages: how Shopify's localized URLs and hreflang work under the hood, which fields Google reads that shoppers never see, how to find the keywords locals actually type, and how to verify the whole thing is working instead of hoping.
Why translated stores still don't rank
When you publish a language in Shopify, it creates localized URLs — yourstore.com/fr/products/leather-tote alongside yourstore.com/products/leather-tote. That part is automatic and it works. What isn't automatic is everything that makes those URLs competitive:
- The meta titles and descriptions are still in English, so your SERP snippet is English even though the page is French
- hreflang is present but broken, because half the catalog has no French equivalent
- Your internal links all point back to English URLs, fragmenting authority
- The translation reads like machine output, so bounce rate climbs and engagement signals sag
Each of these is fixable. Fix all four and you're competing in markets where keyword difficulty is a fraction of what you face in English — which is the entire commercial argument for going multilingual in the first place.
Understand what Shopify gives you for free
Before optimising anything, know where the platform's responsibility ends and yours begins.
Shopify handles:
- Localized URL generation for every published language
hreflangannotations in the<head>of localized pages- Locale detection and the redirect prompt for first-time visitors
- Serving the right translated string when your theme requests it
You handle:
- The quality and completeness of every translated string
- Translated SEO meta fields (they are separate translatable resources, not derived from body text)
- Keyword choice per language
- Internal link structure and navigation
- Keeping translations current as products change
A useful mental model: Shopify builds the road, you decide whether anything worth driving to sits at the end of it. If you haven't set up markets yet, Shopify Markets explained and how to set up Shopify Markets for multiple languages and currencies together cover the configuration side.
1. Get hreflang right
hreflang tags tell Google "this page is the French version of that English page." Without them, Google may serve the wrong language to a searcher, or treat your translations as competing duplicates of each other.
The good news: Shopify automatically adds hreflang tags for languages you have published through Markets. The catch is in the word published — and in what those tags point at.
A valid hreflang cluster has three properties, and most broken implementations fail the second or third:
- Every version declares every other version. Shopify handles this.
- The links are reciprocal and real. If your English page declares a French version, that French URL must return 200 with genuinely French content. A page that falls back to English text still returns 200 — Google sees two "different language" URLs with identical content and quietly drops the annotation.
x-defaultpoints somewhere sensible. Usually your primary market's homepage, so searchers from unlisted countries land somewhere coherent.
Point 2 is where partial translation does real damage. A catalog that's 60% translated doesn't give you 60% of the benefit — it gives you a cluster full of contradictions that Google resolves by trusting none of it. Translate a language completely or don't publish it. That single rule prevents most hreflang problems.
For the tag-level detail — syntax, region codes, script variants like zh-Hans versus zh-Hant — see the complete hreflang guide for Shopify. If you're new to translating altogether, start with the complete guide to translating a Shopify store.
Verifying hreflang without guessing
Google Search Console's old International Targeting report was retired, so don't go looking for it. Use these instead:
- URL Inspection in Search Console on a localized URL: check that Google fetched it, indexed it, and picked the URL itself as canonical rather than the English original
- View source on a localized page and confirm the
alternatelinks list every published language plusx-default - A third-party hreflang validator to catch non-reciprocal or non-200 alternates across a sample of URLs
- The
site:operator with a locale prefix (site:yourstore.com/fr/) as a rough index-coverage check
The failure you're hunting for is "Duplicate, Google chose a different canonical" on localized URLs. That means Google is folding your French pages back into the English ones — nearly always because the French content isn't different enough, which means it isn't really translated. Duplicate content in multilingual SEO goes deeper on diagnosing this, and multilingual reporting in Google Search Console covers how to segment performance by language once things work.
2. Translate the fields Google actually reads
Visible product text is the obvious part. Rankings depend heavily on fields shoppers never see:
- SEO title (meta title) — the single strongest on-page signal you control
- Meta description — doesn't rank you, but drives the click that follows the ranking
- Image alt text — feeds image search, which converts unusually well in fashion and homeware
- Collection and page meta fields — collection pages are often your best category-term landing pages
- Metafields and metaobjects — if your theme renders spec tables, size guides or care instructions from custom data, those are body content to Google even though they don't live on the product description
In Shopify these are separate translatable resources. Translating a product description does not translate its SEO title; they are distinct fields that each need their own translated value. This is the most common reason a store with fully translated body copy still shows English snippets in French SERPs.
Two things worth knowing about URLs specifically: Shopify keeps the same handle across languages — /fr/products/leather-tote, not /fr/produits/sac-cuir — so don't budget effort for translating slugs. The locale prefix is the differentiator, and that's fine; it costs less than people assume.
Deeper dives: translated meta descriptions and SEO, translating metafields, metaobjects and custom data, and translating structured data and schema markup.
A quality translation app translates the meta fields alongside the visible content — StoreLingo, for instance, translates product and collection SEO fields automatically rather than leaving them for a second manual pass.
3. Match search intent in each language
Direct translation isn't always the highest-ranking keyword, and this is where most automated approaches leave money on the table.
"Trainers" in the UK are "sneakers" in the US and "baskets" in France. A German shopper searching for a duvet types Bettdecke; a literal translation of "comforter" gets you nowhere. Spanish splits hard across markets — a móvil in Spain is a celular in Mexico. These aren't translation errors. They're the difference between a page that ranks and a page that doesn't.
Three levels of effort, pick by page value:
For your top 20 products and collections, do real keyword research in the target language. Check search volume for two or three candidate phrasings, look at what the top-ranking local competitors call the product, and set the translated SEO title to the winner. This is a couple of hours of work that determines the ceiling on the entire language.
For the mid-tail, make sure your translation engine is producing natural local phrasing rather than word-for-word output. This is one concrete reason AI translation beats literal machine translation for SEO: it picks the idiomatic term instead of the dictionary one.
For the long tail, let good automated translation run and don't over-engineer it. The traffic per page is too small to justify manual review.
Multilingual keyword research walks through the process in detail, and localized vs translated content covers where the line sits between the two.
4. Localize internal links and navigation
Your internal linking structure passes authority between pages. If every translated page links back to English URLs, you fragment that authority and confuse crawlers about which cluster a page belongs to.
What to check:
- Menus and navigation are translated, and their links resolve to localized URLs
- In-content links between translated pages stay within the same language
- Your language switcher uses real anchor tags with
hrefattributes, not JavaScript click handlers — a switcher that crawlers can't follow is a switcher that doesn't distribute authority - Footer and policy links point at the localized versions, not the English originals
The switcher point catches a surprising number of stores. See how to add a language switcher to your Shopify store for markup that works, and multilingual internal linking for the structural side. Menus, filters and faceted navigation have their own quirks, covered in translating navigation menus, filters and faceted search.
5. Keep translations fresh
Search engines reward maintained content and punish stale, broken pages. The problem is structural: every time you edit an English product description, its translations silently become wrong. Multiply by a catalog that changes weekly and by six languages, and "we'll update them later" becomes "half our international catalog is out of date."
Change detection — flagging exactly which fields changed so you re-translate only those — is what makes this survivable. Without it you either re-translate everything on a schedule (expensive) or let drift accumulate (worse). StoreLingo re-translates changed content automatically; keeping translations in sync on Shopify covers the workflow whichever tool you use.
Two habits worth building:
- When you bulk-edit products, treat the translation refresh as part of the same task, not a separate project
- When you update
dateModifiedon a page, make sure the localized versions get the same treatment — a French page frozen two years behind its English original reads as abandoned
6. Don't translate thin or duplicate content
Translating low-value pages at scale multiplies whatever quality problem you already have. A hundred thin English pages become six hundred thin pages across six languages, and Google's scaled-content signals are not forgiving about that.
Focus your translation budget on:
- Revenue-driving products and collections
- Genuinely useful pages — buying guides, FAQs, sizing, care instructions
- Blog content that targets local keywords
And deliberately skip: near-duplicate variant pages, tag-generated collections nobody searches for, thin supplier-copy product descriptions you haven't rewritten. Quality over quantity applies in every language, and it applies harder when you're multiplying.
7. Measure by language, not in aggregate
If you look at total organic traffic you will never see whether German is working. Segment from day one:
- In Search Console, filter Performance by page containing
/de/to get impressions, clicks, CTR and average position for that language alone - In GA4, build a comparison on landing-page path prefix so you can see conversion rate per language, not just sessions
- Track impressions before clicks. A new language typically shows impressions climbing for four to eight weeks before meaningful clicks arrive — impressions rising with a bad average position means you're indexed but not competitive, which is usually a keyword or meta-title problem, not a translation problem
Measuring ROI from a multilingual store sets out the full reporting structure. The short version: a language that's been live for three months with impressions and no clicks doesn't need more translation, it needs better titles.
A practical multilingual SEO checklist
- Target languages published in Shopify, not just added
- Every published language translated completely — no partial catalogs
- hreflang verified with URL Inspection and a validator,
x-defaultset - Meta titles + descriptions translated for every indexable page
- Image alt text translated
- Metafields and metaobjects rendered by the theme translated
- Top 20 products keyword-researched in each target language
- Internal links, menus and language switcher localized and crawlable
- Change detection in place so pages don't go stale
- Thin and duplicate pages excluded from translation
- Search Console and GA4 segmented by locale prefix
Work top to bottom. The first four items are worth more than the rest combined.
The shortcut
Most of this checklist comes down to one thing: complete, high-quality, maintained translations including the SEO fields. Get that right and Shopify's native hreflang does the heavy lifting for you.
StoreLingo translates products, collections, pages, and articles — including SEO meta fields — with AI. Merchants choose from 47 languages. By default you review and approve before publishing. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. It keeps everything in sync as your catalog changes.
Start ranking in every language your customers search in. Add StoreLingo on the Shopify App Store →
FAQ
Does Shopify add hreflang automatically? Yes, for languages you publish through Markets. You still need to translate the content and meta fields for those tags to be meaningful — hreflang pointing at an untranslated page is worse than no hreflang, because Google resolves the contradiction by ignoring the annotation.
Will multiple languages create duplicate content penalties? No, as long as hreflang correctly identifies each language version and the versions genuinely differ. Duplicate-content problems in multilingual stores almost always come from partial translation, not from having multiple languages.
Should I use subfolders or subdomains for languages?
Shopify uses subfolders (/fr/, /de/) by default, which is the recommended, lowest-maintenance approach for most stores: they inherit the authority of your main domain. Country-code domains can outperform in markets where local trust matters, at the cost of building each domain's authority separately. Subfolders vs subdomains compares the three options.
Can I translate my URL handles? No. Shopify keeps the same handle across languages and differentiates by locale prefix. This is a smaller ranking factor than translated titles and content, so it's not worth working around.
How long before a new language starts ranking? Expect impressions within two to six weeks of the localized URLs being indexed, and meaningful clicks in the two-to-four-month range for competitive terms. If impressions aren't appearing after six weeks, the problem is indexation — check URL Inspection before touching the content.
Do I need a separate blog per language? Not necessarily, but translated blog content is often the fastest route to ranking in a new market because informational keywords are far less competitive than commercial ones. See translating Shopify blog posts for international readers.
Choose from 47 languages
StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.
Add to Shopify →