Back to the blog

Business·7 min read

Multilingual website for exporters: domains and translation

Country domain or /fr/ folder, machine or checked translation, which language first: how to set up your website for export and what to ask.

Before you translate
A .fr domain or a /fr/ folder?
Who checks the translation?
Its own URLs per language?
Who answers in French?
In this article

To sell in another country, your website needs a real version in that language: every page with its own address, translated and checked by someone who knows your product, and someone at your company who can reply in that language. If you already have a .com, folders (/fr/, /de/) are almost always enough; a domain per country pays off when that market runs on its own.

A distributor turns up in France, or you come back from a trade fair with contacts in Germany, and someone says the website should be in French. Behind it sit three decisions (which languages, which domain, how to translate) and one question almost nobody asks in time: who will keep each language up to date a year from now.

Do I need my website in the language of the country I want to sell to?

If you want to be found by people who don't know you yet, yes. Google recommends a different URL for each language version and advises against switching the language with cookies or browser settings. Without a page in French, you have nothing to show someone searching in French.

Google sometimes translates the title and snippet of a result into the searcher's language, and whoever clicks sees your page machine-translated, as with Chrome's translator. Your sizes and terms, in French nobody at your company has read. If you only sell to three importers who already read you in English, English is enough for now.

Which language should I translate first?

The market where you already sell or get asked, not the country that sounds best in the meeting. That's our judgement, based on four things you already have:

  1. Where your orders and distributors are today.
  2. Where enquiries come from: forms, emails, trade fairs.
  3. What Google sees. Search Console's performance report can be filtered by country, and since October 2026 it lets you tick several at once. If you already get impressions in France with your Spanish site, someone there is looking for you.
  4. Who replies. A German website brings emails in German, and if nobody answers them well, it works against you.

And a language isn't a country: the French version works in France, Belgium or Switzerland. Fabrice Canel, from Bing, advised in 2020 against duplicating URLs just to tag them by language and market, because links and clicks get split. Separate copies per country only if prices or the catalogue change.

A country domain (.fr) or folders (/fr/)?

With one team and a .com, folders: one site, one admin panel and all your search visibility in one place. A country domain makes sense when that market runs on its own (a subsidiary, a distributor with its own catalogue or prices) or when you already own that domain and it has years of history (our judgement). Pros and cons, according to Google's guide to multi-regional sites:

OptionExampleForAgainst
Country domainyourbrand.frClearly says which country it targets; server location doesn't matterMore expensive; covers one country only; some registries have requirements
Subdomainfr.yourbrand.comEasy to set up; can be split offFrom the address, you can't tell if "fr" is a language or a country
Folderyourbrand.com/fr/Easy to set up and maintainDoesn't say which country it targets; harder to split off later
Parameteryourbrand.com?lang=frNoneGoogle doesn't recommend it

Two things before you choose. Search Console no longer lets you tell Google which country your site targets: that setting was retired, and Google keeps using hreflang. And Bing, according to its webmaster blog, looks at each page's content-language tag (or the lang attribute), the server header and the country domain. A .fr already says "France"; a /fr/ folder has to say it on every page.

Boix PLV, which makes point-of-sale displays and sells in more than 25 countries, has its website in four languages with a domain for each: boixplv.es, .cat, .com and .fr. Moving the domains over from the old site was part of the job, and Mar Farran's review mentions it: "Nos han gestionado la migración de dominios y el diseño de nuestra nueva web de forma ágil y profesional" (they handled the domain migration and the design of our new website quickly and professionally). It's in the Boix case study, with no figures, because none have been published.

Machine translation, AI or a translator?

For anything that sells (product pages, sizes, terms), AI writes the draft and someone who speaks the language and knows your sector checks it. In its spam policies, Google lists translating among the automated transformations used to generate many pages that add little value. It doesn't ban machine translation: it looks at what the page offers.

How it's translatedWhat happensWhat we'd use it for (our judgement)
A translator widget on top of the siteWithout addresses per language, Google has no French page to showNothing that sells
Machine or AI, uncheckedFast, but gets technical terms and finish names wrongDrafts
AI with a glossary and review by someone in the sectorFast and controlled; needs a regular reviewerProduct pages, catalogue, range pages
Professional translatorSlower; every change goes back through themTerms of sale, warranties, legal texts

Before you translate a single product page, build a glossary: your materials, finishes and product types, with the word your distributors use over there.

What should be translated first, and what can wait?

First, whatever the buyer needs to ask you for a quote: the product pages for the range you'll sell there, the spec sheet, the form and your terms (lead times, shipping, minimum order). News and company history can wait.

The opposite doesn't work: the menu in French and the product pages in Spanish. Google warns that translating only the boilerplate while keeping the bulk of the content in one language makes for a worse experience.

How much does each language cost to maintain?

Every language multiplies every change: a new product page, a price or a corrected size has to be done once per language, and checked.

  • Yearly cost of one language = changes per year × hours to translate and check each change × cost of that hour + whatever you pay outside for translation

Do the maths before you open a third language, and ask for the admin panel to flag when the French version falls behind. Otherwise, six months later each language says something different, just like the PDF catalogue used to.

What to ask before hiring a multilingual website

This applies to us and anyone who quotes you. Next to each question, the answer you'd want to hear.

  1. Does each language have its own addresses, product pages included? Yes, every page in every language with its own URL.
  2. Will you redirect based on browser language or country? No. Google asks you not to redirect automatically between languages or adapt content by IP: a visible link to switch language.
  3. Does each page link to its other versions? Yes, with hreflang and in both directions: if the French page doesn't link back to the Spanish one, Google ignores those tags.
  4. Who translates, who checks and with what glossary? A name for each job.
  5. What happens when I change a product page in Spanish? The panel marks which languages are pending.
  6. What happens to the old addresses if my current site already ranks? They're redirected one by one.
  7. How much will adding a language cost a year from now, and whose name are the domains in? The price, in writing now; the domains, yours.

How do I know if the new language version works?

Before publishing, note your impressions and enquiries from that country and check again three months later: Search Console filtered by country, Bing Webmaster Tools and your inbox. If the form records the page's language, you'll know which enquiries the new version brought in. If there are no impressions and no enquiries, the problem isn't the translation: that market isn't looking for you, or it's looking with other words.

How much does it cost with us?

A corporate website with a catalogue starts at €4,500 excluding VAT, in the languages you need, each with its own addresses and no automatic translator on top (manufacturers). It all starts with a 1 to 2 week assessment, which sets the final price and each phase's timeline in writing, and you pay by phase. For AI assistants to read each language properly, see the AEO guide.

Frequently asked questions

Is a .fr domain or a /fr/ folder better for selling in France?

With a .com and a single team, the folder: it's easier to maintain and keeps everything together. The .fr pays off if that market runs on its own or you already own the domain with some history.

Can I translate my website with ChatGPT or another AI?

As a draft, yes. Before you publish, have it checked by someone who speaks the language and knows your sector, using a glossary of your terms.

Doesn't Google translate my website by itself?

It can translate your result's title and snippet, and whoever clicks sees your page machine-translated, unchecked and without its own French addresses.

Which language should I start with?

The one for the market where you already sell or where people already write to you from, as long as someone on your team can reply in it. If in doubt, English.


Do the maths for each language and run the seven questions past anyone who quotes you, us included. If it still adds up, write to us and we'll look at it with your catalogue and your markets in front of us.

Topics

multilingual website · export · manufacturers · international SEO · translation · B2B

Share

Fast Web Academy

One emailwhen there's something to tell.

What we test in the lab and what works for clients. Written in Spanish. No spam.