Skip to content
Shopify

How to Translate a Shopify Store Properly: Apps, Full Translation, and the SEO That Gets Each Language Found

Translate your Shopify store so buyers in each market can find it and buy from it: free app limits, paid apps, and the SEO setup per language.

By Lynxwell Digital October 31, 2026 11 min read
How to Translate a Shopify Store Properly: Apps, Full Translation, and the SEO That Gets Each Language Found

To translate a Shopify store properly, translate the whole buying path — products, navigation, checkout wording, policies, and emails — not just the product titles, and set up the SEO so Google can find and rank each language version. Shopify's free Translate & Adapt app covers a language or two; paid apps scale by word count for bigger catalogues; and your money pages still need a human translator who knows the market.

If a shopper in Germany lands on your store and everything is in English, you have not lost them to a competitor — you have lost them to friction. They can probably read some of it. They will not buy through it.

That is the difference between a translated store and a store with a translate button on it. The first one takes orders in a new market. The second one looks international and converts like it isn't.

What does "properly translated" actually cover?

Most stores translate the easy half and ship it. Product titles, a few descriptions, the homepage hero — done. Then the buyer hits the parts nobody translated: the shipping and returns policies, the checkout-adjacent pages, the navigation labels, the email notifications, the search results, the size guide, the FAQ. Each untranslated piece is a small reason to stop, and they add up exactly at the point where someone was about to pay.

A properly translated store covers the full path, in this order: product and collection pages first, then navigation and site search, then cart and checkout wording, then policies and shipping information, then emails and notifications, then blog and landing pages. If your budget only stretches to part of the list, spend it in that order. A translated blog with an English checkout is backwards.

What does Shopify translate for free?

Shopify's own app, Translate & Adapt, is free, and for a first language it is the right starting point. It translates store content through a side-by-side editor, lets you adapt wording per market (so, for example, spelling and phrasing can differ between markets that share a language), and handles the language setup alongside Shopify Markets.

The limit to know before you plan around it: automatic translation is capped. Shopify's help docs say stores can auto-translate up to 2 languages, or up to 8 in select countries including the US, UK, Canada, Germany, France, Spain, Italy and others on that list — and the Auto-sync feature that keeps translations current is only available in those select countries. Everywhere else, you re-translate after you change content, or you pay someone — or something — to keep up. Manual translations are not capped the same way, but manual means someone actually doing the work, page by page.

So the free route works well for one or two languages on a store that does not change its catalogue every week. It breaks down as a plan when you have five languages and a catalogue that changes constantly, because the maintenance is where the cost hides. New products launch in English and sit untranslated for weeks. Sale banners go up in one language. Nobody owns the second-language version, so it quietly goes stale.

When is a translation app worth paying for?

Paid translation apps exist for the stores the free app stops fitting: more languages, bigger catalogues, and workflows where a team reviews and edits translations instead of one person pasting text. Weglot is the best-known example, and its pricing shows how the cost scales: a free tier covers 1 language and 2,000 words, Starter is $17 a month for 1 language and 10,000 words, Business is $32 a month for 3 languages and 50,000 words, and Pro is $87 a month for 5 languages and 200,000 words, per its Shopify App Store listing. The unit that matters is words, not pages — a store with long descriptions and hundreds of products burns through a word allowance far faster than a store with fifty short listings.

That word-count model is the question to ask any paid app before you commit: how many words does your store actually have, across products, collections, pages, navigation and policies? Count it first. An app that looks cheap at $17 a month is not cheap once your catalogue pushes you two tiers up, and switching apps later means re-doing the translations or migrating them — work nobody budgets for.

What is full translation, and when do you need it?

Full translation is what it sounds like: a person who knows the market translates your store, including the words that decide a sale. That matters most on your money pages — bestsellers, landing pages for ads, and the pages that answer "will this fit, when will it arrive, what if I want to return it." Machine translation gets the meaning roughly right and the selling wrong: it translates your headline word for word instead of writing the headline a local shopper would click, and it keeps your English keyword choices instead of the phrases people in that market actually search for.

Here is the practical split. Machine translation is fine for the long tail: the hundreds of product pages that each sell a little. Human translation belongs on the pages that carry the revenue: your top 20 products, your homepage, your category pages, your ad landing pages, and your policies. Most stores do not need everything human-translated. Every store needs its money pages human-translated, because that is where a clumsy sentence costs an order instead of just looking clumsy.

The other half of "full" is not language at all — it is local fit. Prices in the local currency, shipping times stated for that country, sizing written the way that market expects, payment methods that market actually uses. A perfectly translated page that shows the wrong currency or a delivery estimate for another continent still does not sell.

How does the SEO work for each language?

This is where most translated stores fail quietly. Translating the pages is only half the job; Google has to understand that the German page is the version for German searchers, not a duplicate of the English page competing with it.

Shopify Markets handles the plumbing when it is set up with domains, languages and localised content: Shopify's own docs say hreflang tags, canonical URLs, sitemaps and crawler access are handled automatically. Hreflang tags tell search engines which version of a page to show for each language and region, so your translated pages are not flagged as duplicates. You can use subfolders, subdomains or top-level domains for each market; subfolders on your main domain are the usual default because they keep all the authority on one domain.

