Subdomains or Subdirectories for Internationalization: Which Hreflang Architecture Does Google Really Favor?

Why Does Google Favor Subdirectories Over Subdomains?

The statement by John Mueller resolves a fifteen-year-old debate. Historically, Google has always claimed to treat subdomains and subdirectories equally when it comes to indexing. This technical neutrality has never changed.

What changes is the consolidation of signals. With subdirectories, all backlinks, domain age, and accumulated trust benefit the entire site. With subdomains, each instance is treated as a semi-autonomous entity — somewhat like if you were managing several distinct sites under the same umbrella.

How Does This Affect Ranking Signal Attribution in Practice?

Subdomains Fragment Authority. An incoming link to fr.example.com does not directly pass authority to en.example.com or to the root domain. Google may transfer some of this trust, but it is less direct, less automatic.

With subdirectories, each backlink to /fr/ strengthens the main domain, and therefore all other language directories indirectly. This is particularly critical for 3-5 language sites that cannot afford to build a separate link profile for each language version.

What About Analytics and Technical Maintenance?

A frequently underestimated point: operational management. With subdomains, you multiply Search Console properties, Google Analytics profiles, GTM configurations. Each language version becomes a silo.

Subdirectories radically simplify infrastructure: a single GSC property, a single GA4, a single performance tracking. You compare versions in two clicks, not by juggling between ten tabs. For an SEO team already managing three different jobs, this time-saving is not trivial.

• Signal Consolidation: backlinks and trust benefit the entire domain with subdirectories
• Avoided Fragmentation: subdomains create semi-autonomous entities that dilute overall authority
• Operational Simplicity: a single Search Console and Analytics property for all markets
• Simplified Hreflang: fewer risks of inter-domain configuration errors
• Optimized Crawl Budget: Google crawls a unified structure more efficiently than an archipelago of subdomains

Is This Recommendation Consistent With What We Observe in the Field?

Yes, and it is even one of the rare cases where official discourse perfectly aligns with empirical observations. International sites transitioning from subdomains to subdirectories regularly observe an improvement in organic traffic within 3-6 months post-migration — provided the migration is clean.

However, it's not a magical lever. If your content is weak, if you have zero backlinks per market, switching to subdirectories won't create traffic ex nihilo. It optimizes the distribution of what you already have, that’s it.

In What Cases Does This Rule Not Apply?

Mueller explicitly talks about sites with 3-5 languages. As soon as you exceed 10-15 markets with autonomous local teams, distinct brands by country, or legal constraints for geographical separation, subdomains make sense again.

For example: a media group operating different brands by country (LeParisien.fr, DerSpiegel.de) will obviously not merge everything under a global domain. Similarly, some sectors (finance, health) impose regional hosting that makes subdomains unavoidable. [To be verified]: Google states that subdomains remain "possible," but never specifies at what threshold of complexity they become preferable again. This gray area leaves room for interpretation.

Should One Migrate an Existing Site from Subdomains to Subdirectories?

It depends on your opportunity cost. If you already have a mature site on subdomains with well-established link profiles per language version, migrating will require 3-6 months of dev, QA, massive 301 redirects, and post-migration monitoring.

If your site is stagnating or regressing, and your subdomains are struggling, then yes, consider the migration. But if your performance is fine, and you do not have dev resources available in the short term, don't break something that works just to tick a box. Prioritize your content and links first — these levers remain 10x more impactful than an architecture optimization.

What Should You Do for a New Multilingual Site?

If you are launching an international site from scratch, favor subdirectories by default. Configure example.com/fr/, example.com/en/, example.com/de/ from the start. Implement hreflang using HTML annotations (through tags in the ) or via the XML sitemap.

Ensure that each page has its hreflang tags pointing to all equivalent language versions, including a reference to itself. A common mistake is forgetting the x-default declaration to designate the default version when the user doesn't match any target language.

How to Migrate a Site from Subdomains to Subdirectories Without Breaking Everything?

First step: a complete mapping of the existing setup. List all URLs by subdomain, their organic traffic, their positions, their backlinks. Build an exact 301 redirect matrix, page by page, no approximate wildcard.

Set up the new configuration in staging. Test the redirects, hreflang, sitemaps. Once validated, migrate in stages: one market at a time if you want to limit risks, or a big bang if you trust your infrastructure. Monitor Search Console like a radar for at least 8 weeks post-migration — fluctuations are normal, but prolonged drops signal a redirect or canonicalization problem.

What Mistakes Should You Absolutely Avoid in This Architecture?

Mistake #1: Mixing subdomains and subdirectories for different languages. Choose a side and stick to it. Google can manage it, but you unnecessarily complicate your hreflang and fragment your signals.

Mistake #2: Leaving duplicate content without proper hreflang. If /fr/ and /en/ display the same hurriedly translated text by DeepL, Google will cannibalize your rankings. Hreflang does not compensate for poor content; it merely signals a relationship between equivalently quality versions. Mistake #3: Underestimating the operational complexity of a migration. These projects require coordination of dev, SEO, product, and customer support — and often a specialized support to avoid critical technical pitfalls.

• Favor subdirectories (example.com/fr/) for any site of 3-10 languages without specific legal constraints
• Implement hreflang in HTML annotations or XML sitemap, with x-default for the default version
• Create an exact 301 redirect matrix before any migration, tested in staging
• Monitor Search Console for 8 weeks post-migration to detect crawl or indexing anomalies
• Never mix subdomains and subdirectories for different language versions
• Ensure that each page references all of its language alternatives, including itself