Shopify Markets and AI translations: 5 multilingual SEO pitfalls

How Shopify serves translated content

A Shopify store has one catalogue and one set of source content. Languages are added in the Languages settings, then assigned to markets, and each market can have its own default language. Customers reach a language through a dedicated URL: a subfolder such as example.com/de, a subdomain such as de.example.com, or a separate top-level domain such as example.de. Shopify’s own guidance calls subfolders the simplest option and the one that benefits most from your existing domain’s authority.

A few things happen without you doing anything:

• hreflang tags are added automatically for every international domain, subfolder and language-specific URL. You can switch this off, but then you own the tags.
• Translated handles are possible: /products/chair can become /products/stuhl in German. The products segment itself stays in English.
• Redirects are created from the default-language URL to the translated URL when you add a translated handle.
• Unpublishing a language hides it from customers without deleting the translations, but its URLs then return 404, so you need redirects.

So the technical layer is mostly handled. What Shopify cannot check for you is whether the words behind those URLs are correct, complete and consistent.

What automatic translation does, and what it skips

Most stores translate with Shopify’s Translate & Adapt app, sometimes with a third-party translation app or an AI tool on top. Translate & Adapt covers products, collections, blog posts, pages and policies, and metafields can be localized too. According to the Help Center:

• You can automatically translate a maximum of two languages. Once a language has been auto-translated you cannot move that allowance to another language, and removing the language does not reset it. Other languages have to be translated manually or with another app.
• URL handles are not auto-translated. You add them by hand, language by language.
• After you run auto-translation, the translations take a few minutes to display on your storefront. There is no review step in between unless you create one.
• When the source content changes, translations go out of sync. Running auto-translate again updates the outdated ones but leaves the translations you added or edited manually untouched.

That last point is useful and dangerous at the same time. Your manual fixes survive, but a manual translation you wrote a year ago will not follow a new source description either.

The five pitfalls that cost rankings

1. Machine translation published without review

The fastest path is also the riskiest: click auto-translate, see the storefront update, move on. Machine translation gets most sentences right and a few badly wrong, and the wrong ones tend to be the ones that matter: sizes, materials, care instructions, legal wording. Google’s spam policies list automated translation among the techniques used to mass-produce pages that give users little value. Your own catalogue translated is not spam, but unread output is exactly how a store ends up publishing sentences no native speaker would write.

2. SEO fields left in the source language

Descriptions get translated because everyone can see them. The page title and meta description are invisible on the page, so they are the easiest fields to leave in English on a French storefront. Search results then show an English snippet for a French query. Check alt text and metafields that render on the page for the same reason.

3. Translated handles that change live URLs

A translated handle reads better to local customers, but adding one after a locale has been live and indexed changes the URL Google knows. Shopify creates a redirect from the default-language URL, but do not assume every older URL is covered, especially if a translated handle is edited a second time. Decide handles before launch, and when you change one, test the old URL.

4. Inconsistent terminology

“Jumper” on the product page, “sweater” in the collection, “pullover” in the meta title. Machine translation picks words sentence by sentence, and several AI tools working on the same catalogue pick differently. Customers notice, and you split the queries you could have matched. Keep a short glossary per language (product types, materials, sizes, your brand terms) and check against it.

5. Duplicate content across same-language markets

If the US and UK markets both use English, they share the same English translation. That is fine when hreflang is in place, and Google’s guidance for similar content in the same language is to pick a preferred version with rel="canonical" and use hreflang so the right regional URL is served. Problems start when hreflang is disabled, when separate domains serve identical copy without canonicals, or when you actually need regional wording. For the last case, Translate & Adapt lets you adapt content per market (its own example: “Sweaters” in the US, “Jumpers” in the UK).

A pre-publication checklist for each locale

Run it against the proposed translation, not the storefront.

1. Read by someone fluent in the language
2. Page title translated and within length
3. Meta description translated, not truncated
4. Handle translated before first indexing, not after
5. Old URL tested after any handle change
6. Product names and key terms match the glossary
7. Sizes, units and currencies correct for the market
8. Care, safety and legal wording checked word for word
9. Metafields that render on the page translated
10. Image alt text translated
11. Same-language markets checked for needed regional wording
12. hreflang still enabled in the domain settings

Reviewing each locale before it goes live

The checklist only works if there is a moment where someone looks at the translation before customers do. In Shopify alone that moment does not exist: a translation saved in Translate & Adapt, or pushed by an app, is live as soon as the language is published.

This is the gap Vetta fills. A translation is proposed as a version, by a person, a CSV import or an AI agent, and reaches the storefront only when a reviewer approves it. The review screen shows a field-by-field diff between what is live and what is proposed, with one tab per locale: title, handle, description, SEO title, meta description, tags and metafields, compared word by word. A native-speaking reviewer can open the German tab, see that the meta description is still in English or that the handle changed, and send it back with a note instead of approving it.

Because reviewers do not need Shopify admin access, you can invite the freelance translator or the colleague in the Milan office to check only their language. And every approved version stays in the history, so if a bad translation does slip through you can restore the previous one.

Where to start

Pick your highest-traffic locale and audit its twenty most visited product pages against the checklist, starting with the SEO title and meta description. Then decide your handles for any locale you have not launched yet, write the glossary, and set a rule that no translation reaches the storefront until someone who reads the language has approved it.