Is it really essential to place your translations in subfolders to rank internationally?

Why does Google favor subfolders over URL parameters?

URL parameters like ?lang=fr or ?country=de pose a fundamental problem: they create dynamic URLs that Googlebot treats with more caution. The engine must guess whether these parameters produce truly distinct content or merely technical variations of the same page.

Subfolders (/fr/, /de/, /uk/) send a clear architectural signal. Each directory becomes an identifiable section of the site, with its own hierarchy, dedicated crawl budget, and geographical relevance signals. Google can analyze content depth by language, measure the authority of each section, and assign pages to regional indexes with greater confidence.

What is the tangible difference for indexing and ranking?

A site structured in subfolders allows Google to isolate ranking signals by language or region. If your French content receives backlinks from .fr sites, that authority concentrates in the /fr/ subfolder and strengthens everything within it. With parameters, this distribution becomes murky, and even inefficient.

Hreflang tags work better when pointing to stable and predictable URLs. Subfolders provide this stability: /fr/product-x and /de/produkt-x are two distinct entities that Google can associate unequivocally. Parameters create variations (product-x?lang=fr, product-x?lang=de®ion=ch) that multiply the risks of mapping errors.

Are subdomains a viable alternative?

Google treats subdomains (fr.site.com, de.site.com) as nearly independent entities. This can be beneficial if you manage separate SEO teams by region or if each language needs distinct technical infrastructure. However, this separation also cuts off the transmission of authority: a backlink to fr.site.com does not benefit de.site.com.

Subfolders keep everything under a single root domain, consolidating the site's overall authority. This is rarely mentioned explicitly by Google, but field observations show that a unified domain distributes internal PageRank better and facilitates future migrations or restructurings.

• Subfolders (/fr/, /de/): better authority consolidation, centralized management, simplified hreflang
• Parameters (?lang=fr): risk of duplication, fragmented crawl budget, blurred geographical signals
• Subdomains (fr.site.com): complete isolation, suitable for decentralized structures but loss of SEO synergy
• ccTLD (.fr, .de): maximum geographical signal but increased management cost and complexity

Is this recommendation truly technically neutral?

Google presents subfolders as a simple architectural preference, but it’s also a question of crawl resources. URL parameters often trigger defensive crawl behaviors: Googlebot limits the number of variants explored to avoid crawler traps. A site with 10 languages in parameters may see only 3-4 versions actually crawled regularly.

With subfolders, each section becomes a distinct branch of the sitemap. You can submit a dedicated sitemap per language, control crawl frequency via Search Console for each directory, and monitor indexing errors granularly. This level of control is impossible with parameters. [To verify]: Google does not publish data on the crawl budget difference between these architectures, but server logs from multilingual sites consistently show deeper and more regular crawls on structures in subfolders.

What exceptions make parameters acceptable?

If your site generates nearly identical content between languages (for example, a translated user interface but with the same product data), parameters may suffice. Google will understand that ?lang=fr and ?lang=de are superficial variations. But as soon as the editorial content diverges, this approach becomes risky.

Sites with millions of pages and complex personalization logic (geolocation + language + currency) sometimes use parameters to avoid an explosion of URLs. In this case, configuring Search Console via "URL Parameters" becomes critical: you need to explicitly indicate to Google which parameters change the content and which are cosmetic. This configuration is fragile and often poorly maintained during technical changes.

What does this statement say about Google's hreflang strategy?

Google does not say it directly, but this recommendation reveals one thing: hreflang tags do not compensate for a poor architecture. Many SEOs think a correctly implemented hreflang is enough to solve multilingual indexing issues. This is false.

Hreflang indicates to Google which pages are linguistic equivalents, but if the underlying architecture is unclear (parameters, dynamic URLs, sessions), the engine does not have enough confidence to apply these annotations. Subfolders create this structural trust: Google sees a coherent /fr/ section, with its own backlinks, its own content, and hreflang pointing to /de/, /es/, etc. The signal becomes redundant and therefore robust. [To verify]: Google does not quantify the impact of architecture on hreflang effectiveness, but field audits show that hreflang errors are 3 to 4 times more frequent on parameter-based sites.

How to migrate from a parameter structure to subfolders?

The migration requires rigorous planning: map each existing URL (?lang=fr) to its subfolder equivalent (/fr/), set up permanent 301 redirects, and submit a newly structured sitemap by language. The main risk is the temporary loss of rankings if redirects are misconfigured or if Google delays in re-indexing the new URLs.

Test the migration on a small section of the site first (for example, the blog or a product category). Monitor Search Console for 404 errors, redirect loops, or orphan pages. Once validated, gradually deploy on other languages, keeping an eye on organic traffic metrics and key positions.

Which tools to use to check the consistency of the multilingual structure?

An SEO crawler like Screaming Frog or Oncrawl should be set up to follow hreflang tags and identify inconsistencies: pages without hreflang, missing backlinks, or annotations pointing to non-existent URLs. Crawling each subfolder separately allows you to measure average depth, the number of orphan pages, and the distribution of internal linking.

Search Console remains the reference tool to check indexing by language. Filter coverage reports by subfolder (/fr/, /de/) to see if Google is successfully indexing all priority pages. If some languages show an abnormally low indexing rate, it is often a sign of crawl budget issues or insufficient content.

Should subfolders and geographic targeting be combined in Search Console?

Yes, absolutely. Once the subfolder structure is deployed, go to Search Console and geographically target each subfolder: /fr/ to France, /de/ to Germany, /uk/ to the United Kingdom. This setup reinforces the signal sent by the architecture and hreflang tags. It's a triple redundancy that maximizes the chances of appearing in the correct regional indexes.

Be careful: geographic targeting only works for subfolders and subdomains, never for URL parameters. This is another reason to avoid this approach for multilingual content. If you have a ccTLD (.fr, .de), targeting is automatic and you do not need to configure manually, but you lose the flexibility to manage multiple regions on the same domain.

• Map all current URLs (?lang=X) to the new structure (/language/)
• Configure permanent 301 redirects tested in staging
• Submit an XML sitemap per language (sitemap-fr.xml, sitemap-de.xml)
• Set up geographic targeting by subfolder in Search Console
• Check the consistency of hreflang tags after migration (no broken links)
• Monitor the evolution of crawl budget by language via server logs for at least 3 months