---
title: "A website in two languages, done properly"
description: "If your customers speak two languages, your site should too. How to plan, write and keep two languages in step without losing your voice."
url: "https://www.litetile.io/blog/a-website-in-two-languages"
lang: "en"
---

A bakery in Brussels serves customers in French and Dutch. A guesthouse in the Alps welcomes guests in German, Italian and English. A physiotherapist in Montreal sees patients in French and English every day. For businesses like these, a website in one language turns away part of the people they already serve.

A second language is more than a copy of the first, though. Done carelessly, it reads like a manual translated by a machine, and it tells customers that one of their languages comes second. Done properly, each version sounds like you speaking to that customer.

## Which languages, which pages

Start with your customers, not with a map. Which languages do they speak when they call, walk in or write to you? Those are the languages your site needs. A language only a few customers use can often wait, especially if they read one of your main languages comfortably.

Then decide which pages each language needs. Usually the answer is all of them, but it does not have to be on day one:

- start with the pages people use to decide and act: home, services, prices and contact;
- add the rest when you have time to write them well;
- keep the same structure in each language, so a visitor who switches lands on the same page in the other language.

A few complete pages in a second language serve visitors better than a whole site half translated, with sentences in one language and buttons in the other.

## Writing, not translating

The best second-language page is written, not translated. Start from the same facts: what you do, where, for whom, at what price and how to get in touch. Then write the page as you would explain it to a customer who speaks that language.

That often means changing more than the words:

- **Tone and politeness.** French, German and Dutch each have a formal and an informal "you". Choose the one your customers expect and keep it throughout.
- **Examples and references.** A local landmark, a holiday or a way of paying that is familiar in one community may mean nothing in the other.
- **Length.** French and German text often runs longer than English. Headlines that fit on one line in English may need two, so keep them short in every language.
- **Formats.** Dates, times, prices and phone numbers are written differently from one country to the next. Write them the way that customer would.

If you are not fluent in the second language, write the facts yourself and ask a fluent speaker who knows your trade to write or check the page. A customer, a colleague or a professional translator who works in your field will catch what a dictionary misses. [Writing website copy that sounds like you](https://www.litetile.io/blog/writing-website-copy-that-sounds-like-you) applies to every language you publish in.

## Menus, buttons and image descriptions

The small lines are the easiest to forget, and a visitor notices them at once. Before you publish a language, go through:

- the menu and the footer;
- every button and link label;
- page titles and descriptions, which appear in search results in that language;
- image descriptions (alt text), which people using screen readers hear in the language of the page;
- your opening hours, address and any notes on holidays.

A page with French text and an English menu tells the visitor that their language was an afterthought. Check each language from top to bottom, on a phone, as a visitor would.

Tip

Ask a customer who speaks the second language to look through the site on their phone and note anything that sounds odd. Five minutes of their time finds more than an hour of your own checking.

## Keeping them in step

The hard part of two languages is not the first version. It is keeping both correct a year later, after prices rise, hours change and services come and go.

A few habits make it manageable:

- **Change facts everywhere at once.** When your hours or prices change, update every language the same day. A wrong price in one language is worse than a slightly older sentence.
- **Keep a short list.** Write down each page and the date each language was last updated. When one falls behind, you see it.
- **Write new pages in pairs.** When you add a page, plan its second version at the same time, even if it goes live a few days later.
- **Review together.** In your monthly check of the site, read the same page in both languages side by side.

## What search engines need

Search engines show each language to the people who search in it, but only if each version can be found on its own. That needs a few things:

- **A separate address for each language**, such as one address for the French page and another for the Dutch one. Switching the language on the same address, by cookie or by detecting the browser, leaves search engines seeing only one version.
- **A note linking the versions.** A small tag in each page, called hreflang, tells search engines that these pages are the same content in different languages, so each searcher is shown the right one.
- **A visible language menu.** Let visitors choose. Sending them automatically to a language based on their browser can trap someone who reads both, and search engines advise against it.
- **Titles and descriptions in each language**, written for the searcher in that language.

[Search basics for small businesses](https://www.litetile.io/blog/search-basics-for-small-businesses) covers the rest of what search engines look for.

## Machine translation: a draft at best

Machine translation is fast and free, and it has its uses: understanding a message from a customer, or getting a first rough version of a page. It is not a finished page.

It gets trade terms wrong, misses the formal or informal tone, keeps sentence shapes that sound foreign and turns idioms into nonsense. It cannot know which details matter to your customers. Google's spam policies have long given text translated by an automated tool without human review as an example of low-value automated content.

Watch out

Never publish a machine translation without a fluent reader checking every line. A customer who meets an odd sentence on your site may wonder what else was done without care.

If you use one, treat the output as a starting point: correct it, rewrite it in your voice and have it read by someone fluent before it goes live.

In litetile, Studio sites can have up to five languages. "Translate to" makes a copy of a page for you to rewrite in the new language, rather than translating it by machine, and each language has its own addresses, menu words and image descriptions, listed for search engines on every publish. [See how languages work](https://www.litetile.io/features/languages).

Related reading: [Writing website copy that sounds like you](https://www.litetile.io/blog/writing-website-copy-that-sounds-like-you) and [Search basics for small businesses](https://www.litetile.io/blog/search-basics-for-small-businesses).
