Subdomain vs Subdirectory for Multilingual Websites: Which Is Better for SEO?

If you're translating your website into multiple languages, one of the first decisions you'll face is how to structure your URLs. Should French visitors land on fr.example.com (a subdomain) or example.com/fr/ (a subdirectory)? The answer has real consequences for your search rankings, your maintenance workload, and your budget. The short version: subdirectories win for the vast majority of businesses. Here's why — backed by data, expert consensus, and Google's own documentation.

You've probably seen conflicting advice on this. Google says both approaches work. SEO tools give different answers depending on who you ask. And some enterprise sites use subdomains successfully, which muddies the picture further.

The confusion exists because the answer is nuanced — but only at the extremes. For small and mid-size businesses launching their first multilingual site, the evidence strongly favors one approach. This guide breaks down exactly what you need to know to make a confident decision.

First, Let's Clarify the Three Options

Before diving into the SEO data, here's what we're actually comparing. There are three ways to structure a multilingual website's URLs:

Each approach tells search engines and visitors where to find translated content. But each one comes with very different trade-offs in terms of SEO performance, technical complexity, and cost.

How Google Actually Treats Subdomains vs Subdirectories

Let's start with what Google itself says. Google's official documentation lists subdomains, subdirectories, and ccTLDs as equally valid options for multilingual sites. John Mueller, Google's Search Advocate, has stated multiple times that "Google web search is fine with using either subdomains or subdirectories." Former head of webspam Matt Cutts has called them "roughly equivalent."

So Google doesn't officially prefer one over the other. Case closed? Not quite.

The practical reality beneath this official neutrality is more revealing. When you use a subdomain, Google Search Console requires you to verify it as a separate property. Each subdomain gets its own crawl budget, its own robots.txt, its own sitemap, and its own error reporting. Google's crawler treats fr.example.com and example.com as distinct entities that it needs to learn are related.

Subdirectories? Everything at example.com/fr/ is automatically recognized as part of example.com. One Search Console property. One sitemap. One crawl budget. Mueller himself has acknowledged this distinction, noting that keeping content on the same server under one domain helps Google crawl it more efficiently.

The official stance is neutrality. The technical implementation suggests subdirectories have a structural advantage right out of the gate.

The Domain Authority Question (This Is Where It Gets Important)

Here's where the choice really matters for your rankings.

Subdirectories Consolidate Your SEO Power

When someone links to a page at example.com/fr/pricing, that backlink strengthens the authority of your entire domain — example.com and every page underneath it. Your French content directly benefits from backlinks earned by your English content, and vice versa. All your SEO efforts compound under one roof.

When someone links to fr.example.com/pricing, that authority primarily benefits the subdomain. It doesn't automatically flow back to example.com with the same force. Your SEO efforts are split across separate entities that each need to build credibility independently.

This isn't just theory. Backlinko's analysis of 11.8 million Google search results found that subdirectories consistently outperform subdomains in organic rankings, particularly for competitive keywords. And SE Ranking's study of 20,000 keywords confirmed the pattern — sites using subdirectories generally achieve stronger positions than those using subdomains for equivalent content.

The Moz Migration Story

One of the most cited examples in this debate comes from Moz itself. When they moved their Beginner's Guide to SEO from guides.moz.com (a subdomain) to moz.com/beginners-guide-to-seo (a subdirectory), rankings improved immediately — they outranked Google's own content for the term "SEO guide."

The reverse direction has also been tested. When G2.com moved blog content onto a subdomain at learn.g2.com, it took months to rebuild trust in the new location — despite G2 having a Domain Rating of 88 and over 750,000 monthly visitors.

What SEO Tools Actually Measure

Here's a detail many people miss: major SEO tools like Ahrefs' Domain Rating and Moz's Domain Authority treat subdomains as separate entities. A backlink pointing to blog.example.com does not register as a backlink to example.com in these tools. This means your authority metrics are fragmented across subdomains — making it harder to demonstrate domain strength to potential link partners, journalists, and anyone evaluating your site's credibility.

The counterargument, made by Patrick Stox of Ahrefs, is that many migration case studies had confounding variables — sites often improved content and fixed technical issues simultaneously. This is fair. But the weight of practitioner evidence still tilts firmly toward subdirectories for most businesses.

Hreflang Tags: Same Syntax, Different Difficulty

Regardless of which URL structure you choose, you need hreflang tags to tell search engines which language version of a page to show to which audience. The hreflang syntax is identical for both approaches — a <link rel="alternate" hreflang="fr" href="..."/> tag on each page pointing to all its language variants.

The difference is how hard it is to get them right.

Subdirectories Make Hreflang Implementation Simpler

With subdirectories, a single CMS or translation tool generates all hreflang tags from one system. When you add a new language or change a URL, the tags update automatically across your entire site.

With subdomains, each language version may run on a separate installation, managed by different teams or different configurations. Every time you add or change a page on one subdomain, you need to coordinate hreflang updates across all other subdomains. If the French team updates a URL but the German team doesn't update their corresponding hreflang tag, Google ignores both annotations.

