Subdomain or Subdirectory: Which URL Structure Should You Choose for a Multilingual Site?

Why Does Google Allow All URL Structures for Multilingual Sites?

Google's position is clear: URL structure is not a ranking factor in itself. Whether you choose example.com/fr/, fr.example.com, or example.com?lang=fr, the search engine will index and rank your content equivalently, as long as each URL serves only one language.

This technical neutrality is explained by the evolution of Googlebot’s ability to interpret contextual signals: hreflang tags, declared language in HTML, and the content itself. The choice of structure is therefore more about internal technical constraints — server architecture, CMS, deployment capabilities — than a strict SEO imperative.

What’s the Difference Between a Multilingual Site and a Multi-Country Site?

Mueller makes a fundamental distinction that many still confuse. A multilingual site offers several languages without specific geographical targeting — for example, a B2B SaaS in English, French, and German without territorial preference.

A multi-country site, on the other hand, targets distinct national markets with differentiated content, offers, or business strategies. In this case, Google requires a structure that allows geo-targeting via Search Console: subdomains (fr.example.com), subdirectories (example.com/fr/), or separate domains (example.fr). URL parameters are excluded for multi-country — they do not allow for configuring geographical targeting.

What Does “One Language per URL” Really Mean?

Google Rejects Mixed URLs where multiple languages coexist on the same page — think of those sites with a JavaScript language selector that modifies the DOM without changing the URL. Each language version must have its own canonical, stable, and independently accessible URL.

This rule directly impacts the implementation of hreflang: it is impossible to declare language alternatives if the URL remains identical. URL segmentation ensures that Googlebot can crawl, index, and serve the correct version according to the user’s query language.

• Accepted Structures for Pure Multilingual: subdomains, subdirectories, parameters, separate domains
• Accepted Structures for Multi-Country: only subdomains, subdirectories, and separate domains (no parameters)
• Absolute Obligation: a single language per URL, no mixed content
• Mandatory Configuration for Multi-Country: geo-targeting in Search Console by property or subsection
• Additional Signal Required: properly implemented hreflang tags for all structures

Does This Statement Align with Observed Practices on the Ground?

Yes, but with a significant nuance: not all structures are equal in terms of operational SEO effectiveness. Google is correct when it claims that no structure is favored algorithmically — but it omits the practical consequences of each choice.

Subdomains fragment domain authority and multiply Search Console properties, complicating management. URL parameters pose crawling budget and duplication issues if poorly configured. Subdirectories concentrate authority on a single domain but complicate technical management when multiple teams manage different countries. Google's neutrality does not mean your choice is consequence-free.

What Are the Grey Areas of This Statement?

Mueller does not clarify Google’s behavior regarding inconsistencies between URL structure, hreflang, and geo-targeting. What happens if a subdirectory /fr/ targets Belgium via Search Console but uses hreflang to fr-FR? [To be verified] — field reports show indexing inconsistencies in these hybrid configurations.

Another point: Google does not address sites with regional variants of the same language (French France vs French Canada, English US vs UK). The recommendation of one language per URL holds true, but how does Google arbitrate between /fr-fr/ and /fr-ca/ without explicit geo-targeting? Observations suggest that content and localization signals (server, local backlinks) take precedence — but no official confirmation.

In What Cases Is This Rule Not Sufficient?

Complex markets with multiple languages per country expose the limits of Google’s doctrine. Take Switzerland: French, German, Italian, Romansh. Should you create example.com/ch-fr/, example.com/ch-de/, etc., or example.com/fr/ with geo-targeting for Switzerland? Both approaches are technically valid, but the implications for crawl budget, content duplication, and hreflang consistency diverge radically.

Google also recommends configuring geo-targeting “by property or subsection” in Search Console — but the actual granularity of this parameter remains unclear. Can a subdirectory target multiple countries simultaneously? Not according to the interface, only one country per subsection. This forces the duplication of /fr/ into /fr-fr/, /fr-be/, /fr-ch/ for fine targeting — with the risks of cannibalization that this implies.

How to Choose the Appropriate URL Structure for Your Context?

For a multilingual site without strict geographical targeting, favor subdirectories (example.com/fr/, /de/, /es/). They concentrate domain authority, simplify Search Console management, and facilitate technical deployment on a single server or CDN. The only case where subdomains are justified is when technical infrastructures are segmented by market, teams are autonomous by language, or CMS constraints impose this segmentation.

For a multi-country site with distinct business strategies, there are three viable options: separate domains (example.fr, example.de) if you have the resources to manage multiple properties and if local identity is critical; subdomains (fr.example.com) if you want decentralized management but a unified back office; subdirectories (example.com/fr/, /de/) if you seek maximum authority concentration and accept centralized technical complexity.

What Critical Mistakes to Avoid During Implementation?

Never use URL parameters for multi-country — Google does not allow geo-targeting configuration on example.com?country=fr. This structure remains acceptable for pure multilingual, but it raises crawling budget, duplication, and social sharing issues. Avoid it unless there’s a major technical constraint.

Another frequent mistake: forgetting to configure geo-targeting in Search Console after choosing subdomains or subdirectories. Without this step, Google tries to guess targeting via server IP, ccTLD, content — often resulting in inconsistent outcomes. Also validate that your hreflang are bidirectional and include all variants, including x-default for users outside the target.

How to Audit the Compliance of Your Current Structure?

First, check that each URL serves only one language — inspect the HTML source, not just the visual rendering. Language selectors in JavaScript that modify the DOM without changing the URL violate this rule. Crawl your site with Screaming Frog or Oncrawl while analyzing lang and hreflang attributes to detect inconsistencies.

Then, check the Search Console configuration: for a multi-country site, each subdomain or subdirectory must have its explicit geographical targeting. Compare this configuration with your hreflang declarations — any divergence generates contradictory signals for Google. Finally, test visibility in SERPs from different countries via VPN or tools like Valentin.app to validate that Google serves the correct version according to geolocation.

• Audit the current structure: a unique language per URL, no mixed content
• Validate hreflang tags: bidirectional, complete, including x-default
• Configure geo-targeting in Search Console for each multi-country property/subsection
• Avoid URL parameters for geographical targeting
• Document the logic of choice (subdomain vs subdirectory vs domain) according to business constraints
• Test the display in international SERPs to confirm correct targeting