Multilingual ecommerce: how to structure it so you don’t penalise SEO or AI Overviews

Published on 7 minute read Team Tecnico Studio Mate

Structuring a multilingual ecommerce the wrong way can penalise your SEO rankings and reduce your chances of being quoted in AI answers just as much as not having a multilingual site at all. The most common mistakes are relying on the browser’s automatic translation instead of dedicated URLs for each language, forgetting the hreflang tag that tells Google which language version to show to each user, and duplicating content between languages without clear signals for search engines. In 2026, with Google AI Overviews and assistants such as ChatGPT increasingly drawing on multilingual content to answer international queries, the technical structure of a multilingual ecommerce affects visibility as much as the quality of the translation itself.

In this article we look at how to structure a multilingual ecommerce correctly, from a technical point of view, so that SEO and visibility in AI answers are not penalised.

Subdomains, subfolders or separate domains: which is the best structure?

There are three main ways to structure the languages of an ecommerce: subfolders (example.it/en/), subdomains (en.example.it), or separate country domains (example.com, example.de). For most Italian SMEs, subfolders are generally the most efficient choice: they inherit the SEO authority the main domain has already built up, they are simpler to manage technically, and they make it easier for Google to associate the different language versions with the same site.

Separate country domains make sense when the company already has a distinct market identity in each country (different prices, catalogues or branding), but they come with the cost of building SEO authority from scratch for every domain, a process that takes time and significant resources.

What is hreflang and why is it essential for a multilingual ecommerce?

hreflang is an HTML tag that tells search engines which language or regional version of a page to show, based on the language and location of the user performing the search. Without hreflang configured correctly, Google may show a French user the Italian version of the page (or the other way round), or it may interpret the different language versions as duplicate content, penalising the rankings of all of them.

Each translated page must declare, through hreflang, all its equivalent language versions, including an x-default version that indicates which language to show when no specific match is available. On WooCommerce, professional translation plugins manage this configuration automatically, but it should always be verified using the check tools in Google Search Console.

Browser automatic translation or structured translation: what is the difference?

A common mistake is to rely on the browser’s automatic translation (such as the built-in Google Translate) instead of creating real translated pages with their own URLs. The problem is that Google does not index translations generated dynamically by the browser: in the eyes of the search engine, those pages remain only in the original language, and the site never shows up in searches made in other languages. A structured translation, on the other hand, creates indexable URLs and content for every language, letting the site rank genuinely for searches done in that language, and also making it readable, quotable and reusable by AI assistants.

How to avoid duplicate content between the language versions?

Duplicate content does not arise from having several languages (which is correct and necessary), but from technical configuration mistakes: pages reachable through more than one URL without a clear canonical, missing or wrongly configured hreflang, or language versions that actually contain the same untranslated text. The solution is to make sure each language version has a unique URL, a self-referencing canonical tag, and correct reciprocal hreflang across all the languages available.

It is also worth avoiding mechanically translating content designed for the Italian market without adapting it: a translated page that is not culturally relevant to the target market tends to generate less engagement, a signal that search engines interpret over time.

How do you structure a multilingual ecommerce so that AI Overviews will cite it?

AI assistants and Google AI Overviews tend to favour well-structured content, with direct answers and clear semantic markup, regardless of the language. For a multilingual ecommerce, this means keeping the same structural quality (clear headings, lists, tables, FAQs) in every language, not only in the main one: an English or German version translated quickly and with no structure is less likely to be quoted than a carefully crafted Italian version.

Structured data (schema.org) for the product, price, availability and reviews also has to be implemented consistently across all language versions, so that each language has the same chance of appearing in rich results and AI answers for its own local searches.

Technical checklist for a correct multilingual ecommerce

  • Use subfolders (/en/, /de/) for each language, unless you have specific reasons for a separate domain.
  • Configure reciprocal hreflang on all translated pages, including the x-default version.
  • Create indexable pages for each language, avoiding dynamic browser translations.
  • Set a self-referencing canonical on every language version.
  • Keep the same semantic structure (headings, lists, FAQs) in all languages.
  • Implement structured data consistently on each language version.
  • Localise, don’t just translate, content and calls to action for every market.

At Studio Mate we structure multilingual ecommerce projects by taking care of the technical architecture from the very beginning (hreflang, canonical, URL structure), so the store is not only translated correctly but keeps, and can continue to grow, its SEO visibility in every activated language market, instead of dispersing the authority it has already built up in Italian.

In summary

A well-structured multilingual ecommerce uses subfolders for each language, configures hreflang correctly on every page, creates content that is genuinely indexable (not dynamic browser translations) and avoids duplicate content with self-referencing canonical tags. Keeping the same structural quality (headings, lists, FAQs, structured data) in each language increases the chances of ranking in search engines and of being cited by AI Overviews and AI assistants on all the markets served, not just the Italian one. Technical mistakes at this stage are among the most common causes of poor international visibility for ecommerce sites that are otherwise well translated.

Frequently asked questions

Are subfolders, subdomains or separate domains better for a multilingual ecommerce?

For most Italian SMEs, subfolders (example.it/en/) are the most efficient choice: they inherit the SEO authority of the main domain and are simpler to manage technically than subdomains or separate country domains.

What happens if I don’t configure hreflang correctly?

Google may show users the wrong language version, or interpret the different languages as duplicate content, with a negative impact on the rankings of all versions involved, not just the one with the error.

Is the browser automatic translation enough for a multilingual ecommerce?

No: those translations are not indexed by search engines, so the site does not show up for searches performed in other languages. You need translated pages with their own URLs and genuinely indexable content.

Do I also have to translate the structured data (schema.org) into each language?

Yes, structured data must be implemented consistently in every language version, so that each language has the same chance of appearing in rich results and AI Overviews answers for its own local searches.

How many languages should you activate at the beginning of a multilingual ecommerce?

It is better to start with one or two languages done well, with a correct technical structure and carefully localised content, rather than activate many languages translated roughly: the quality of the structure weighs more than the number of languages available.

T
Team Tecnico Studio Mate

Team tecnico Studio Mate — sviluppo software su misura.

The service we talk about in this article

Ecommerce

Discover the service