Website & Development
Building a Bilingual Website (NL/FR) for the Belgian Market
Copy for AI
A bilingual website for Belgium starts with a commercial question, not with technology.
Are you truly serving a French-speaking market, or does a second language mainly add work and maintenance?
The verdict: build the French version only when French belongs to your sales plan. Then use subdirectories, fixed URLs per language, and translate what converts first.
Only after that “yes” do the choices about URL structure, default language and translation scope start to matter.
This guide covers those strategic decisions, separate from the pure code.
The goal: one site that generates leads in two languages, not two half sites that get in each other’s way.
When do you really need a French version?
When French-speaking Belgium or France is a deliberate part of your target audience and sales plan.
Not because “it’s expected in Belgium”.
That distinction decides whether a second language becomes an investment or a ball and chain.
Belgium’s language map
Belgium has 4 language regions:
- Flanders: Dutch-speaking
- Wallonia: French-speaking
- A small German-speaking community in the east
- Brussels: bilingual, Dutch and French equivalent
For commercial communication, freedom of language use largely applies.
You may in principle address your customers in the language that suits your market.
As an ordinary B2B company, you usually have no legal obligation to be bilingual.
The question is purely commercial. For example, a Ghent installer whose clients all sit in Flanders doesn’t need French. A Brussels IT firm with clients in Wallonia probably does.
Three questions before you start
Ask yourself 3 questions:
- Is there concrete demand from Wallonia or Brussels, or do you only suspect it?
- Can your team follow up French-speaking leads in French, from quote to invoice?
- Does the extra revenue outweigh the permanent maintenance of a second version?
Three times “yes”? Then French is justified.
If you’re in doubt, a tidy single-language site that converts is almost always better than two half sites.
Our experience: localisation goes beyond language.
Buyers prefer local companies, a local address and local partners, so plan those signals too.
Where to start when you do enter that market is covered in entering the French-speaking market with your website.
First a site that converts? See our guide on B2B website development.
Which URL structure do you choose for a bilingual site?
Subdirectories, for most Belgian B2B companies: example.be/nl/ and example.be/fr/ on the same domain.
You keep all your authority on one domain.
Management stays simple, and the structure is crystal clear for search engines.
Here are the 3 options side by side:
Subdirectories (example.be/nl/, example.be/fr/)
Simple, all SEO value stays on one domain, and it’s cheap to maintain.
Google lists them as “easy to set up” and “low maintenance (same host)”.
For virtually every Belgian B2B site, this is the default choice.
Subdomains (nl.example.be, fr.example.be)
Sometimes handy if the two versions are managed by separate teams or systems.
Google lists them as easy to set up.
But users can’t always tell whether “fr” means a language or a country.
In practice, you end up maintaining two separate properties.
Separate country domains (example.be and example.fr)
Only worthwhile if you truly serve different countries with their own entities, for example Belgium and France separately.
It’s the most expensive to manage and builds authority per domain.
Google notes a country domain “can only target a single country”.
Match slugs to the language
For a Belgian company serving NL and FR within Belgium, subdirectories are the smartest choice in nine out of ten cases.
Watch out: let the URL slugs match the language of the content. So /nl/diensten/ and /fr/services/, not /fr/diensten/.
That consistency helps visitors and search engines, and fits a clean website architecture for SEO.
The wider picture: our multilingual website strategy.
How do you choose which language is the default?
Pick the language of your largest or most important market. When in doubt, the language in which most leads come in.
For a typical Flemish company that’s Dutch.
For a company centred in Brussels or Wallonia it can be French.
Don’t redirect automatically
A common mistake is redirecting based on browser language or the visitor’s IP address.
That feels clever, but it often backfires.
For example, a French-speaking buyer in Brussels with an English browser opens your Dutch page on purpose. An automatic redirect sends them somewhere they didn’t ask for.
Google explicitly advises against automatic redirects between language versions. Googlebot usually crawls from the US without an Accept-Language header and may never see some versions.
Use a clear language switcher
Put each language version on a fixed, findable URL.
Let the visitor choose with a clear switcher in the navigation.
Three rules for that switcher:
- Visible: place it prominently, usually top right
- Native names: “Nederlands”, “Français”, not “Dutch”, “French”
- Same page: the choice lands on the translated page, not the homepage
Here’s how that switcher works on our own site:
Tell search engines with hreflang
For search engines, you also indicate which version is the fallback for visitors without a clear language preference.
You arrange that technically with hreflang, including an x-default. Google’s localized versions guide says “each language version must list itself as well as all other language versions”.
If two pages don’t point to each other, Google ignores the tags.
The details are in the article on hreflang tags for Belgium.
Common slips are in fixing hreflang errors. Here’s what a clean result looks like:
Should you translate everything or only what converts?
Only what converts, to start. Expand once the second language proves itself.
A full translation upfront is expensive.
It’s often largely wasted while the French-speaking market still has to be proven.
A pragmatic order for a first French version
Translate in 3 layers:
- Core pages: homepage, key service pages and contact
- Proof and trust: about page, references or cases
- Deeper content: blog and knowledge base, once layer 1 pays off
Layer 1 is the minimum with which a French-speaking lead can take you seriously and get in touch.
Layer 2 matters because trust is often the bottleneck in B2B.
Watch out: Google warns that translating “only the boilerplate text” while the bulk stays in one language can “create a bad user experience”. Translate whole pages, not just menus and buttons.
Localise, don’t just translate
A good French version is localised: amounts, VAT logic, examples and references that are right for that market.
Our explainer on website translation vs localization shows the difference page by page.
Get the keyword right per language
Translation tools often pick the wrong search term, so the page doesn’t rank.
Our experience: for a Belgian software client, a translation plugin turned “time registration” into “tijdsregistratie”. Belgian searchers type “tijdregistratie”, without the s.
So check the local search term for every key page. Our guide to local keyword research explains how.
Machine translation, then a human pass
Machine translation can speed up a first version.
But don’t publish it uncorrected on pages meant to make money.
A form or call to action that sounds just slightly off costs you conversions.
Our experience: we do all translations in-house.
AI translation plus local search-term data gets you most of the way. A human pass follows only where it’s really needed.
More in our piece on AI translation for your website.
Rule of thumb: better three strong French pages than thirty mediocre ones.
Where do bilingual B2B sites get stuck in practice?
In maintenance: a second language version is a permanent commitment, not a one-off project.
Every new service, price change or campaign now has to be applied twice.
Otherwise one version falls behind.
Half-finished translations
A Dutch button or error message in the middle of a French page undermines your credibility more than a correct single-language site.
A translation tool rarely solves that. To manage your translations in your own CMS, read how to leave a translation tool without losing SEO, or compare Weglot alternatives.
Our experience: we once sent translation corrections to many Belgian companies. Many were happy to receive them.
Orphaned versions
The French site is no longer updated after launch and slowly drifts out of sync.
Tip: add “update FR” as a fixed step to every content change, with one owner.
Lost positions during a migration
Converting a single-language site to bilingual often changes your URL structure.
Without clean redirects you lose rankings.
Plan that carefully, as described in website migration without losing rankings. Our translation tool migration team handles the move off plugins.
Accessibility rules
Since 28 June 2025, the European Accessibility Act applies to certain products and to services provided to consumers, including e-commerce services.
Purely B2B services fall outside it.
Microenterprises (fewer than 10 staff and no more than 2 million euros turnover) are exempt for services.
But as soon as you also sell to consumers online, it can come into play.
Have this assessed case by case, and build in accessibility anyway: it makes your site more usable for everyone.
Whether your Belgian site falls under it is covered in the European Accessibility Act for Belgian websites.
The mistakes to avoid are in web accessibility mistakes.
Frequently asked questions
Is a bilingual website legally required in Belgium?
For an ordinary B2B company, usually not. Freedom of language use largely applies to commercial communication, so the choice is commercial.
Should I use subdirectories or subdomains for NL and FR?
Subdirectories for most Belgian B2B sites. They keep authority on one domain and are easy to maintain. Subdomains only make sense with separate teams or systems.
Can I redirect visitors to their language automatically?
Better not. Google advises against automatic redirects by language, because visitors and Googlebot may never reach the other version. Use a language switcher instead.
Do I need to translate my blog straight away?
No. Start with the homepage, key service pages and contact, then proof pages.
Translate the blog once the French version brings in leads.
The short summary
A bilingual website for Belgium is first a strategic choice, then a technical one.
Confirm that a French-speaking market belongs to your sales plan. Then choose subdirectories on one domain, put each language on a fixed URL with a clear switcher, and translate what converts first.
Maintenance is the real cost: a tidy single-language site always beats two neglected half sites.
Want this worked out platform-neutrally and conversion-focused for your case?
See our approach to website development and website translation services. We’ll tell you whether French is worth it before we build it.
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.