Multilingual websites
Language estates that sell, rather than translated pages that reassure.
A buyer who has to read about an engineered product in their second language, in copy that was obviously translated by machine, draws conclusions about the company before they reach the specification.
Where multilingual sites usually fail
A multilingual international website gives buyers in each target country a complete commercial experience in their own language — pages, navigation, forms, validation, confirmations and follow-up email. The technical requirement is correct language and country architecture with reciprocal hreflang and self-referencing canonicals. The commercial requirement is that the language never breaks partway through the journey.
Most failures are continuity failures. The landing page is in German, the navigation is in German, and then the contact form, the validation message or the confirmation email is in English. The buyer notices immediately, and it costs credibility exactly at the point of commitment.
The second failure is machine translation. Technical B2B language does not survive it, and native buyers can tell within a paragraph. Terminology in particular — the words a market actually uses for a product category — is rarely what a translation engine produces.
The third is technical: missing or non-reciprocal hreflang, inconsistent canonicals and duplicated country pages, which leave search engines uncertain which page belongs to which audience.
What this includes
Language architecture
One canonical convention per language, self-referencing canonicals and reciprocal hreflang across the whole estate.
Native commercial content
Copy written for the market and reviewed for commercial accuracy, not machine-translated.
End-to-end continuity
Navigation, footer, forms, validation, errors, confirmations and emails all in the visitor's language.
Language persistence
A chosen language that survives navigation, return visits and links arriving from email.
Honest English-only labelling
Where a resource genuinely only exists in English, it is labelled as such in the reader's language before they click.
Native metadata
Titles, descriptions and structured data written in-language rather than translated after the fact.
When it is the right piece of work
Selling into several European markets
Buyers in each country expect to evaluate in their own language, particularly for technical products.
Distributors in multiple countries
Partners need local-language material that supports their own selling.
An English-only site in non-English markets
Traffic exists but converts poorly, because evaluation stops where the language does.
A translated site that under-performs
Pages exist in other languages but read as translation and break at the point of enquiry.
Common questions
The ones where you have a genuine commercial route to market. A language estate with no salesperson, distributor or fulfilment capability behind it generates enquiries nobody can serve, which is worse than not having it.
For most B2B businesses language subdirectories on one strong domain are the pragmatic answer, because they concentrate authority and are far simpler to maintain. Country domains can be justified where markets are genuinely separate businesses.
No. Language and market are different things. One German estate can serve Germany, Austria and much of Switzerland, while a single market may need more than one language. The architecture should reflect how buyers actually read and buy.
Native review before publication, with commercial review to make sure terminology matches what the market actually calls the product.
Related capabilities
The full digital commercial capability and how the parts fit together.
The commercial strategy the digital estate is built to serve.
The commercial person in the territory who works behind the infrastructure.
Working out what your expansion actually needs?
Tell us the markets, the languages and the commercial objective. We will set out what infrastructure is genuinely required — and what is not worth building.