Introduction
An industrial company exporting to France, Germany or the United Kingdom needs a website that works in those markets. That seems obvious. What is less obvious is what "works" means at a website level in an international market.
For a large number of industrial companies, "having the website in three languages" means having translated the content from Spanish into English and French. Sometimes with a generalist professional translator, sometimes with an automated tool, sometimes with an employee who "speaks English fairly well". The result is a version in other languages that exists, can be navigated and has all the pages. But it does not rank in the target market's search engines, does not use the technical terminology the local buyer recognises as standard in their sector and does not send the signal the professional visitor needs to take the supplier seriously.
The problem is not linguistic. It is structural. A poorly resolved multilingual website does not fail because of grammatical errors. It fails because its architecture, content and positioning are not designed to compete in each market as if they were native websites.
AI search engines are amplifying that difference. Google AI Overviews, ChatGPT, Gemini and Perplexity generate answers in the user's language and cite sources in that same language. If the French version of an industrial website does not have real technical content in French — with the correct regulatory references, sector vocabulary and structured data in that language — it will not appear when a French engineer asks an AI which European suppliers work with a particular material or certification.
Translating is not localising. And localising is not just adapting words.
The difference between translation and localisation is quickly explained in theory. In practice, the vast majority of multilingual industrial websites apply neither with rigour.
In industry, technical terms do not work the same way in every language. There are concepts that remain in English in certain markets and are translated in others. There are regulatory references that change by geography. There are product nomenclatures that vary between countries sharing the same language.
A German buyer in the pressure equipment sector works with PED 2014/68/EU just like a Spanish buyer, but searches Google with different terminology, references DIN standards as well as EN, and expects a different level of technical documentation. If the German version of the website simply translates the Spanish text, the result is a page that a German buyer immediately recognises as translated content, not as content designed for their market.
The same happens with technical French. In the food sector, French regulatory references — such as the Arrêté of 25 November 1992 for food-contact materials — do not appear if the content has been translated from a Spanish version that only mentions EC 1935/2004 and FDA. The French buyer in the food sector searches using their local regulatory framework. If the website does not contain it, that website does not exist for them in terms of search ranking.
Search intent changes between markets
It is not enough to translate keywords. The way a technical buyer searches varies between markets for reasons that go beyond language.
In some sectors, the English-speaking market maintains technical terminology in English that other markets translate partially or fully. "Food grade" is a term understood globally, but the buyer searching in German may be using "lebensmittelecht" or "lebensmittelkonform", terms with distinct nuances. Searching on Google France may combine French terms with anglicisms differently from how an engineer in the UK would.
A website that translates keywords from Spanish into literal English loses all of those variations. And each lost variation is a search that goes uncaptured in the target market.
The regulatory framework is not the same in every country
A manufacturer working with materials for regulated sectors needs to reference the applicable standards in each market. But within Europe, regulation has national layers that the generic version of the website does not account for: BfR in Germany, specific regulations in France, particular provisions in Italy.
If the French version of the website only translates the references from the Spanish version without adding those that apply specifically to the French market, the website loses relevance for the buyer searching within that regulatory framework. And it loses search ranking for engines that index those references as highly specific technical terms.
The technical architecture of a multilingual website
Content localisation is useless if the website's technical architecture does not correctly support the multilingual structure. There are infrastructure decisions that determine whether search engines will index, classify and rank each language version independently or treat it as duplicate or subsidiary content.
Each language version needs its own URL structure with translated slugs, not transliterated ones. A website that keeps URLs in Spanish for all language versions is sending a contradictory signal to search engines: the content is in French but the URL remains in another language. That inconsistency affects ranking.
Hreflang tags tell search engines which version of a page corresponds to which language and region. They are the mechanism by which Google decides which version to show to each user. Incorrect hreflang implementation is one of the most common technical errors on multilingual websites. According to industry data, around 70% of multilingual sites have errors in their hreflang tags: tags pointing to non-existent pages, tags that are not reciprocal between versions, or tags that confuse language with region.
Titles, descriptions, structured data and image alt texts must be localised in each language version. Not automatically translated on publishing, but written with the correct keywords for the target market. The metadata for each version must be researched separately, with keyword analysis specific to each language and market.
Adapted content, not translated content
The operational difference between a translated website and a localised website manifests itself on every page of the site.
If the company has a sector landing page, the French version of that landing should not be a translation of the Spanish version. It should reference the French regulatory framework, use the vocabulary the French buyer uses in the sector, mention the certifications and documentation relevant to that market and, where appropriate, reference applications or projects in that country. The same applies to every sector and every market: the content must speak the visitor's professional language, not just their linguistic one.
Product datasheets should reference the documentation and standards applicable in each target market. Downloadable documentation should be available in the target market's language where possible, or at least in professional technical English when the original document is in Spanish.
And a blog that exists only in Spanish contributes nothing to ranking in international markets. If the company wants to rank in France for technical searches in its sector, it needs technical content in French that answers the questions the French buyer asks using their vocabulary and references. That does not mean translating every article. It means deciding which content makes sense for each market and producing it with the appropriate level of localisation.
The real cost of a poorly resolved multilingual website
An English or French version that does not rank, does not use the correct vocabulary and does not build confidence in the local buyer is not a neutral version. It is a version that detracts.
A French technical buyer who arrives at the French version of an industrial website and finds imprecise terminology, incomplete regulatory references and a level of detail lower than the original version does not conclude that "the website is being improved". They conclude that the supplier does not have a real presence in their market. And if that is the signal, the buyer does not make contact. They move on to the next supplier that does speak their technical language.
McKinsey has documented in its B2B Pulse Survey that 54% of B2B buyers would abandon a purchase or switch suppliers in the face of a poor digital experience. A deficient language version is, to all intents and purposes, a poor digital experience for the visitor from the target market.
The investment in a real multilingual expansion — with correct technical structure, localised content and SEO by market — is significantly greater than the cost of a literal translation. But a literal translation that does not rank, does not convert and does not build trust has a return of zero. And that zero continues to cost maintenance, server space and the illusion that "the website is already in three languages".
What a real multilingual expansion involves
A well-planned multilingual expansion project includes, at a minimum: analysis of priority target markets, keyword research by language and market — not keyword translation but native research —, independent URL structure per language with localised slugs, correct hreflang implementation with cross-version verification, localised metadata and structured data, market-adapted content with the local regulatory framework, and independently verified indexation for each version.
That turns the multilingual website into a real commercial asset in each market. Not a decorative appendage of the main site.
Conclusion
Having a website in three languages is not having international presence. It is having international presence when each language version ranks in the target market's search engines, uses the technical vocabulary the local buyer recognises, references the regulatory framework applicable in that geography and offers the same level of depth and credibility as the original version.
When the English or French version is a literal translation from Spanish, without local keyword research, without regulatory adaptation, without its own SEO structure and without content designed for that market, the website has languages but does not have markets. And the difference between the two is the difference between taking up space and generating business.
If the company has language versions of its website that are not ranking in target markets or generating international contacts, I can analyse the current situation of each version, identify gaps in structure, content and positioning, and propose a multilingual expansion plan that turns each language into a real commercial channel.
Request multilingual analysis →
