Short answer: a multilingual website is useful when a real share of your clients reads another language more easily, not to look international. If you do it, each language must have its own address, properly translated copy and a simple way to switch from one to the other.
The right question: who reads you?
Before talking about translation, look at who writes to you. A lakeside B&B that gets bookings from Germans and Swiss, a festival in the Aosta Valley with a French audience, a gallery that sells to collectors abroad: here a second language brings clients. A practice that only works with clients from its own province, on the other hand, gains more by polishing its main language.
A good clue is the data you already have: email enquiries, reviews, where your website’s visits come from in its statistics. If one language keeps coming up, that is the one to add. If none does, better to wait.
One language done well beats three done halfway
A website translated only in its menus, with the copy left in the original language, disappoints whoever lands on it. Google itself advises against it: translating only the fixed parts of the page while leaving the content in another language creates a confusing experience (Google Search Central).
The same goes for machine translation published without being checked: a native speaker notices from the first sentence, and the careful tone of the rest of the site is lost. Automatic tools are a good starting point; the last word belongs to someone who really speaks the language.
The three technical rules that matter
- One address per language: for example yoursite.it/ in Italian and yoursite.it/en/ in English. Google recommends separate URLs for each language, rather than switching the text with a cookie or according to the browser.
- Pages linked to each other: each version declares the others to Google with the hreflang tag, and must list itself too (Google Search Central). That way, people searching in English find the English page.
- No forced redirects: automatically sending visitors to their browser’s language can stop them, and Google, from seeing the other versions. Better to suggest the language and leave the choice to them.
The language switcher: visible and honest
The way to switch languages belongs where the eye looks for it, at the top, and must lead to the same page in the other language, not to the home page. Write language names in their own language (Italiano, Français, English): someone who does not read Italian will not look for “Inglese”. Flags stand for countries, not languages: someone from Quebec or a Swiss person from Geneva does not identify with the French tricolour.
Before you start, three questions
- Who replies? If a client writes in German, someone must be able to reply in German.
- Who updates? Every new page, price or opening time has to be changed in every language. A foreign-language version stuck two years ago does more harm than none at all.
- What to translate? Not necessarily everything: service pages, contact details and practical information are often enough to start with.
In the websites we build, languages are added with their own addresses, pages linked to each other and a sitemap that declares them all. Our own website is in Italian, French, English and Spanish: if you have an audience that speaks another language, we can decide together which pages to translate first.
Sources
The statements in this guide are based on these sources, consulted in November 2026 (some in Italian).
- Managing multi-regional and multilingual sites — Google Search Central, 2025
- Tell Google about localized versions of your page (hreflang) — Google Search Central, 2025
- Working with multilingual websites («avoid automatic redirections based on the user’s perceived language») — Google Search Central Blog, 2010
- Indicating the language of a link destination («Flags represent countries, not languages») — W3C Internationalization, 2013
- Guiding users to translated pages — W3C Internationalization, 2015