Technical SEO Consultant, Switzerland

Four language versions, one set of templates

Most Swiss company sites run their languages from one system: TYPO3, WordPress with a translation plugin, a headless CMS, or a shop platform such as Shopware, Magento or Shopify. That is efficient for editors, but it means a single template decision affects every version at once, and a fault in one language can sit unnoticed for months.

The patterns worth testing on a multilingual Swiss site include:

• Fallback content. A page missing in French shows the German text under a /fr/ address, creating a duplicate that competes with the original.
• Phantom translations. The CMS publishes empty or half-finished language pages that were never meant to go live.
• Uneven sitemaps. The XML sitemap lists the German pages only, so the other versions rely on internal links to be found.
• Collapsed canonicals. Every language points its canonical tag at the German page, which tells search engines to ignore the rest.

My technical SEO audit starts with a page-type inventory per language, then compares the number of indexable pages, sitemap entries and Search Console data for each folder. Gaps between those counts show where a version is leaking. The method behind it is the same one described on my technical SEO page; what changes in Switzerland is that every check runs three or four times, once per language, before any conclusion is drawn.

Language detection and what crawlers actually receive

Many Swiss sites choose the language on the first visit, using the browser's language setting, the visitor's IP address or a stored cookie. For people this feels convenient. For search engines it can hide whole versions of the site.

Google's documentation explains that its crawler mostly requests pages from addresses in the United States and without a language preference in the request. If the root domain redirects by language or location, the crawler is sent to one default version every time. If the language switch only changes a cookie while the address stays the same, the French or Italian content may never be crawled at all, because there is no separate URL to request.

A crawl-friendly setup for a Swiss site usually means:

• Every language version on its own URL, such as a folder or subdomain, reachable without cookies or scripts.
• A language switcher built from real links to the equivalent page, not to each home page.
• A neutral root page or a clear default with x-default handling, instead of a forced redirect.
• Suggestion banners for visitors who land on the wrong language, which they can dismiss.

I test this with the URL Inspection tool, with crawls that send no language header and, where available, with server logs that show which versions bots really request. The results feed straight into the hreflang and structure work on my international SEO page for Switzerland.

Umlauts, accents and apostrophes in Swiss URLs

German slugs contain ä, ö and ü; French slugs contain é, è, à and ç, plus elided articles such as l' and d'. There are two workable approaches: keep the characters, which browsers display normally while servers transmit them percent-encoded, or transliterate them, so that ä becomes ae and é becomes e. Search engines handle both. What causes trouble is mixing them.

Inconsistency shows up in predictable places:

• The CMS creates one form, the sitemap lists another and the canonical tag uses a third.
• Internal links mix upper and lower case in the percent-encoding, so the same page is reached at two addresses.
• Redirect rules match the transliterated form but not the encoded one.
• Analytics and Search Console split one page into two rows, which makes reporting unreliable.

The fix is a short URL style guide per language, agreed with your developers, that sets the rule for umlauts, accents, apostrophes and capital letters, and a test that the server returns one canonical form. Existing URLs are only changed when the gain justifies a redirect, never as a cosmetic clean-up before a busy season.

Fonts belong in the same review. Web fonts subset to save weight sometimes leave out accented glyphs, so the browser swaps in a fallback font for single letters. That looks careless and can shift the layout while the page loads, which shows up in Core Web Vitals.

Francs, euros and catalogs fed from the ERP

Swiss manufacturers and distributors frequently sell to Swiss customers in francs including Swiss VAT and to EU customers in euros under different terms. When one URL changes its price by cookie or IP address, product markup may report the wrong currency to search engines and merchant listings may disagree with the page. Where prices differ by market, separate URLs per market, each with consistent offer markup, are the cleaner route. Where B2B prices sit behind a login, the markup should describe the product without inventing a public price.

Product data deserves a look at its source. Many Swiss catalogs are generated from an ERP or PIM, with long lists of technical attributes and variants. The risks are specific:

• Variants for each size or voltage producing near-identical pages.
• Discontinued items returning a normal page with nothing on it.
• Filter combinations creating far more URLs than anyone searches for.
• Datasheets available only as PDFs, so the details buyers search for are never on an HTML page.

I review which filter pages should be indexable, how retired products are handled and whether markup matches what each language version shows, following the approach on my schema markup consulting and ecommerce SEO pages. When the feed itself is the problem, the fix sits in the ERP integration, which is where my ERP consulting in Switzerland overlaps with search.

Hosting, consent tools and relaunches with your agency

Many Swiss firms host in Switzerland for data protection reasons or client expectations. That is a business decision, not a ranking factor to rely on; what matters for search is response time, stability and what the server returns. A CDN can keep pages fast for visitors abroad, and staging environments need password protection so test versions never reach the index.

Consent management deserves attention too. A consent tool, a tag manager and several marketing scripts can delay the main content and slow interaction, depending on how they are configured. I measure the effect per template with field data rather than assuming it, then suggest loading changes your developers can test. The consent approach itself is for your legal advisor to set, with Swiss data protection rules in mind and GDPR where EU visitors are concerned; my role is to make the technical setup follow that decision efficiently. The Core Web Vitals consulting page describes the method.

Swiss sites tend to be rebuilt by agencies every few years. Each relaunch needs a redirect map for every language folder, old PDFs and campaign pages, plus checks before and after launch, as set out under SEO migration consulting. Delivery is remote, working alongside your agency rather than replacing it. The wider search picture is on my SEO consultant page for Switzerland, while the Swiss hub page collects the ERP and growth services around it.