A multilingual website: one site, three languages, without three times the work

What is a multilingual website, and who needs one?

A multilingual website is one site with the same pages in several languages, so each customer reads your business in their own.

Say a small family business sells olive oil in Spain, Italy and Britain. A buyer in Milan lands on the site. If it is in Spanish only, she leaves. If it greets her in Italian, in words an Italian would use, she stays and reads on.

You need one when customers, suppliers or partners use more than one language. A hotel with guests from three countries needs one. A local bakery serving one town may not.

Picture a dentist near a border. Half of the patients speak one language and half another. A site in both lets the receptionist stop repeating the same answers on the phone.

It is not about showing off. It is about making it easy to say yes.

What makes a multilingual website feel native?

A multilingual website feels native when each language is written for its readers, not translated word for word from another.

Think of a restaurant menu. A literal translation of a regional dish name comes out as nonsense. A native writer explains it in a few words that make the guest hungry. The same applies to a delivery promise, a return policy or a joke on the About page.

Three things make the difference. Here they are:

• Each language is written by someone who thinks in it.
• Names, units and dates follow local habits.
• The tone fits the market: some readers like warm, some like formal.
• The facts match in every language, so nothing contradicts.
• Buttons, forms and small texts are translated too, not just the main pages.

How do you keep one design across languages?

You keep one design by building the site once and filling the same layout with each language's words.

Imagine three separate sites made at different times. The Italian one has a new header, the Spanish one still has the old one, and the English one has a different font. A visitor who switches language feels like they walked into a different shop.

A single design avoids that. Text lengths differ between languages, and the layout has to cope. German words are long. Some languages need more space for a button. The site is checked on a phone in every language, so nothing breaks.

That is how we build today: one design, the same in every language, checked on mobile. It runs for clients now.

How do search engines and AI assistants handle several languages?

They need to be told which page is for which language, and each page needs its own clear title and answer in that language.

A customer in Spain searches in Spanish. If your Spanish page has a proper Spanish title and a plain Spanish answer near the top, it can be found and quoted. If the Spanish page is a copy of the English one with a few words swapped, it is passed over.

So each language gets its own main phrase, a title and description in its own words, a plain answer at the start of each section and a place in the sitemap. Search Console is set up so you can see how each language performs.

We do all of this as part of building multi-language sites. Nobody can promise a ranking, but each language page is set up properly.

Here is the order of work.

1. Decide which languages your customers really use.
2. Write the pages in each language, from the facts, not word for word.
3. Build one design and check it on a phone in each language.
4. Give each page its own title, description and main phrase.
5. Add the sitemap and set up Search Console.
6. Agree who updates what, and when.

How do you keep the languages in step when things change?

You keep them in step by changing the facts once and updating every language in the same round.

A small hotel changes breakfast time. If only the English page is updated, a guest from Rome shows up at the wrong hour. The most common failure of a multilingual site is not bad translation. It is one language going out of date.

So agree one owner for each change, and update all languages together. Keep one master list of the facts that change: prices, hours, products, policies. When one changes, every language changes in that round.

A useful habit is a simple log. Every time you change something on the main page, write one line: what and when. At the end of the week, that log is the to-do list for the other languages.

This is the heavy part, and it grows with each page and each language. The calculator below shows the work one round of changes can take, using your own numbers.

Where do you start?

Start with your most important pages in two languages, then add more once they feel right.

A small manufacturer might begin with the home page, one page per product group and a contact page, in English and one more language. Once those read well, it adds the third language, then the blog.

Do not translate everything on day one. Translate what customers need to decide: who you are, what you sell and how to reach you.

Nothing about this has to be rushed. A neat two-language site that grows beats a sprawling five-language site that nobody can keep current.

We write, build and update multi-language websites for clients, with the search side set up. You read every page before it goes live.

Questions