A multilingual blog in Switzerland needs three things: a clear URL structure with one language directory per language (/de/, /fr/, /it/), hreflang tags with a country code (de-CH, fr-CH, it-CH) so Google can match the versions to each other, and content that fits the relevant language region. Straight translations work for service pages, but for blog posts it usually pays to have a separate topic plan per language. Start with the language in which you have the most customers today.
Switzerland has four national languages, but hardly any SME needs four language versions. The question isn't how many languages your website can handle, but which languages your customers search in. This page shows how to set up a multilingual blog with sound technical foundations, what order makes sense and where translation alone isn't enough.
Answer the market question first, then the technical one
Before you set up a language directory, answer three questions:
- Where do your customers come from today? Check your order list, not the federal government's language statistics.
- Which language do the customers you want to win speak? A hotel in Gstaad has different guests from a plumbing firm in Arbon.
- Can you answer enquiries in that language? A French website with nobody behind it who speaks French creates frustration, not orders.
This determines the order. For most German-speaking Swiss SMEs, that means: German first and complete, French as a second language if French-speaking Switzerland is a genuine market, Italian only where there's concrete demand in Ticino. Bilingual cantons such as Fribourg, Valais and Bern are the exception: there, French is often mandatory from the start.
The URL structure: three options compared
Google documents three common ways of structuring language versions. For Swiss SMEs, the first is almost always the right one.
| Option | Example | Advantage | Disadvantage |
|---|---|---|---|
| Language directory | firma.ch/de/blog/, firma.ch/fr/blog/ | One domain, one set of trust, easy to maintain | Main language also needs its own directory, or must be cleanly defined as the default |
| Subdomain | fr.firma.ch | Separation possible where systems are separate | Google sometimes treats subdomains as separate websites |
| Separate domain | firma.ch and firma-romandie.ch | Full separation of brand and market | Double the effort, trust has to be built up twice |
Blog paths should be consistent within each language: /fr/blog/ with French slugs, not /fr/blog/ with German slugs. A French post under a German-style address looks inconsistent to readers and search engines alike.
hreflang: telling Google which version belongs where
hreflang is a tag in the HTML head or in the sitemap that tells Google which language and country version of a page exists. For Switzerland, the country code matters, because French from Switzerland isn't the same as French from France.
A post with a German and a French version carries these tags in both versions:
<link rel="alternate" hreflang="de-CH" href="https://www.firma.ch/de/blog/waermepumpe-kosten/" />
<link rel="alternate" hreflang="fr-CH" href="https://www.firma.ch/fr/blog/pompe-a-chaleur-prix/" />
<link
rel="alternate"
hreflang="x-default"
href="https://www.firma.ch/de/blog/waermepumpe-kosten/"
/>Three rules that Google states in its documentation and that are most often broken in practice:
- Every version links to all the others, and to itself. Google ignores one-sided links.
- x-default names the version shown to anyone who can't be matched to a specific language, usually the main language.
- Every version has its own canonical tag pointing to itself, not to the main German version.
These terms are explained in more detail in the glossary under hreflang and on the page about the canonical tag. Most systems (WordPress with a multilingual plugin, Wix, Shopify Markets) set hreflang automatically once the language versions are correctly linked to each other. Check it in the source code anyway.
Translate or write separate posts?
This is where most multilingual blogs fail. The technical setup is fine, but the French version brings no visitors. The reason: a translated post answers a question that a German-speaking Swiss person asked.
| Page type | Translation is enough | Own content needed |
|---|---|---|
| Service pages, About us, Contact | Yes, with review by someone who knows the market | No |
| Product descriptions | Mostly | For culturally shaped products |
| Blog posts on technical questions | Partly, when the question is framed the same way in both regions | When search terms, authorities or habits differ |
| Regional posts | No | Always: different places, different providers, different questions |
Example: a property manager in Biel writes about «checking service charge statements» in German. The French version isn't simply «vérifier le décompte des charges», it has to match the terms actually searched for in French-speaking Switzerland and take into account the cantonal particularities in tenancy law in the canton of Bern. No translation without market knowledge can achieve that.
The practical approach for SMEs: have service pages translated, but run a separate, smaller topic plan per language for the blog. Ten good French posts achieve more than fifty translated ones. You can find out how such a plan is built under Editorial plan for the company blog.
Duplicate content: not a problem if hreflang is correct
Many business owners worry that a French translation will count as a duplicate. Google is clear on this: translated content in different languages is not duplicate content. It only becomes an issue when the same language appears under several addresses, for example de-CH and de-DE with identical text. hreflang helps in that case, but Google may still only pick one version. More on this on the page about duplicate content.
What can be automated and what can't
The technical side can be automated: language directories, hreflang, sitemaps per language, linking the versions together. Machine translation delivers usable rough drafts for service pages.
Market knowledge can't be automated: which questions are asked in French-speaking Switzerland, which terms are common there, which authorities and laws apply there. A blog system that delivers German posts doesn't automatically cover French-speaking Switzerland too. Before signing a contract, clarify which languages a provider writes in and whether French posts are created as original texts or as translations. For the full picture of Swiss particularities, it's worth looking at the page SEO in Switzerland.
What to do with this
- Set the order of languages based on your actual customers, not on the map of Switzerland.
- Use language directories on your existing domain.
- Set hreflang with a country code and check it in the source code.
- Have service pages translated, but plan blog topics independently per language.
- Make sure enquiries can be answered in every language you offer.
A second language is an investment spanning years. Better to do one language fully than three half heartedly.
Frequently asked questions
Is it enough to have the German blog automatically translated into French?
It's better than nothing as a start, but usually not enough for rankings in French-speaking Switzerland. Translated posts answer questions asked by German-speaking Swiss, not the questions people in Lausanne or Fribourg ask. On top of that, technical terms are often translated incorrectly by machines. Have translations checked by at least one person who knows the market.
Do I need a separate domain for each language?
No. A language directory on your existing .ch domain is the simplest and usually the best solution for SMEs. All languages benefit from the trust the domain has already built up. Separate domains per language are only worthwhile for separate brands or very large websites.
What happens if I leave out hreflang?
Google will then assign the language versions itself, which often works but not always. A typical problem: someone searching from Geneva is shown the German page even though a French one exists. hreflang takes this decision off Google's hands and, in most systems, takes only a few minutes to set up.
Can a blog system supply several languages at the same time?
This depends on the provider and should be clarified before signing a contract. Some systems only write in one language, others translate, and a few plan topics independently per language region. Ask specifically whether French and Italian posts are created as original content or as translations of the German text.