Multilingual SEO in Switzerland means building your website so that Google shows the right language version — German, French, Italian or English — to the right searcher. It needs three things done properly: a separate, indexable URL for every language, hreflang tags connecting the versions, and keyword research done natively in each language instead of translated. Miss any one of the three and your language versions start quietly competing against each other.

I run a bilingual agency site myself (this article has a German twin), and we build multilingual websites for Swiss SMEs every month at Clear Design. This guide is the checklist we actually use — including the mistakes that cost us rankings before we learned better.

Why Switzerland is a special case

Most “international SEO” guides assume you’re targeting different countries. Switzerland breaks that assumption: one small country, four national languages, plus English as the unofficial fifth for the roughly 40% of Zurich residents with a migration background and the entire international business community.

Those national numbers hide the local reality — in Zurich and Geneva the English share triples. And that has a practical consequence people underestimate. A fiduciary in Biel/Bienne isn’t choosing between markets — the same street searches in two languages. “Treuhänder Biel” and “fiduciaire Bienne” are the same customer intent, different keywords, different SERPs, different competitors. If your site only answers one of them, you’re invisible to half your town.

And no, English alone doesn’t cover you. English works for expats, international firms and tech. For trades, health, law and anything local, German (or French, or Italian) still wins the search volume by a wide margin. The right question is never “which language?” — it’s “which two?”

One domain or many? Get the URL structure right first

This is the decision you can’t cheaply undo later, so it comes first. You have three options, and for almost every Swiss SME the answer is the same one:

Subdirectories, every time. I’ll happily die on this hill: a .ch domain with /de/ and /en/ folders is the setup that wins for Swiss businesses, because your Swiss backlinks — the hardest ones to earn — push both languages up at once. We wrote more about the domain side in our guide to .ch domains and SEO.

hreflang: the tag almost everyone gets wrong

hreflang tells Google which language version to show which user. It sounds trivial. In audits of Swiss SME sites we find it broken more often than working — and a broken hreflang setup is worse than none, because Google starts guessing.

A correct minimal pair looks like this — every version listing every version, plus a default:

<link rel="alternate" hreflang="de-CH" href="https://example.ch/de/" />
<link rel="alternate" hreflang="en" href="https://example.ch/" />
<link rel="alternate" hreflang="x-default" href="https://example.ch/" />

The full specification is short and worth ten minutes: Google’s documentation on localized versions is the only source you need — most blog posts about hreflang paraphrase it badly.

The three errors we see constantly:

• No return tag. The German page points to the English one, but the English page doesn’t point back. Google ignores the whole pair. Every version must reference every other version, including itself.
• Wrong region codes. Use de-CH and fr-CH if you want to be precise about Swiss German and Swiss French — or plain de / fr if you also serve Germany and France. Mixing conventions across pages confuses the mapping.
• Missing x-default. The x-default tag tells Google what to show everyone else — a Spanish speaker in Geneva, say. Point it at your most universal version, usually English.

The honest good news: if you’re on WordPress, you don’t hand-write any of this. Polylang and WPML both generate correct hreflang automatically once languages are connected properly — which is exactly why we insist on connecting every translation pair in the CMS instead of just creating parallel pages and hoping.

Don’t translate keywords. Research them.

This is the single most expensive mistake in Swiss multilingual SEO, and it’s baked into how most agencies quote “translation”.

A real example from our own work: an English page targeting “moving company” translated cleanly into “Umzugsunternehmen”. Except Swiss Germans overwhelmingly search “Zügelfirma” — a word that barely exists in Germany. The correctly translated page ranked for a keyword nobody in Switzerland types.

French Switzerland has the same trap. “Natel” (mobile phone) exists nowhere in France. A “fiduciaire” in Lausanne is a “Treuhänder” in Zug, and neither is the literal dictionary translation of the other’s services. Every language version needs its own five minutes of SERP research: type the candidate keyword into Google, look at what actually ranks, and check whether the results match your customer’s intent. Boring, manual, and worth more than any translation budget.

Machine translation: what Google actually tolerates in 2026

Google’s position hasn’t changed since the helpful content updates: machine-translated text isn’t penalised for being machine-translated — it’s penalised when it’s unedited, unhelpful bulk content. Raw DeepL output pasted into 10 pages is thin content with extra steps.

What works, and what we do for our own bilingual clients: machine translation as the first draft, then a human pass for three things. Keywords (see above — the machine translates, it doesn’t research). Swiss conventions (Swiss German uses “ss”, never “ß”; prices are CHF 1’599, not 1.599 €). And register — Swiss business German is more formal than German German, and French Switzerland notices when your “vous” slips.

One more Swiss-specific note: don’t auto-redirect visitors by browser language or IP. Google’s crawler mostly arrives from the US with English headers; aggressive redirects can hide your German content from it entirely. Show a language switcher, remember the choice, and let people (and bots) reach every version freely.

The technical checklist we run on every bilingual launch

1. Every language has its own indexable URL (no cookies, no JS-swapped text on one URL)
2. Translation pairs connected in Polylang so hreflang + return tags generate correctly
3. Translated slugs — /de/webdesign-preise/, not /de/web-design-prices/
4. Meta titles and descriptions written (not translated) per language
5. Per-language XML sitemaps submitted in Search Console
6. Language switcher visible in the header, linking to the equivalent page, not the homepage
7. Forms, confirmation emails and error messages localised — the enquiry experience is part of SEO’s job
8. Google Business Profile language matches your primary local market

Point 6 sounds cosmetic. It isn’t. A switcher that dumps French visitors on the German homepage is the fastest bounce in Swiss web design, and Google measures what happens after the click. Multilingual SEO overlaps heavily with local SEO in Switzerland here — the language you rank in determines which local pack you appear in.

What it costs, and when a second language pays for itself

The maths is less scary than agencies make it. A second language roughly doubles your addressable search volume in most Swiss regions; done on the setup above, it does so without splitting your domain authority. For a business whose average client is worth four figures, one extra enquiry a quarter covers any sane cost of running the second language. Don’t take my word for it — put your own numbers in:

For transparency, since we publish our prices: our Bilingual plan runs the whole setup in this article — two full language versions, researched keywords, hreflang, localised forms — for CHF 133 a month billed annually, about CHF 50 more than a single-language site. That price only works because we’ve done it dozens of times; if you’re building it yourself or with another agency, budget the keyword research per language, not just the translation, and you’ll avoid the expensive mistake in section four.

Frequently asked questions

Written by Asel Mamytova, founder of Clear Design in Zurich. We design, build and run bilingual WordPress websites for Swiss SMEs — including the one you’re reading. Last updated July 2026.