What Shopify cannot do is the strategy part, and this is the gap the top search results mostly skip. First, keyword research per language: a direct translation of your English keywords is often not what people search in that market, so your translated pages need their own keyword targets, titles and meta descriptions — not copies of the English ones. Second, translated metadata: titles and descriptions that stay in English while the page is translated will underperform in local search. Third, duplicate hreflang tags from an old translation app or theme code — Shopify's docs warn to use either its automatic tags or your own, not both, or Google may ignore them. Fourth, translated pages that are published but never linked in navigation: search engines and shoppers both struggle to find them.

The check before you call a language "live": search for your product in that language, in that market, and see which version of your store shows up. If the English page ranks instead, or nothing does, the translation is not finished — the SEO setup is not.

Which markets should you translate for first?

Do not translate for every country you ship to. Translate for the markets already sending you traffic or orders, in order of evidence. Check your analytics for where visitors already come from, check where orders already ship, and check which markets your ads already reach. One well-translated language for a market that already buys from you beats five half-translated languages for markets that have never visited.

One language at a time is also how you keep quality up. Launch it, check the whole buying path in that language yourself, fix what reads wrong, watch it for a month, then add the next one. Stores that launch six languages at once almost always launch six versions of the same half-finished job — and then nobody on the team knows which one broke when something changes.

The cost question, answered plainly

There are three bills, and only the first one is obvious. The tool bill: free with Translate & Adapt for a language or two, or a monthly app fee that scales with words and languages. The translation bill: machine translation is cheap and rough, human translation costs per word and belongs on money pages. The maintenance bill: every new product, every sale banner, every policy change has to reach every language, or your store drifts back to half-translated within a quarter. Budget for the third bill before you pick the first two, because it is the one that decides whether the translation is still good in six months.

A store doing this properly for one new language should expect the setup to be a project, not an afternoon: language and market setup, translation of the buying path, SEO checks per language, and a named owner for keeping it current. That is also why it pays back — it is a moat. Competitors can copy your product; they cannot copy a store that reads, ranks and sells in a market they have not bothered to enter properly.

What we'd do

If a store owner came to Lynxwell Digital with an English-only store and one foreign market already sending traffic, we'd start narrow. Translate & Adapt for the full buying path in that one language first, then a human pass over the top products, the homepage, the policies, and any page ads point to — and the per-language SEO checks before the language is announced. We'd leave the long tail of the catalogue to machine translation until the first language earns its keep. That order puts the money where a clumsy sentence costs an order, and it keeps the maintenance bill survivable when the catalogue changes.

What to do next

Pick the one market already sending you traffic that you have not translated for yet. Check whether Translate & Adapt's free auto-translation covers it, count your store's words before you price a paid app, and translate the buying path — not just the product titles — before you announce the new language. (Still deciding the store's foundations? Our guides to Shopify's plans and Shopify vs WooCommerce cover those choices.) And if you want the whole thing handled — market setup, translation workflow, and the SEO checks per language — send Lynxwell Digital your store URL and tell us which market you want first. We will look at what is already translated, what is missing, and what the first language should cost to do properly.

FAQ

Can I just use Shopify's free Translate & Adapt app?

Yes, for a first language or two. It is free and covers store content with a side-by-side editor, but automatic translation is capped at 2 languages (8 in select countries), and Auto-sync is only available in those select countries — so on a fast-changing catalogue, keeping translations current becomes manual work.

Does Shopify handle hreflang automatically?

Yes, when markets are configured with domains, languages and localised content, Shopify generates hreflang tags, canonical URLs and sitemaps automatically. You still own keyword research per language, translated titles and meta descriptions, and making sure no old app or theme code adds a second set of hreflang tags.

Should I translate every page, or just the products?

Translate the full buying path in order: products and collections, navigation and search, cart and checkout wording, policies and shipping information, then emails and notifications. A translated product page with an English checkout and English returns policy loses the sale it just won.

Is machine translation good enough for a store?

For the long tail of product pages, usually yes. For the pages that carry revenue — bestsellers, ad landing pages, homepage and policies — get a human who knows the market to review or write them, because machine translation keeps your English selling angles instead of the phrases local shoppers search and trust.

How much does a paid translation app cost?

It depends on words and languages, not pages. As an example from its Shopify App Store listing, Weglot's free tier covers 1 language and 2,000 words, Starter is $17 a month for 1 language and 10,000 words, Business is $32 a month for 3 languages and 50,000 words, and Pro is $87 a month for 5 languages and 200,000 words. Count your store's total words before choosing a tier.

#Shopify#store translation#international SEO
All posts

So, what are you building?

Tell us about it. The first conversation's free: no pitch, no “let's circle back,” just an honest take on how we'd do it and a real number.

First call's free
5.0 · usually replies in ~2 hours
  • Real human replies in ~2 hours
  • Fixed price, agreed before you pay
  • No lock-in, you own everything
  • Free first call + honest audit