Skip to content

Multilingual websites

Multilingual website development, with SEO in every language

Each language gets its own addresses, its own copy and its own search terms, so a buyer in Lyon or Leipzig lands on a page written for them.

Multilingual website development: the English version of business-centrum.be, one of four language versions we built

Your second market searches with other words

Multilingual website development means building one site that reads as a native site in every language it serves: addresses in that language, copy written for that market, the search terms people there actually type, and hreflang links that tell Google which pages are versions of each other. A translated site only swaps the words of the original, and a buyer in another country rarely asks the original's questions.

We build this every week, because our home market forces it: Belgium has three official languages and Brussels is bilingual. The sites we run for clients serve Dutch, French, English, Turkish and German. This page is for a company that sells, or wants to sell, in more than one language: how to structure the site, what changes per language, which market to add next, what a language costs in work, and the mistakes that quietly cost traffic.

One page, four addresses

One pricing page, four addresses

  • nlexample.eu/nl/prijzenNetherlands, Flanders

    Every version tells Google about all four:

    • nl
    • fr
    • de
    • en
    • x-default
  • frexample.eu/fr/tarifsWallonia, Brussels, France

    Every version tells Google about all four:

    • nl
    • fr
    • de
    • en
    • x-default
  • deexample.eu/de/preiseGermany, Austria

    Every version tells Google about all four:

    • nl
    • fr
    • de
    • en
    • x-default
  • enexample.eu/en/pricingEveryone else

    Every version tells Google about all four:

    • nl
    • fr
    • de
    • en
    • x-default

x-default: the version for everyone else

Example addresses. Each language gets its own words in the address, its own copy and its own search terms, not a translation of the Dutch ones.

What a language version needs beyond the translation

PartTranslated siteBuilt per market
Address/fr/services, often with the original slug kepta slug in the language of the page, such as /fr/tarifs
Title and descriptionthe original, translatedwritten on the terms people in that market search
Set of pagesidentical in every languagethe pages that market needs, which can be fewer or more
hreflangmissing, or pointing one way onlyevery version lists itself and all its siblings, plus an x-default
Forms and emailsin the original languagein the visitor's language, down to the confirmation email and the error message
Legal pagestranslatedchecked for the country you sell into, starting with the privacy policy
Reportingone totalimpressions and clicks per language and per country

The row about the set of pages surprises most buyers. On 19 October 2026 the site we run for Business Centrum, a payroll office in Ghent, had 395 addresses in Dutch and 395 in French, but 281 in English and 281 in Turkish: the Belgian markets get every guide and wage table, the expat markets get what expats ask about. A language version is an editorial choice per market, not a copy. How to plan the markets, structure and search terms is in international SEO strategy, the annotations come from our hreflang tag generator, and what an exporter's site needs per market is in website for an export business.

Subfolders, country domains or subdomains

StructureExamplePick it whenThe catch
Subfoldersexample.com/de/one company sells one offer in several languagesnone worth naming; one site to maintain, one authority to build
Country domainsexample.de, example.freach country has its own brand, prices or legal entityevery domain starts from zero in Google
Subdomainsde.example.comone market runs on a separate systemGoogle treats them closer to separate sites
One address, language by browser settingexample.com for everyoneneverGoogle's crawler sees one language only

The last row deserves a warning. Google asks for a separate address per language and advises against switching the language automatically on the visitor's browser or location, because its crawler mostly comes from the United States and would only ever see one version. Show a language switch the visitor chooses, and remember the choice.

The five hreflang mistakes we find on almost every audit

Hreflang can live in the HTML head, in HTTP headers or in the sitemap. Wherever it lives, the same five errors come back:

MistakeEffectFix
No return linkGoogle ignores a pair when A points to B but B not to Aevery version lists all siblings, itself included
Invented codesen-UK instead of en-GB, or be for Belgian Dutchan ISO 639-1 language, optionally an ISO 3166-1 region: nl-BE, fr-BE, de
Pointing at redirects or noindex pagesthe signal is droppedhreflang skips any 301 redirect and points at final addresses
Canonical to another languagethe other version drops out of the indexeach version is a canonical to itself
No x-defaultvisitors from unplanned markets land anywherean x-default to a chooser page or your main language

For a company selling from one site into several European markets, the codes look like this:

VersionhreflangServes
English for the UKen-GBbuyers in the United Kingdom, prices in pounds
English, no countryeneveryone else who reads English
German for Germanyde-DEbuyers in Germany
German for Switzerlandde-CHbuyers in Switzerland, prices in francs
French for Belgiumfr-BEWallonia and French-speaking Brussels
Defaultx-defaultanyone no version above was made for

