# A professional shop available in eleven languages

> A B2B distributor sold into several European countries but presented its catalogue in only two languages, which limited its credibility in some markets.

- Source canonique : [https://allaux.fr/en/realisations/site-b2b-multilingue-onze-langues](https://allaux.fr/en/realisations/site-b2b-multilingue-onze-langues)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## The context

The professional customer base was spread across much of Europe, but the shop spoke only two languages. Customers in other countries browsed in a language that wasn't their own, which hurt confidence when placing orders for significant professional amounts. The goal was to extend the shop to eleven languages, without ending up with eleven catalogues to maintain separately or SEO diluted across versions.

The difficulty wasn't so much the translation as structuring the multilingual setup correctly: clean URLs per language, markup clearly telling Google which version addresses which audience, and handling fields that deliberately shouldn't be translated, such as internal references.

## What I did

1. **Technical structuring of the multilingual setup** — Setting up dedicated URLs per language and hreflang tags linking each version of the same page together, to avoid any duplicate-content signal.
2. **Organising translatable content** — Drawing a clear line between fields to translate (descriptions, editorial content) and fields to keep identical (references, standardised technical specifications).
3. **Structured data per language** — Updating structured-data markup so it stays consistent and accurate in each of the eleven languages, rather than settling for roughly translated markup.
4. **Translation and update workflow** — Setting up a process for easily identifying content not yet translated or that's gone out of date after an update to the source catalogue.

## The trap of poorly structured multilingual setups

> Adding languages without hreflang or distinct URLs often amounts to creating content search engines perceive as duplicated, which can hurt SEO rather than improve it.

## FAQ

### Why not just translate the pages with an automatic plugin?

An automatic translation displayed without correct technical structuring (clean URLs, hreflang) creates a risk of duplicate content in search engines' eyes, on top of translation quality that's often insufficient for professional use.

### Do all eleven languages have the same level of content?

The catalogue and transactional pages are covered in every language; some secondary editorial content may stay prioritised for the higher-volume languages.

### How is a new language added afterwards?

The architecture set up allows an additional language to be added without reworking the existing structure: it's mainly a translation job, not a development one.

### Was SEO affected during the rollout?

The rollout happened language by language, with hreflang markup checked at each step, to avoid sending any conflicting signal to search engines.