TLD, subdomain or folder: what structure should you choose for your multilingual site?

Does Google really treat these three structures equally?

The official stance is clear: no structure has an intrinsic SEO advantage over the others. Whether you opt for a country code TLD (exemple.fr), a subdomain (fr.exemple.com), or a folder (exemple.com/fr/), the search engine will apply the same ranking criteria.

However, this equivalence relies on a non-negotiable prerequisite: the correct configuration of geotargeting in Search Console. For subdomains and TLDs, you can specify a target country. Folders, on the other hand, require the use of hreflang tags to indicate the intended language and region.

In practice, Google relies on several signals to determine geographical relevance: the targeting declared in Search Console, hreflang signals, the physical address mentioned on the site, local backlinks, and the content language. The URL structure is just one signal among others, not the decisive factor.

Why can this statement be confusing?

Because it oversimplifies the real technical and strategic implications. A national TLD provides an immediate geographic trust signal for users and certain search engines. Subdomains are treated as separate entities by Google, meaning that the authority of the main domain does not automatically transfer.

Folders, conversely, consolidate all authority on a single root domain but share the same crawl budget among all language versions. This pooling can become problematic for large websites where each geographical section contains thousands of pages.

What are the truly relevant decision criteria?

The choice should stem from your operational model and resources. Country code TLDs are suitable for organizations with autonomous local teams and separate marketing budgets per country. They allow for decentralized management and extensive hosting customization.

Folders are ideal when you're looking to maximize the leverage of accumulated authority on a single domain, particularly relevant for startups or companies rapidly expanding internationally. Subdomains occupy an intermediate position, useful for markets requiring strong technical separation without investing in multiple TLDs.

• Theoretical SEO neutrality: Google does not favor any structure if the geotargeting configuration is correct
• Hreflang signal required: essential for folders, recommended for all structures
• Crawl budget: pooled on folders, separate on TLDs and subdomains
• Domain authority: consolidated on folders, fragmented on TLDs and subdomains
• Hosting flexibility: maximal with TLDs, limited with folders

Can this stated equivalence withstand real-world observations?

Partially. Tests show that once the technical configuration is mastered, all three structures can perform comparably. But the real difference lies in execution ease. Folders offer the path of least resistance: one Search Console, one SSL certificate, one technical infrastructure.

Subdomains often pose problems with authority attribution. Contrary to what Mueller's statement suggests, observations indicate that a subdomain often starts with less initial credit than a folder hosted on an established domain. The boost from a strong root domain does not mechanically transfer to subdomains, even if they benefit indirectly from overall trust.

What critical nuances does Google deliberately omit?

Firstly, the issue of crawl budget is never addressed in these official statements. On a site structured with folders having 10 language versions of 50,000 pages each, Googlebot has to arbitrate between the different sections. This constraint does not exist with separate TLDs that each have their own crawl allocation. [To be verified]: Google has never published quantitative data on crawl distribution among language folders.

Secondly, the deployment speed differs radically. Launching a new market in a folder takes a few hours. Setting up a new TLD with its DNS, hosting, SSL certificates, and Search Console takes several days. This operational friction is not neutral for an aggressive international expansion strategy.

Thirdly, local backlinks behave differently depending on the structure. A .fr site naturally attracts more links from French domains than an exemple.com/fr/, even when the content is identical. This acquisition bias is never mentioned in official communications but significantly impacts local ranking.

In what cases does this equivalence rule not fully apply?

Markets with mandatory local extensions for certain sectors escape this neutrality. In China, a .cn significantly facilitates local hosting and speed performance, two indirect but real ranking factors. Russia historically favors .ru in its results, even though Google will never officially admit it.

Sites with radically different content strategies by market benefit more from separate TLDs. If your offer in Germany has nothing to do with your offer in France, pooling authority on a single domain loses its meaning. The technical separation then reflects a business reality, not an artificial SEO optimization.

How can you effectively choose between these three options?

Start by auditing your available technical and human resources. Multiple TLDs require the capability to manage several infrastructures simultaneously, with strong DevOps skills and time to maintain each configuration. If your technical team is small, folders offer unmatched maintenance simplicity.

Next, evaluate your domain authority strategy. Are you launching an international brand with significant link-building budgets for each market? Separate TLDs make sense. Is your strength in an already established root domain that you want to shine internationally? Folders capitalize on this existing advantage.

Question your technical customization needs. Some markets require local hosting for speed or regulatory compliance reasons. TLDs allow for this geographic flexibility. Other markets are perfectly served by a global CDN with language folders, a less costly and quicker solution to deploy.

What configuration mistakes should you absolutely avoid?

The most common mistake concerns the implementation of hreflang tags. Too many sites completely omit them on folder structures, thinking the URL is sufficient to signal the language. Google needs these explicit annotations to understand the relationships between language versions and avoid international duplicate content issues.

Another classic pitfall: mixing structures incoherently. Using subdomains for some countries and folders for others creates an unmanageable management complexity and sends conflicting signals to Google about your organizational logic. Choose a structure and stick to it across all your markets.

Never neglect the geotargeting declaration in Search Console. Generic TLDs (.com, .org) without explicit settings leave Google guessing your intent. Subdomains require a separate Search Console property for each language version, which many forget during the initial deployment.

How to check if your current configuration is optimal?

Analyze the distribution of organic traffic by country in Analytics. If a target market significantly underperforms expectations while the content is solid, your structure or geotargeting configuration is likely problematic. Compare the performances of different language versions with equivalent content volume.

Check the effective indexing of each version via Search Console. Folders on large sites sometimes face partial indexing issues of secondary versions, indicating an insufficient crawl budget. The strategic pages of each language version must appear in the index.

Test the search result behavior from different countries using a VPN. Does your French site prioritize in searches made from France? Does your German version appear in German SERPs? These simple tests quickly reveal geotargeting issues.

• Audit the available technical resources before choosing a structure
• Implement hreflang tags on all language versions without exception
• Configure geotargeting in Search Console for each version
• Maintain structural consistency across all deployed markets
• Regularly monitor the indexing of each language version
• Test geographic performance with VPNs from target countries