Hreflang Errors Are Extremely Common

This coordination challenge matters because hreflang tags are notoriously difficult to implement correctly. Mueller has called hreflang "one of the most complex aspects of SEO." Studies from 2026 suggest that roughly 75% of international sites have hreflang errors.

The most common failure is the missing return link — Page A declares Page B as its French version, but Page B doesn't point back to Page A. Google ignores both annotations when this happens. Other frequent mistakes include using incorrect language codes, pointing hreflang tags to non-indexable pages (404s, redirected URLs, or noindexed pages), and conflicts between hreflang and canonical tags.

Every one of these errors is easier to prevent and detect when all your languages live under one domain in subdirectories.

Technical Setup: The Complexity Gap Is Huge

For non-technical founders, this section might be the most important one. The difference in setup and ongoing maintenance between subdirectories and subdomains is not marginal — it's dramatic.

Subdirectories: Almost Nothing to Configure

Subdirectories require zero DNS changes. They're simply paths within your existing website, handled by your CMS or translation tool. Your existing SSL certificate covers all subdirectories automatically. One hosting account, one deployment, one backup strategy.

If you're using a tool like Verbi, translated content is served through subdirectories by default — you set up your DNS once, and every language you add gets its own clean subdirectory path (like /fr/, /de/, /es/) without any additional configuration.

Subdomains: A Multiplication of Everything

Subdomains require a DNS record for each language (individual A/CNAME records or a wildcard), web server configuration to route traffic to each subdomain, and SSL certificate planning. A standard SSL certificate only covers one domain — you'll need either a wildcard certificate (covering *.example.com) or individual certificates per subdomain.

The ongoing maintenance burden is where things really diverge:

Every row in that table where subdirectories show "one" and subdomains show "multiple" represents ongoing time, cost, and risk.

