Multilingual Websites Done Right: DE/FR/IT for Switzerland

Anyone in Switzerland who wants to sell beyond their own language region cannot avoid the question: does the website need to speak French? Italian? English? And how do you do it right? Here are the answers, including the mistakes we see most often.

Does your website even need several languages?

The honest counter-question first: do you have customers (or want them) in other language regions? If your clientele is entirely German-speaking, multilingualism is money thrown away, so build out the German version better instead. But if the French-speaking part of Switzerland, Ticino or international customers are part of the market: yes, because people search in their own language, and someone searching in French will not find a German page.

What makes a real language version

Completeness. The most common trap is the token translation: the home page in French, the rest in German, and the contact form in German anyway. That looks worse than no translation at all, it signals “this is how much you matter to us”. Every language offered has to cover the whole journey, right down to the confirmation email.

Translation with judgement. Word-for-word translations give themselves away immediately. It is about the search terms and phrasing of the target market: the customer in French-speaking Switzerland searches differently, not just in another language.

The Google mapping. Google has to know which page belongs to which language, so that searchers see the right version (the invisible signal for this is called hreflang). If it is missing or set wrongly, a very common mistake, your language versions compete against each other or appear to the wrong audience.

One content, one upkeep. Technically the language versions have to be connected: the language switcher leads to the same page in the other language (not to the home page!), and changes must not create duplicate maintenance work.

What often goes wrong, the short list

Half-finished translations (see above), a language switcher that always jumps to the home page, machine-translated text without review including embarrassing technical terms, a missing Google mapping, forms and error messages that stay in German, website-builder limits: many systems can only handle multilingualism as a workaround, a common reason to move.

What it realistically costs

Multilingualism has two cost blocks: the technology (a one-off if set up cleanly, then manageable per language) and the content (translation and upkeep, the part that is often underestimated). Our recommendation: build it multilingual-capable from the start technically, even if you launch with one language, so the later expansion is a fraction of the effort.

Can it be done quickly?

Yes. The association website SFH went live in three languages (DE/FR/IT) in three weeks, and the brand website Al Freihat in two weeks in three languages, including Arabic with a fully mirrored reading direction, which most systems fail at. And plaene-scannen.ch takes orders in four languages.

Whether and how many languages are worth it for you belongs in the honest initial consultation, and the way there is two minutes with the price calculator.