LANGUAGE
What the visitor reads
Use a language route when navigation, page content and the next step are available in that language from start to finish.
/de/ · /en/ · /fr/DACH / LANGUAGE / COUNTRY
A DACH website needs an explicit model for language, country, URLs and follow-up. Translation changes language; localization changes the parts of the journey that truly differ.
First distinction
A German-language page can serve more than one country. A country page is justified when the offer, audience, availability, contact route or content is materially different.
LANGUAGE
Use a language route when navigation, page content and the next step are available in that language from start to finish.
/de/ · /en/ · /fr/COUNTRY
Use a country-language route when market-specific content is substantial enough to maintain: for example availability, trust inputs or handoff.
/de-de/ · /de-at/ · /de-ch/URL signals
Every maintained version needs a crawlable URL and a visible route from the interface. Search annotations cannot repair duplicate or incomplete pages.
x-default can identify a neutral selector or fallback.Content model
Not every paragraph needs a country variant. Keep the common foundation shared and split only the inputs that affect relevance or operation.
SHARED FOUNDATION
LOCAL INPUTS
Do not force the route
Do not automatically send visitors to a country or language version based on IP address. It can hide alternate pages from people and crawlers, misread travellers or multilingual users, and remove user choice. Offer a visible selector and remember a deliberate choice only when appropriate.
Country context