What Major Platforms Default To (They've Already Decided)

The website builder and CMS ecosystem has largely voted on this question, and the verdict is nearly unanimous.

Webflow uses subdirectories exclusively for its native Localization feature. Translated content automatically gets clean subdirectory paths, hreflang tags are generated automatically, and CMS content inherits across locales — all managed from the visual Designer.

Shopify Markets supports subfolders, subdomains, and top-level domains, but explicitly recommends subfolders as the default and creates them automatically when you publish a new locale.

Wix defaults to subdirectories and warns that language query parameters (like ?lang=fr) are bad for SEO.

WordPress supports both through its Multisite feature, but the choice is made at installation and is effectively permanent. WordPress VIP, the enterprise tier, defaults to subdirectories. Translation plugins like WPML and TranslatePress use subdirectories as their primary mode with zero additional configuration required.

Among translation tools, Weglot supports both structures but labels subdirectories as "Recommended" in its dashboard.

The one notable gap is Squarespace, which lacks native multilingual support entirely — teams on Squarespace need third-party tools for translation.

The pattern is clear: every major platform either defaults to or explicitly recommends subdirectories for multilingual websites.

What About ccTLDs? (The Third Option)

Country-code top-level domains like example.fr or example.de deserve a mention because they're the strongest geo-targeting signal Google recognizes. A .de domain is automatically associated with Germany in search results — no Search Console configuration needed.

The data backs this up. A 2024 study analyzing 20,000 keywords across 15 markets found that over half of Google's top-ranking positions globally are held by ccTLDs. European users are reportedly three times more likely to click a result on their local ccTLD, and 82% of French internet users prefer companies using .fr domains.

But ccTLDs come with significant trade-offs:

• Each domain starts from zero authority. You need a separate backlink strategy for every country domain.
• Each domain needs its own hosting, CMS, SSL, and SEO management. The operational surface area multiplies with every domain you add.
• Registration costs add up. Some ccTLDs impose residency requirements (.no, .ie, .jp), and you'll want to register your brand defensively across relevant extensions.
• Brand protection gets expensive. Every unregistered ccTLD is a potential cybersquatting risk.

Amazon, IKEA, and BBC use ccTLDs — but they have country-level teams and enterprise budgets to sustain them. For most small and mid-size businesses, ccTLDs are a "maybe someday" option, not a starting point.

Five Mistakes That Hurt Multilingual SEO (Regardless of URL Structure)

Getting the URL structure right is step one. Here are the most common mistakes that undermine multilingual SEO performance no matter which approach you choose:

1. Auto-Redirecting Based on IP or Browser Language

This is explicitly warned against in Google's documentation. Googlebot typically crawls from the US, so automatic redirects prevent it from discovering your non-English content. Use suggestion banners instead — "This page is also available in French" — and let users choose. Verbi supports this through configurable language detection that follows best practices.

2. Translating Keywords Literally

A word-for-word translation of your English keywords almost never matches how people actually search in another language. "Cheap flights" in English might be best translated as the equivalent of "affordable flights" or "flight deals" in German. Always conduct local keyword research for each target language.

3. Forgetting to Translate Metadata

Title tags, meta descriptions, image alt text, and URL slugs all need to be in the target language. Leaving them in English signals to search engines that the page isn't truly localized. A good multilingual SEO setup handles this automatically.

4. Mixing URL Structures Across Markets

Some businesses put French on a subdomain, German in a subdirectory, and Spanish on a ccTLD. This creates inconsistent signals, complicates hreflang management, and makes maintenance exponentially harder. Pick one approach and stick with it.

5. Pointing Hreflang Tags to Broken Pages

Hreflang tags that point to 404 pages, redirected URLs, or noindexed pages cause Google to ignore the annotation for that entire page cluster. Audit your hreflang tags regularly, especially after URL changes or content removals.

Our Recommendation: Start With Subdirectories

The consensus across SEO research, expert opinion, and platform design is clear. For the vast majority of businesses going multilingual, subdirectories are the right choice.

Here's how to think about it based on your situation:

If You're a Startup or Small Business

Use subdirectories. No hesitation. They're the cheapest to implement, the simplest to maintain, and they deliver the fastest SEO results because they leverage your existing domain authority from day one. A translation tool like Verbi handles subdirectory creation, hreflang tags, and SEO optimization automatically. Focus your energy on translating the pages that matter most — the 20% that drive 80% of your traffic and revenue.

If You're a Growing Mid-Size Company

Stick with subdirectories as your default. The only reason to consider subdomains is if specific markets require different hosting infrastructure, payment systems, or compliance environments that genuinely can't share a server with your main site. That's a narrow set of cases.

If You're an Enterprise

Consider a hybrid: ccTLDs for your top three to five proven markets where you have local teams, with subdirectories on your main .com for everything else. Migrate a market to its own ccTLD only when it generates enough revenue and has enough dedicated staff to justify the operational overhead.

The Emerging Case for Going Multilingual Now

Regardless of which URL structure you choose, the case for translating your website has never been stronger. AI-powered search is increasingly surfacing translated content in Google's AI Overviews, with some reports showing up to 327% more visibility for websites with multilingual content in non-English queries.

The structure matters far less than the decision to start. Subdirectories give you the simplest, most cost-effective path to get there — and you can always add complexity later when the data justifies it.

Ready to make your website multilingual? Get started with Verbi — we handle URL structure, hreflang tags, and multilingual SEO so you can focus on reaching new markets.

Frequently Asked Questions

Is a subdomain or subdirectory better for multilingual SEO?

Subdirectories are better for the vast majority of multilingual websites. They consolidate domain authority under a single domain, simplify hreflang implementation, and require far less technical setup and maintenance. While Google officially states both structures are valid, independent studies consistently show subdirectories outperforming subdomains in organic rankings — particularly for sites that haven't yet built strong backlink profiles for each language version.

Does Google treat subdomains as separate websites?

Technically, Google treats subdomains as separate properties in Search Console, assigns them independent crawl budgets, and requires separate sitemaps and robots.txt files. Google can recognize that subdomains belong to the same organization, but this recognition depends on strong internal linking. For practical purposes, you should assume each subdomain needs to build authority somewhat independently.

What is the best URL structure for a multilingual website?

For most businesses, subdirectories (like example.com/fr/) are the best choice. They consolidate SEO authority, require minimal technical setup, and are the default recommendation of every major website platform including Shopify, Webflow, Wix, and WordPress. Country-code top-level domains (like example.fr) deliver the strongest local trust signals but require enterprise-level budgets. Subdomains occupy a narrow middle ground for organizations that need technical infrastructure separation.

How do I implement hreflang tags with subdirectories?

With subdirectories, hreflang implementation is straightforward. Each page includes <link rel="alternate" hreflang="x" href="..."/> tags pointing to every language version of that page, including a self-referencing tag. Most translation tools — including Verbi — generate these tags automatically when you use subdirectories. The key requirement is that every hreflang annotation must be reciprocal: if your English page points to the French version, the French page must point back to the English version.

Should I use ccTLDs instead of subdirectories for international SEO?

Only if you have the budget and local teams to support them. ccTLDs provide the strongest geo-targeting signal to search engines and build more trust with local users. However, each ccTLD starts from zero domain authority, requires separate hosting and SEO management, and multiplies your operational costs. Most businesses should start with subdirectories and consider ccTLDs only for their highest-performing markets once they have dedicated country-level resources.

Can I switch from subdomains to subdirectories later?

Yes, but migration requires careful planning. You'll need to set up 301 redirects from every subdomain URL to its corresponding subdirectory URL, update all hreflang annotations, resubmit sitemaps, and monitor Search Console for crawl errors. There will typically be a temporary ranking fluctuation during the transition. The effort is worthwhile — most sites that make this move report improved rankings within a few months — but it's better to start with subdirectories from the beginning if possible.

Do I need separate Google Search Console properties for each language?

With subdirectories, no — all languages are part of one domain property. With subdomains, yes — each subdomain must be verified and monitored as a separate property. With ccTLDs, each domain is its own property. This is one of the key maintenance advantages of subdirectories: one dashboard to monitor your entire multilingual site's health, indexing status, and search performance.