Multilingual store: what breaks between translation, addresses and search
Translating a store is a content project. Getting it found in the right language by the right buyer is an architecture project. Businesses almost always fund the first and discover the second six months later, when English-language traffic has not moved despite a complete translation.
- Language and country are two different things. A Belgian buyer reads in French and pays in euros, a Quebec buyer reads in French and pays in Canadian dollars.
- On a secondary market, the address has to combine language and country. A language-only subfolder exists only on the primary market.
- Google treats the declaration of versions as a hint, not as a directive. Genuinely distinct content weighs more than a perfect tag on a word-for-word translation.
- The most frequent break is not the translation, it is the page created outside the tool's flow: it is neither translated nor declared, and nothing flags it.
- A product page translated word for word misses the market's buying vocabulary. Buyers do not search for the translation of your words, they search for their own.
On this page
Language cannibalization
Language cannibalization happens when two versions of the same page, in two languages, compete for the same query because the engine never received a complete and reciprocal declaration of the available versions. It picks one, usually the more established one, and serves that version to every audience. The symptom is measurable: impressions in one language landing on the pages of another.
The three breaks in a multilingual store
They do not happen at the same moment and they do not show up in the same place.
The first is the incomplete translation. A store launches its English version with the main pages and the catalogue, then life resumes: a new product, a collection page, an article. Those additions are born in the original language and the catch-up has no owner. Six months later the secondary version is a subset of the store, and the customer who lands on a hole rarely comes back. The cost is invisible because it is counted in sales that never happened.
The second is the malformed address. It is not visible at all from the store admin, where everything looks fine. It shows up in the data, as impressions in one language on the pages of another. The demand exists, the wrong page gets served, and management concludes the market does not respond, then cuts the budget on the wrong line.
The third is the faithful translation. It is the most expensive because it passes every quality check. The text is correct, the grammar is good, and it contains none of the words buyers in that market actually type. The invoice is paid, the risk is untouched.
The order of magnitude is worth stating, because it determines who has to decide. Translating a mid-sized catalogue and maintaining it costs about as much as hiring a part-time resource for a year. That is not a line in a marketing budget, it is an investment whose return is measured in sales in a market you have not yet validated. The decision therefore belongs to management, exactly like the decision to open the market.
These three breaks share one trait that explains why they go unnoticed: none of them appears in a sales report. An incomplete translation does not lower revenue, it prevents an increase. That is the hardest kind of loss to defend in a budget meeting, and the one businesses fund the longest without knowing it.
The addressing rule, and why it exists
Language is not country. That distinction, which sounds theoretical, produces a very concrete rule: on a secondary market, the address has to carry both language and country, of the /fr-ca or /en-eu type. A language-only subfolder, of the /fr type, exists only on your primary market.
The reason is mechanical. On a secondary market, the address does not only pick a language, it serves the right currency, the right prices and the right terms. An isolated /fr does not tell the system which French it is, therefore which market, therefore which prices and which currency.
A store already using language subfolders keeps its existing addresses. It is the markets added afterward that follow the combined rule, which often produces a hybrid structure, consistent but surprising to anyone discovering it without explanation.
On the engine side, three declaration rules apply and integrations regularly miss them. Every version has to declare itself. Every version has to declare all the others. And the declaration has to be reciprocal, failing which the whole set is ignored rather than partly kept. Since Google retired its international targeting report in 2022, no official tool flags those errors at site level.
What to settle before translating
Translating a store runs into the tens of thousands of dollars for a mid-sized catalogue. The question is not whether to translate, it is what to translate, in what order, and who will keep the whole thing current once the invoice is paid.
- Which pages do we translate first, and on what criterion: sales or the full catalogue?
- Who translates new items, and does that process exist anywhere other than in a good intention?
- Does our secondary version target a language or a specific country, and does the address reflect that?
- Has the market's buying vocabulary been pulled, or are we translating our own words?
- Who checks, one month after launch, that the two versions are not competing for the same queries?
The answer that holds up names an order of priority and a person responsible for catching up. An answer about the number of pages translated measures a deliverable, not a result.
Deciding what to translate, in what order and under which structure is part of what we cover in a paid audit.
Translating is not getting found
A buyer does not search for the translation of your word, they search for their own. Those two words coincide less often than you would think, and the gap is widest exactly where your margin is best, on technical products.
Three gaps recur. The trade term first: two English-speaking markets can name the same product differently, and a professional translator will pick the correct term rather than the searched one. Units and formats next, which change how a product gets searched for. The standards cited last: a buyer often searches by the standard they have to meet, and a Quebec standard means nothing to them.
The translation order follows directly from that, and it is not the one people adopt spontaneously. Rank your pages by revenue generated over twelve months, translate the first tenth, measure for a quarter. A business that translates its whole catalogue at once commits the entire expense before getting any answer from the market, and sometimes discovers that demand sits on three product lines.
The correction is not a retranslation. It is a survey of the words searched in the target market, done before the translation, and handed to the translator as a constraint. It costs a few days and it changes the return on the whole project.
A perfect translation in the wrong words is a full expense for no result. Surveying the vocabulary costs three days and decides everything else.
Falia analysis gridWho keeps the translation current
This is the question that determines whether the project ages well, and it almost never has a written answer.
The break point is identifiable: any page created outside the flow of Shopify's Translate and Adapt app, or of whichever translation app you use, escapes the process. A product added by one team, a collection page built for a promotion, an article published by marketing. Nothing flags the absence, and the gap settles in one page at a time, without any sales report showing it.
The rule that works is to treat translation as a publishing step rather than as a project. A page is not live until its secondary version exists, or else it is explicitly accepted as unilingual, with a note for the visitor. Both choices can be defended, the absence of a choice produces a store full of holes.
The monthly check fits in two numbers: the number of pages published in the primary language and the number published in the second. The gap between them is your translation debt, and it reads in thirty seconds. As long as nobody tracks those two numbers, the debt grows without any meeting addressing it, because it appears in no sales report.
Before launching the translated version
Market structure is covered in opening a market without duplicating your store, and pricing in what multi-currency settles and what it leaves you. Quebec language obligations are in the language obligations on your website, and the opening sequence in your export plan does not say where the customers will come from.
The architecture choice that comes before these settings is covered in the address architecture for two markets. The decision is taken before the first translation, because it sets the maintenance budget and the room to manoeuvre in the target market.
Opening a market is the subject of the Develop a new market goal.
The visibility side runs through search optimization.
Frequently asked questions about multilingual stores
Why has our English traffic not moved after the translation?
Usually because the declaration of versions is incomplete and the engine serves the original version. The sign is measurable: English impressions landing on your French pages. That is a technical fix, not a market problem.
Why does /fr not work on a secondary market?
Because a language-only subfolder exists only on the primary market. On a secondary market the address has to combine language and country, of the /fr-ca or /en-eu type, so it also serves the right currency and prices.
Do you have to translate the whole catalogue?
Rarely at the start. Translating what sells and what gets searched first gives an answer in a quarter for a fraction of the cost. The rest gets translated as the market confirms demand.
Is machine translation enough?
To be understood, often. To sell, rarely, because it reproduces your words instead of using the market's. Surveying the buying vocabulary matters more than the translation method.
Who should translate new products?
The same person who publishes them, in the same motion. Treating translation as a publishing step rather than a separate project is the only rule that keeps the debt from accumulating.
How do you check that the two versions are not competing?
In Search Console, by comparing the impressions of one version's pages against the other's. Impressions in one language on the pages of another signal an incomplete declaration.
- Shopify, International domains, help centre, consulted August 2026. The rule on subfolders combining language and country on secondary markets, translation tools.
- Google Search Central, Tell Google about localized versions of your page, official documentation, consulted August 2026.
- Google, The international targeting report is deprecated, Search Console Help, consulted August 2026.

Geneviève puts the strategy for your engagement into action. She leads all our web development projects: Shopify, WordPress and the new ways of building a site with AI. She manages our team of developers and translates your business needs into technical language. She runs your organic search (SEO), your visibility in AI answers (GEO) and your site's conversion rate optimization (CRO). Her work is at the heart of three goals: Attract customers with SEO and AI, Improve your site's conversion, and Strengthen your visibility in AI answers. With Gabriel, she also builds the landing pages for your advertising campaigns. She writes mainly about SEO, AI visibility and web design.
About Falia →