The advice you’ll hear most often is that using subdomains for languages “splits your authority” and quietly kills your SEO, so you should always use subdirectories instead. That’s a half-truth dressed up as a law. Google’s own engineers have said for years that they treat subdomains and subdirectories largely the same for ranking — the real difference is not a hard-coded penalty, it’s how reliably link equity and quality signals flow across the boundary, and how much operational overhead each structure costs you. Get past the myth and the decision becomes a practical one about your infrastructure, your team, and how many markets you actually serve.
What “Subdomains for Languages” Actually Means
A subdomain sits in front of your root domain: de.example.com for German, fr.example.com for French, es.example.com for Spanish. Each one is technically a distinct host that can point to a separate server, run on a different CMS, and be managed by a different team — which is exactly why large organizations reach for them. Contrast that with subdirectories (example.com/de/, example.com/fr/), which live inside one host, and ccTLDs (example.de, example.fr), which are entirely separate domains. Using subdomains for languages is the middle option on that spectrum: more separation than a folder, less than a country-code domain.
The Myth That Subdomains Kill Your Rankings
The claim that subdomains are treated as “separate websites” and therefore start authority from zero is the single most repeated piece of misinformation in international SEO. Google crawls and consolidates signals across subdomains of the same root domain routinely — think of how maps.google.com and news.google.com coexist. What’s true is subtler: signals cross the subdomain boundary less automatically than they do inside a single host. A strong internal link from your homepage to /de/ passes context obviously; the same link to de.example.com works, but historically some site owners have seen subdirectory migrations outperform subdomain ones. The honest read is that subdirectories tend to consolidate signals with less friction, not that subdomains are penalized. If your language subdomains are well-linked, well-structured, and correctly tagged, they rank.
Subdomain vs Subdirectory vs ccTLD: The Real Trade-Offs
There is no universally correct answer here — there’s a correct answer for your resources and market count. Here’s how the three structures genuinely compare:
- ccTLD (
example.de): the strongest geo-targeting signal, automatic and unambiguous, and trusted by local users. The cost is real — you’re building authority on a fresh domain per country, you pay for and manage each registration, and link equity is fully fragmented. Best when you have serious per-market budget and want maximum local trust. - Subdirectory (
example.com/de/): consolidates all authority on one domain, is the cheapest and easiest to launch, and is the pragmatic winner for most sites. The downside is you can’t easily host different language sites on different servers or split them across teams. - Subdomain (
de.example.com): the middle ground. You get infrastructural separation — separate hosting, separate stacks, easier delegation to regional teams — while staying under one root domain. The trade-off is slightly weaker signal consolidation and more configuration to keep hreflang and analytics coherent across hosts.
Notice that “splits authority” is a genuine concern for ccTLDs and a mild one for subdomains — not the deal-breaker it’s made out to be.
When Language Subdomains Are Genuinely the Right Call
Reach for subdomains for languages when the separation is a feature, not a bug. If your German and French sites run on different platforms, are maintained by autonomous regional teams, or need to be hosted in-region for latency or legal reasons, subdomains let each operate independently without spinning up separate domains. Large media companies and multi-brand enterprises often land here for exactly these operational reasons. If you’re a lean team serving three or four languages off one CMS, a subdirectory is almost always the lower-friction choice — don’t take on subdomain overhead for a benefit you won’t use.
Hreflang Is Non-Negotiable — And Easy to Break Across Subdomains
Whatever structure you choose, hreflang is what tells Google which language version to serve to which user. It is not optional the moment you have more than one language, and subdomains make it slightly easier to get wrong because the annotations point across hosts. The rules that trip people up:
- Reciprocity. Every version must reference every other version, including itself, and each referenced page must point back. If
de.example.comlistsfr.example.comas an alternate, the French page must list the German one in return. One-directional hreflang is silently ignored. - Correct codes. Use ISO 639-1 for language (
en,de,fr) and, only when you need to distinguish regions, add an ISO 3166-1 Alpha-2 country code (en-gb,es-mx,pt-br). The classic error is inventing codes: it’sen-gb, neveren-uk, and you never put a country code where only a language belongs. - An x-default. Include an
x-defaultentry pointing to your language-selector or fallback page for users whose language you don’t target. - Pick one delivery method. Implement hreflang via HTML
<link>tags, an HTTP header, or the XML sitemap — one of them, not all three at once, which only creates conflicting signals.
Because subdomain setups multiply the number of cross-references, they’re where reciprocity breaks quietly. This is exactly the class of error a real-crawler site audit catches — SEO Rocket’s audit fetches your pages the way a search engine does and flags missing return references, malformed language codes, and duplicate content across language versions before they cost you visibility.
Geotargeting: Language Is Not the Same as Country
A subdomain for a language (say, Spanish) and a subdomain for a country (Mexico) are different jobs, and conflating them causes real damage. Spanish is spoken across two dozen countries; es.example.com shouldn’t be geo-locked to Spain. If you genuinely need country-level targeting, that’s what region-qualified hreflang (es-mx, es-es) is for. Note that Google retired the country-targeting setting in Search Console back in 2022, so you can no longer geo-assign a subdomain in the old International Targeting report. Geotargeting today relies on hreflang annotations, ccTLDs where you use them, server location, and local signals like in-country backlinks and a local business address — not a toggle in a dashboard.
Don’t Auto-Redirect by IP or Browser Language
The tempting move on a multi-subdomain setup is to sniff a visitor’s IP or Accept-Language header and bounce them to the “right” subdomain automatically. Resist it. Googlebot crawls predominantly from US IP addresses, so IP-based redirection can trap the crawler on your English subdomain and prevent it from ever discovering and indexing your German or Japanese versions — the ones you built the whole structure to rank. The safer pattern is a suggestion, not a forced redirect: detect the likely language and surface a dismissible banner (“View this site in Deutsch?”) while letting the user — and the crawler — stay on the URL they requested. User choice keeps every language version crawlable.
Migrating to Subdomains Without Losing Rankings
If you’re moving from a single-language site or from subdirectories to subdomains for languages, treat it as a structural migration, because that’s what it is. Map every old URL to its new subdomain equivalent and put 301 redirects in place one-to-one — never bulk-redirect an entire language to a single homepage. Keep the content identical through the move so you’re only changing the address, not the page. Update internal links to point at the final subdomain URLs rather than chaining through redirects, submit fresh XML sitemaps per subdomain, and expect a few weeks to a couple of months of ranking turbulence while Google re-consolidates signals against the new hosts. Watch each market separately during the settling period — a portfolio-level average will hide a single language that’s dropped.
A Technical Checklist for Subdomain International SEO
Before and after you launch language subdomains, verify the fundamentals that make subdomain international SEO hold together:
- Reciprocal, correctly-coded hreflang across every subdomain, plus an
x-default. - One hreflang delivery method, consistently applied.
- Self-referencing canonical tags on each version, pointing at that version’s own URL — not at the English original (a canonical to the English page tells Google to drop the translated one entirely).
- A distinct, submitted XML sitemap per subdomain, and each subdomain verified in Search Console so you get per-language coverage and performance data.
- No forced IP/language redirects; a dismissible language-suggestion banner instead.
- Genuine localization, not just machine translation — currency, examples, and idiom that read as native, since thin translated pages get treated as low-value.
The keyword work underneath this matters just as much as the plumbing. Search demand differs by market — the term with volume in Spain may be near-zero in Mexico — so research keywords per country against real data rather than translating your English list. SEO Rocket pulls Ahrefs keyword data with a per-market country selector for exactly this, and its rank tracking follows positions across countries so you can see each language subdomain’s performance on its own, not blended into a misleading global number. It’s an SEO layer, not a translation service — you still need a real localizer for the words — but it’s the layer that tells you which words are worth localizing.
Frequently Asked Questions
Do subdomains for languages hurt SEO compared to subdirectories?
Not through any penalty. Google treats subdomains and subdirectories largely the same for ranking. In practice subdirectories consolidate link equity and quality signals with a little less friction, which is why they’re the default recommendation for most sites. Subdomains rank perfectly well when they’re strongly internally linked, correctly tagged with hreflang, and genuinely localized — the choice should come down to your infrastructure and team structure, not a fear of lost authority.
Should I use a subdomain per language or per country?
Per language when your content is the same across countries that share a language, and per country only when you truly serve different offerings, currencies, or legal requirements by market. Don’t geo-lock a language subdomain to one country — use region-qualified hreflang like es-mx versus es-es to handle country nuance instead of splitting into more subdomains than you can maintain.
Is hreflang still required if I use language subdomains?
Yes. The URL structure doesn’t tell Google how versions relate — hreflang does. You need reciprocal annotations across every subdomain, valid ISO language (and optional region) codes, and an x-default, delivered through one method. Subdomains actually make broken reciprocity more likely because the references point across hosts, so audit them regularly.