Add a country only where the version really differs in price, delivery or words. One German version without a country serves Germany, Austria and Switzerland until one of them needs its own.

On our builds hreflang comes out of the content model: a page that exists in two languages links both ways automatically, a page in one language carries none, and a build check stops a broken pair before it goes live. For the definition and the code, see our glossary entry on hreflang; for the full checklist, the SEO checklist; to test a live page, the SEO checker.

Which market to add next

  • Choose the language your visitors already useif analytics shows traffic from a country that leaves fast: they find you but cannot use the page. Start with the pages they land on.
  • Choose the language of your inbound requestsif clients already write or call in it. They want you; give them your services, prices and contact in their words.
  • Choose the empty marketif your competitors have no page in the local language. Build a term map for that market first, the way our guide to keyword research describes, and only write the pages people search for.
  • Choose the language of the lawif you sell to consumers in a country that expects information about the sale in its language: product pages, terms, checkout and emails come first.
  • Waitif nobody on your side can answer a client in that language. A site in German that leads to replies in English loses the trust it just earned.

AI drafts, translators and a native reader

AI translation is good enough for a first draft of most business copy, and we use it that way. Published unread, it misses the words a market searches with, gets product and legal terms wrong and keeps the sentence order of the original. Our routine is a draft written from the term map of that market, a check of product and legal terms by your team, and a native reader before anything goes live. That keeps a language affordable without making it read like a manual.

What each language adds to the price

Three things set the cost of a language: how many pages it gets, who writes the copy, and how much of the site talks back in that language (forms, emails, a portal, invoices). With us, a website starts at 1,500 euros for a one-pager, and a site with many pages, languages, bookings or a shop costs more; each language is a part of the quote with its own fixed price, agreed after a call. The website cost calculator shows how a second or third language moves your site. A language planned from the start costs less than one bolted on later, because menus, addresses and templates make room for it from day one.

Ranking in French is two markets

Ranking in French in Belgium and in France are two jobs, as our article on a website in French and Dutch shows for Belgium. A Belgian employer looks for a "secrétariat social", the French market for "gestion de la paie"; competitors differ, and so do the rules a page talks about. The same holds for German in Germany, Austria and Switzerland, and for English in the UK and Ireland. That is why every language starts from its own term map before we decide which pages it gets, and why an agency that only translates your keywords rarely gets far. Being cited in AI assistants follows the same logic: they answer in the language of the question, so a market without pages in its language is invisible there too, which our page on generative engine optimization covers. If you also sell from Belgium to the rest of Europe, our web development agency in Europe page covers the EU rules a site has to meet.

10,200Google impressions a day, across four languages

Business Centrum went from 220 to 10,200 impressions a day in five weeks, with 1,593 search terms without the brand name on page one of Google. Each of its four languages has its own term map and its own set of pages.

Business CentrumView the case

Turkish for the clients who speak it at home

FK Boekhouding, an accounting firm in Ghent, has clients who prefer Dutch, French, English or Turkish. Each language on their site has its own service and sector pages, written for the questions those clients ask, with its own addresses.

Turkish is not an official language in Belgium, yet it brings in clients a Dutch-only competitor never sees. Pick languages from your clients, not from the map.

The Turkish version of fkboekhouding.be on a desktop, one of the four languages of the site
The Turkish version of fkboekhouding.be on a desktop, one of the four languages of the site

Questions buyers ask before a second language

Do we need every page in every language?

No. A market gets the pages it needs. A page without a sibling simply carries no hreflang to that language, which Google handles fine.

Can you add languages to the site we have now?

Usually, yes. We map the existing addresses, add each language with its own slugs and hreflang, and keep every existing page on its address or redirect it. If the current system cannot hold proper language versions, we say so before quoting.

Who writes the copy in a language you do not speak?

We write Dutch, French and English ourselves and draft other languages from the term map of that market. A native reader checks every language before launch, and your team checks the product terms.

How do we see whether a language works?

Search Console reports impressions, clicks and positions per page; filtered on the language folder and the country, it shows each market apart. We set that up at launch and read it with you after four to six weeks.

Website design

How VBS builds a site that works in each language

We start with your markets, not your menu: which countries, which buyers, which pages each needs. Then a term map per language, one content model that keeps the versions in step, copy written per market and read by a native speaker, and hreflang, sitemaps and Search Console set up per language. Examples: Business Centrum and K&A Law in four languages, Villa Lidia in English and Dutch for guests from across Europe. Read what is in every build on our website design page, and see how we make each language findable through SEO. Then book a call and tell us where you sell.

Selling in more than one language?

Tell us which markets you sell to. We reply with the pages each language needs first.

Optional, if you prefer a call.

What do you want to achieve, and what is already there?

We only use your details to reply to you.