Choose a stable URL model
Give every published language page a unique crawlable URL. Subdirectories such as /de/ and /fr/ are straightforward to explain and manage for many Swiss businesses. Keep slugs and routing rules predictable, and decide what happens when an equivalent page does not exist.
Each page should identify itself as canonical. Do not canonicalize localized pages to English, because that tells search engines the localized URLs are duplicates to ignore. Make language switching a normal link so users and crawlers can reach every version without scripts or form controls.
- One indexable URL per language version
- Self-referencing canonical on each page
- Direct links between equivalent pages
- Intentional fallback for missing translations
Check the alternate-language map
Every equivalent page lists all published variants, including itself, using the correct language or language-region code. The references must be reciprocal: if English points to German, German points back to English. An x-default can indicate the general entry page when that choice is meaningful.
Generate tags from a single route map rather than editing them page by page. Then test the built HTML, not only a CMS preview. Confirm that alternate URLs return successful responses, use the expected canonical and are not blocked from indexing.
- Self and reciprocal hreflang references
- Valid language codes and absolute URLs
- Matching page intent across variants
- No redirects, errors or noindex targets
Test the whole localized journey
Open each version on desktop and mobile. Switch language from a service page and a legal page, preserving the equivalent route, query parameters and useful fragment. Check menus, breadcrumbs, forms, validation, consent links, confirmation states and downloadable material.
Finally, include localized URLs in XML sitemaps and review analytics attribution. Crawl for broken internal links and accidental English fallbacks. Record who will repeat these checks when pages are added or removed; hreflang quality declines quickly when route maps and content inventories drift apart.
- Equivalent-path language switching
- Localized forms and legal routes
- Sitemap and analytics coverage
- Repeatable post-launch audit
Frequently asked questions
Frequently asked questions
Does hreflang improve rankings?
It is a targeting signal that helps search engines show the appropriate equivalent page. It does not make weak content competitive or guarantee visibility.
Should every page include all four languages?
Only list versions that genuinely exist and serve the same intent. Do not point to a homepage as the alternate for every untranslated detail page.
Are translated slugs required?
No. Clear localized slugs can help people, but technical consistency and stable routing matter more. Agree the model before launch and avoid changing URLs without redirects.