Discussion
  • International SEO
  • Site Architecture

Countries with several official languages, like Switzerland, Belgium or Canada: which URL structure has served you best?

Published 1 reply

Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The structure that has served best in multilingual countries is one country site, on a ccTLD or a country subfolder of a global domain, with a subfolder per language: example.ch/de/, example.ch/fr/ and example.ch/it/, or example.be/nl/ and example.be/fr/, or example.ca/en/ and example.ca/fr/. Each language version gets its own hreflang annotation with the country code, such as de-CH, fr-CH, nl-BE or fr-CA. Users choose their language through a clear selector, not an automatic redirect. The harder decisions are about languages shared with neighbouring countries: whether Swiss French pages need to differ from French pages for France, and how to stop Google folding near-identical versions together.

    Why language subfolders within a country work

    • One domain, one set of signals for the country: links, reputation and local relevance are shared across languages.
    • Clear targeting. A ccTLD is a strong country signal, and language folders make the language explicit.
    • Simple hreflang clusters. Each language version annotates the others and any equivalent pages in other countries.
    • Manageable operations. One platform and one set of country-level settings for prices, shipping and legal terms.

    Structures compared

    Structure Example Assessment
    ccTLD with language folders example.ch/fr/ Strong country signal; usually the best choice where a ccTLD is available
    Global domain with country-language folders example.com/ch-fr/ Consolidates authority on one domain; country signal comes from hreflang, content and local signals
    Separate domains per language example-fr.ch Splits signals; rarely justified unless brands differ
    Language parameters ?lang=fr Harder to manage and more error-prone; avoid
    One URL, language by browser settings Automatic switching Crawlers may see only one language; avoid

    Shared languages across borders

    French is spoken in France, Belgium, Switzerland and Canada; German in Germany, Austria and Switzerland; Dutch in the Netherlands and Belgium. If a Swiss French page is identical to the French page for France apart from the country flag, Google may treat them as duplicates and choose one as canonical. Google representatives have said that when language versions are the same, one is often chosen as canonical, although hreflang may still swap the URL shown in results; reporting will then be on the canonical URL. Genuine local differences reduce this: currency, prices, shipping and returns, legal information, contact details, local terminology and local examples. Where the business offers the same thing in both countries, accept that Google may cluster the pages and rely on hreflang to show the right version.

    Legal and practical language requirements

    In some places language is also a legal matter. In Quebec, French-language requirements apply to commercial websites serving Quebec consumers, and they were strengthened in recent years. Belgian and Swiss businesses often have expectations about which languages are offered by region. These requirements usually determine which languages a site must have; the URL structure then follows from that decision.

    Choosing the default for the country root

    In a country with several official languages, the root URL, such as example.ch/, needs a deliberate treatment. Common options are a language selector page marked as x-default, or a redirect to the language most visitors use with the other languages one click away. A selector page is the more neutral choice and works well with hreflang; a redirect to a default language is simpler but should never be based on IP or browser settings for crawlers, and users should be able to switch easily. Whichever you choose, make sure internal links, sitemaps and the main navigation point to language-specific URLs rather than the root, so each language version accumulates its own signals.

    Implementation checklist

    • Reciprocal hreflang annotations with country codes for every language version, including a self-reference.
    • An x-default for a language selector page, if the country root has no single default language.
    • A visible language selector on every page, linking to the equivalent page in each language, not to the language homepage.
    • No automatic redirects based on IP or browser language; Google advises against redirecting users based on perceived language.
    • Localised titles, descriptions, navigation and URL slugs where you localise slugs.
    • Structured data in the page’s language, with country-specific prices and currencies.

    Hypothetical example:

    A retailer serves Switzerland from example.com/de-ch/ using German content copied from its German site, with no French or Italian versions. Swiss French speakers land on German pages or the site for France, with euro prices. It launches example.ch with /de/, /fr/ and /it/, Swiss franc pricing, Swiss delivery information and a language selector, with hreflang connecting the Swiss versions to each other and to the German, French and Italian country sites. Search Console shows French-speaking Swiss searches now landing on /fr/ pages, and conversion in Romandy improves because prices and delivery match the market.

    Watch for this:

    Partially translated sites, where navigation is translated but product descriptions stay in one language, confuse both users and language detection. Launch a language only when the pages that matter are fully translated, and keep untranslated sections out of that language’s hreflang cluster.

    Use one country site with language subfolders, connect every version with hreflang, let users choose their language, and give each shared-language version genuine local differences so it is not folded into a neighbour’s.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.