Website & Development
Website Translation: Machine, Translator or Hybrid, and What It Does to Your SEO
Copy for AI
Website translation into French does not mean converting your Dutch copy word for word, but rewriting your message so it sounds natural and prompts action for a French-speaking audience. That difference between translation and localization decides whether your French-speaking visitors gain trust and fill in a form, or click away within ten seconds. In this article you will learn why a literal website translation puts off a Belgian French audience, where it goes wrong in tone, examples and CTAs, and how to approach it so your French site truly generates leads. You will also learn which translation method (machine, translator or hybrid) suits which type of page and what a translation does to your findability in Google.
What is the difference between translating and localizing?
Translating converts words from one language into another; localizing adapts the entire message to the culture, context and expectations of the new audience. In a translation, the sentence structure and rhythm of your source language often linger, which makes the text technically correct but unnatural. With localization you rewrite: you choose different examples, a different way of addressing the reader, different arguments and sometimes a different structure, because what convinces a Dutch speaker does not automatically convince a French speaker.
For a B2B website, that distinction is commercially relevant. You are not selling individual words, you are selling trust and clarity. A visitor who senses that a text came “out of a machine” or “out of Dutch” unconsciously doubts the rest of your offer. Localization makes your French-language page read as if it were originally written in French, and that is exactly what is needed to move someone toward an enquiry. The same logic applies, incidentally, to every page that has to build trust on a B2B website.
Why does a literal translation put off French-speaking visitors?
A literal translation stands out for the wrong reasons: it sounds strange, sometimes even rude, and that undermines trust before you have even made your point. Belgian French has its own words and habits that a Dutch-speaking copywriter or an automatic translator does not know by default. French-speaking Belgians use “septante” for seventy and “nonante” for ninety, for example, where the French of France uses “soixante-dix” and “quatre-vingt-dix”. Meal names differ too: in Belgium, “déjeuner” is breakfast and “dîner” is lunch, whereas in France it is not. Small things in themselves, but they immediately signal whether a text was written for “this market” or not.
Then there is tone. French is more formal in business communication than Dutch. Where a Flemish B2B site happily uses the informal address and gets straight to the point, a French-speaking business audience often expects the polite “vous” and a slightly more elaborate, courteous wording. A direct translation of your breezy informal address can therefore come across as abrupt or careless. The message is identical, but the register is off, and register in French is a strong signal of professionalism.
The third problem is recognizability. A text full of references to Flemish situations, Dutch-language terms or examples that only exist north of the language border makes a French-speaking reader feel they are not the intended customer. And someone who does not feel addressed will not convert.
What should you localize beyond the words?
Beyond the text itself, you localize the tone, the examples, the evidence and the calls to action, because these are the elements that drive conversion. A French version that is correct only at the word level but keeps the same Flemish references and CTAs remains a translated site rather than a French-language site.
Think concretely about these layers:
- Tone and address. Deliberately choose “vous” or “tu” and keep it consistent across the whole site. For most B2B contexts in French-speaking Belgium, “vous” is the safer choice.
- Examples and references. Replace Flemish cases, sectors and place names with examples a French-speaking audience recognizes. Show customer stories that are relevant to that market, without inventing anything that does not exist.
- Evidence and figures. Numbers, prices, VAT mentions and date formats must be right for the Belgian context, not carried over automatically from a French or Dutch template.
- Calls to action. A CTA is not a word but a promise. “Request your free quote” does not get stronger through a literal translation, but through wording that sounds equally inviting and clear in French. Which verbs, which urgency and which form of politeness work differs per language. It pays to treat your calls to action as separate copy and not as an afterthought.
Do not forget the forms either. Field labels, error messages, confirmation texts and placeholder text are often the last thing to be translated, even though they sit exactly at the moment of conversion. A French-speaking visitor who sees a Dutch error message drops out. So read through your entire conversion path in forms, not just the running text.
How do you approach a French-language B2B site technically?
Technically, you treat the French version as a full set of pages with their own URLs, their own copy and their own findability, not as a hidden copy behind a language button. The most common approach is a separate URL structure per language, for example with a folder (/fr/) or a subdomain, so that search engines and visitors treat each version as its own page.
To prevent your Dutch-language and French-language pages from competing with each other in the search results, you use hreflang signals to indicate which version is meant for which audience (nl-be and fr-be, exactly the codes Google gives as an example for Belgium). That is a separate and error-prone topic; how it works is explained in our guide to hreflang tags for Belgian B2B. The most important principle: each language version must be findable, readable and convertible on its own.
Just as important is who writes the copy. Good localization is not left to an automatic translation tool alone. Machine translation can produce a first draft, but a native speaker with a feel for B2B and for the Belgian context has to rewrite and proofread the copy. That is not a luxury: it is the difference between a site that generates leads and a site that looks “finished but strange”. Which platform you build on, whether it is Webflow, WordPress or a headless setup, makes no difference to the principle; multilingualism is possible on each of those platforms, each with its own management pros and cons. If you want to weigh that up objectively for your situation, our web design agency helps you make the right choice.
Machine, translator or hybrid: which website translation approach do you choose?
There are three ways to translate a website, and the best choice differs per page type, not per site. Machine translation (with tools such as DeepL, Google Translate or a platform like Weglot) is fast and scalable. A professional translator or copywriter delivers copy that sounds as if it were written in the target language. The hybrid approach combines both: the machine produces a first draft, a native speaker rewrites what matters.
| Machine translation | Translator or copywriter | Hybrid | |
|---|---|---|---|
| Speed | Minutes | Days to weeks | A few days |
| Quality of tone and CTAs | Variable, often sounds translated | Natural, tuned to the market | Natural on the important pages |
| Keywords per language | Translated literally | Only if the translator includes SEO | Researched and applied to key pages |
| What drives the effort | Number of words and languages in the plan | Number of words, jargon, rewriting | Number of pages that get rewritten |
| Risk for SEO | Unreviewed content at scale | Low | Low, provided it is proofread |
| Suited to | Catalogues, knowledge base, documentation | Homepage, services, campaigns | Most B2B sites |
For most Belgian B2B sites, the hybrid approach wins. You do not need to have two hundred blog articles translated by hand, but your homepage, service pages, landing pages and forms deserve a native speaker. If you are considering a translation platform, our Weglot review shows what automatic translation does well and badly. Already running on a translation tool and want your translations in your own CMS? Read how to leave a translation tool without losing SEO or see our translation tool migration.
What does a translation do to your SEO?
A translated page does not rank by itself, and a badly translated page can even be a risk. Google does not penalise machine translation because it is machine translation, but Google’s spam policies explicitly name automatic translation as a technique for creating content at scale that offers little value. A proofread translation that helps the reader does not fall under that; thousands of unreviewed pages might. How Google sees this exactly is covered in our article on AI translation for websites.
For findability, four things count most:
- Keywords per language. French speakers do not search with the literal translation of your Dutch keyword. Research per language what people search for and build your title, URL and H1 around it.
- A separate URL per language. Google recommends separate URLs per language version instead of switching language via cookies, and asks you not to redirect visitors automatically based on their language.
- Translated metadata. Title, meta description, alt texts and the URL slug belong in the language of the page, not in the source language.
- Hreflang. Let Google know which versions belong together. After going live, check it with our free hreflang checker.
When are you better off not starting a French version?
Only start a French-language site if you genuinely serve and can maintain that market, because a half-finished or sloppy translation harms your credibility more than no French version at all. A French-speaking visitor forgives the absence of a French site more readily than a French site full of mistakes, because the latter suggests you do not take their market seriously.
Ask yourself a few honest questions. Do you have French-speaking sales or support to follow up the leads that come in? Can you keep the French content up to date when your Dutch site changes, or will one version soon fall months behind the other? Do you have access to a native speaker who can write and guard the copy? If the answer to those questions is no, you are better off investing your budget first in a stronger single-language site that is fully correct. That fits how we at Customer Impact look at this kind of choice: honest advice, focused on leads and revenue, and realistic about what a website does and does not do for you.
The short summary
Translating a website into French is only effective if you localize rather than translate literally. The difference lies in tone, examples, evidence and calls to action, and in the choice to treat each language version as its own conversion path with the right technology underneath. Literal translation puts off a Belgian French audience because it sounds unnatural and undermines trust; localization wins that trust back. Only take it on if you genuinely serve the market and can keep maintaining the French content. For the broader context of a conversion-focused B2B site, see our guide to having a B2B website built.
Frequently asked questions about website translation
Can I simply translate my website with DeepL or Google Translate?
As a first draft, yes; as the end result, rarely. A machine translation is understandable, but it misses tone, Belgian context and the keywords people use locally. At the very least, have your homepage, service pages and forms rewritten by a native speaker.
What determines the effort of a translation project?
The number of words and languages, how many pages need to be rewritten rather than translated, how technical your jargon is and whether keyword research per language is included. The technical side counts too: separate URLs, hreflang and translated metadata take work in your CMS.
Will I lose rankings if I translate my site?
Not on your existing pages, as long as you do not change their URLs. The new language versions build their own positions. If you do change URLs, for example by adding a language folder, set up 301 redirects following a redirect plan.
Should I translate into French or Dutch for Belgium?
That depends on where your customers are. If you serve all of Belgium, you need both; in that case, also read our guide to a bilingual NL/FR website.
Not sure whether a French-language version makes sense for your business and how best to set it up? See how our website translation services deliver native copy and a correct multilingual SEO setup, or contact us and we will look together at the right approach for your market.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.