Shopify Multi-Language SEO: How to Set Up Translated Content Search Engines Can Actually Index

A related guide on this blog, Shopify Hreflang: What Markets Sets Up Automatically (and What You Still Need to Check), covers the hreflang tag itself. The signal that tells Google which language version of a page to show a given searcher. This post covers the step that has to happen before any of that matters: actually creating a translated, published, indexable page for hreflang to point at. Shopify splits that job across two separate tools — Markets, which sets up the market and URL structure, and Translate & Adapt, which does the actual translating — and it’s entirely possible to switch one on without the other. And end up with a language switcher pointing at content that isn’t really there yet.

Multi-language on Shopify is two separate systems, not one setting

“Shopify multi-language” isn’t a single toggle. It’s the combination of two tools that don’t automatically talk to each other to finish the job:

• Markets defines the region, the URL structure (domain, subdomain, or subfolder), the currency, and which language is assigned to that market.
• Translate & Adapt is the app that actually translates your product, collection, and theme content into that language and publishes it.

You can assign French to a market in Markets settings without a single word of your store having been translated in Translate & Adapt. Visitors landing on that market’s URL won’t see a broken page. Shopify falls back to showing your original-language content for anything that hasn’t been translated yet. It looks like the store “works” in French. It just isn’t actually French, and there’s nothing genuinely new for a search engine to index.

Step 1: Translate your content in Translate & Adapt

Translate & Adapt (Shopify’s own translation app) lets you auto-translate up to two languages for free using Shopify’s built-in AI translation. Beyond that, you add languages and edit translations manually. Resource by resource, in a side-by-side editor.

Two things worth knowing before you rely on it:

• Review before you publish. Shopify’s own guidance is to review auto-translated content for accuracy before it goes live — auto-translation is a starting draft, not a finished, publish-ready page.
• Coverage has real gaps. Store policies aren’t auto-translated and have to be translated manually. Collection filters, product images, tags, and most third-party app content aren’t covered unless that app has specifically built its content as a translatable resource.

Step 2: Publish it — this is what actually creates an indexable page

Saving a translation in the editor isn’t the same as it existing publicly. Publishing a language in Translate & Adapt is what makes the translated content visible to customers and crawlable by search engines. Per Shopify’s own documentation, publishing creates unique translated URL handles for each translated page, sets up redirects from the default-language URLs to those new translated URLs, and updates your sitemap to include them.

That URL-creation step is the part that’s easy to miss. Until a language is published, you don’t have a second set of real pages. You have translated text sitting in an editor.

Step 3: Give that language its own URL structure in Markets

Back in Markets, assign the published language to a market with a distinct URL: a subfolder (Shopify’s own example is a structure like yourstore.com/fr/), a subdomain, or a separate country-code domain. This is also the condition that determines whether Shopify generates hreflang tags for that market at all.

A market sharing the same URL as another one (say, a currency-only market with no language or URL change) doesn’t get its own page, so there’s nothing for hreflang to tag. The mechanics of that tag are covered in the hreflang guide. The point here is just that translating and publishing content (steps 1 and 2 above) has to happen first, or a correctly configured market URL is just an empty shell.

Where this leaves gaps that outlast the setup

Even after translation and publishing, a few spots reliably get left half-done:

• Policies. Refund, privacy, and shipping policy pages stay in your default language unless someone translates them by hand. They’re excluded from auto-translation entirely.
• Image alt text and file names. Translate & Adapt covers text content. It doesn’t rewrite alt text or rename image files for a second language, so translated product pages can end up with alt text still in your original language.
• Meta titles and descriptions. Translating the on-page copy doesn’t automatically rewrite the SEO meta for that locale — a common miss that leaves a French product page ranking with an English search snippet.

How to check your own setup is actually finished

1. Open the market’s live URL directly (not just the language switcher) and read a product page in that language. If it’s still showing your default-language copy, the translation hasn’t been published for that resource.
2. Check the sitemap for the translated URLs. Published translations should appear in your sitemap under their own URL handles.
3. Run a site: search restricted to the market’s subfolder or domain to confirm Google has actually indexed the translated pages, not just that they exist.
4. Scan meta titles, descriptions, and alt text on the translated pages the same way you would your primary store. They don’t inherit optimization from the original-language version automatically.
5. Confirm hreflang is present once content is live — covered step by step in the companion hreflang guide.