If you’re running a multilingual site, you’ve probably hit the wall on this one. You have content in English, French, German, and Spanish, but every time you try to scale, something breaks — duplicate content warnings, hreflang mismatches, or link equity that seems to vanish into thin air. The subdomain vs subfolder decision feels like a coin flip, but it’s really not. The wrong choice can screw your rankings for months, and the right one can give you a clean path to global growth. This whole thing comes down to how search engines parse your structure, how users experience your localised content, and how much maintenance you can stomach. So which one do you pick? Let’s walk through the data, the edge cases, and the workflow implications.
Understanding the Core Difference: Subdomain vs Subfolder
A subdomain, in case you needed a refresher, sits off your root domain as a separate entity — fr.yoursite.com is a subdomain handling French content, while de.yoursite.com handles German. Search engines treat these as semi-independent sites, for better or worse. A subfolder, on the other hand, is a directory within your main domain — yoursite.com/fr/ stays under the same roof as your English content.
The difference matters because of how Google crawls, indexes, and passes authority. Subdomains can be standalone in a way that fragments your link juice. Subfolders keep everything under one topical umbrella, which tends to consolidate ranking power. But that’s not the whole story. Multilingual setups add their own layer of complexity: hreflang tags, alternative language annotations, and content overlapping issues that don’t exist in a single-language site.
From a technical perspective, subdomains let you spin up separate server stacks. You can host your French site on a different provider if you want, or use a different CMS for each language. Subfolders basically lock you into a single infrastructure. That flexibility point is real, but honestly, most small teams don’t need it.
SEO Implications: Link Equity and Crawl Budget
Here’s where the rubber meets the road. When you use subfolders, every page on your site — regardless of language — sits under the same root domain. That means backlinks to your English homepage pass authority directly to your French subfolder pages, because they share the same domain trust. With subdomains, that link equity is diluted. A link to yoursite.com does almost nothing for fr.yoursite.com in terms of direct authority transfer. Google has clarified this over the years — they treat subdomains as separate entities unless you actively cross-link them heavily.
Crawl budget is another angle. If you have a massive site with thousands of pages in each language, subdomains force Googlebot to crawl each subdomain separately, which can mean slower indexing for new content. Subfolders keep everything in one crawl path, so Google discovers your French article about 24 hours faster than it would on a subdomain. For a small team publishing daily, that delay adds up.
But here’s the nuance: if your multilingual content is wildly different — say, you sell completely different products in France versus Germany — a subdomain might actually help Google understand that difference. It reduces the risk of duplicate content flags because the subdomain acts as a separate site. However, for most brands selling the same products across markets, subfolders are the safer bet.
Pros and Cons at a Glance
| Factor | Subdomain | Subfolder |
|---|---|---|
| Link equity transfer | Weak — separate authority | Strong — shared domain trust |
| Crawl efficiency | Slower — separate crawl budgets | Faster — unified crawl path |
| Technical flexibility | High — separate servers/CMS possible | Low — single infrastructure required |
| Hreflang implementation | Slightly trickier — cross-domain tags needed | Straightforward — within same domain |
| Duplicate content risk | Lower (if content varies heavily) | Higher (if content overlaps) |
| Maintenance overhead | Higher — multiple properties to manage | Lower — one property to maintain |
If you’re a small team with limited resources, that last row — maintenance overhead — will probably tip the scales. Managing hreflang across subdomains is possible, but it adds failure points. One broken tag and your Spanish page starts ranking for the French SERP. Not fun.
Technical Considerations: Hreflang, Canonicals, and Server Setup
Hreflang tags tell Google which language a page is intended for. With subfolders, you use relative paths or full URLs within your domain. With subdomains, you need cross-domain hreflang implementations, which are more prone to errors. For example, a hreflang tag on en.yoursite.com pointing to fr.yoursite.com requires the URL to be fully qualified and accessible. If either subdomain goes down or returns a 5xx, the whole cluster gets messy.
Canonicals also behave differently. On subfolders, you can set a canonical to the root domain to consolidate authority. On subdomains, canonicals across subdomains are treated as cross-domain signals, which don’t carry the same weight. Google might ignore them altogether, leaving you with duplicate content spreads.
Server setup wise, if you use a single CMS like WordPress, subfolders are basically plug-and-play. You install a multilingual plugin, point it at subfolders, and you’re done. Subdomains require separate installations or multisite networks, which doubles your update and maintenance work. For a small team running on a shoestring budget, that’s a pain in the backside.
When to Go with Subdomain Anyway
Look, subfolders are the default recommendation from most SEO analysts — including me, generally — but there are legitimate cases where subdomains make sense. If your content strategy treats each language as a completely separate brand, subdomains give you the isolation you need. For example, a media publisher might have dutch.publisher.com for Netherlands content and belgian.publisher.com for Belgium, even though both speak Dutch. Different editorial teams, different content calendars, separate tracking. That’s a subdomain play.
Another scenario: technical restrictions. If your CMS can’t handle a folder structure for multiple languages — maybe you’re on a legacy system — spinning up subdomains might be the only clean option. I’ve seen companies run Joomla with subdomains for years because the migration cost was too high. It’s suboptimal, but it works.
Also, if you rely heavily on country-specific hosting for speed, subdomains let you host fr.mysite.com on a server in France and de.mysite.com on one in Germany. That geographical closeness can improve load times, which matters for core web vitals.
Practical Recommendations for Small Teams
For most small teams publishing multilingual content, subfolders win. The reason is simple: link equity consolidation and maintenance simplicity. You don’t have the bandwidth to babysit five subdomain installations, and you don’t want to trade link juice for the sake of theoretical flexibility. Set up your hreflang tags correctly, use a solid multilingual plugin, and move on to creating content.
But here’s the thing — creating content across multiple languages is the actual hard part. You need articles in English, translations or adaptations for French, German, Spanish, maybe Japanese. Doing that manually with freelance translators is expensive and slow. At the same time, tools like Surfer SEO and Frase can optimise your content against SERP data, but they don’t solve the workflow problem. Surfer gives you on-page scores. Frase lets you research topics. Neither one autonomously writes and publishes a full article in four languages at once.
That’s where SEOLetters steps into the gap. It’s an AI writing engine that takes a single keyword, researches it, writes a structured article with headings and images, and then lets you route each language through Gemini, OpenAI, or Claude — your choice. You set a multilingual campaign once, and it publishes on its own schedule to WordPress or Shopify. For a small team, that’s the difference between drowning in translation emails and waking up to a fully localised content library.
Step-by-Step Implementation Guide
If you’ve decided on subfolders — which you should, unless you have a strong reason not to — here’s how to set it up properly for multilingual SEO.
1. Choose your language path structure. Use ISO 639-1 codes: /en/, /fr/, /de/. Avoid regional codes unless absolutely necessary. /en-us/ vs /en-gb/ is fine if you have distinct content, but it adds complexity.
2. Configure hreflang tags. Every page needs a self-referencing hreflang and alternative language tags. Use x-default for the fallback (usually English). Test them with Google’s hreflang validator.
3. Set canonical tags. For each language version, canonical to itself. Don’t canonical across languages — that signals duplicate content.
4. Enable language-specific sitemaps. Submit separate sitemaps for /en/, /fr/, etc. in Google Search Console. This helps Google discover the structure faster.
5. Use consistent internal linking. Link from your French page to the English version and vice versa, but only where relevant. Avoid forcing language switchers if the content doesn’t align.
6. Automate content creation. This is where you save your sanity. Instead of writing each article manually, use SEOLetters to generate a base article in English and then auto-translate and publish it to your subfolders with a scheduled campaign. The tool handles the hreflang links and image localisation as part of its output. You literally choose a topic, set a cadence, and it publishes while you do something else.
The Surfer SEO vs Frase Side Note
While we’re on tools, you might be wondering about Surfer SEO and Frase for multilingual work. Surfer is great for on-page structure recommendations — heading density, keyword mentions, word count targets. Frase is better for research, pulling SERP data and suggesting questions to answer. Both can optimise a single article, but neither one manages a multilingual pipeline.
For a small team, the real question isn’t “which content optimizer?” — it’s “how do I produce content at scale without burning out?” Surfer and Frase are point tools. SEOLetters is the engine that runs the whole operation. You bring the strategy; it handles the execution. Plus, you can plug your own API keys into it and route different stages to different models — so you can research with Claude, write with GPT, and translate with Gemini, all in one workflow.
Common Pitfalls to Avoid
- Forgetting to set correct hreflang return tags. If your French page links to English, the English page must link back. Broken reciprocity kills the signal.
- Using automatic translation without human review. SEOLetters lets you set tone and brand voice per language, which cuts down on robotic phrasing, but you still need a native speaker to approve each batch.
- Mixing subdomain and subfolder structures. Don’t put English at
example.comand French atfr.example.com/fr/— that’s a hybrid that confuses crawlers. - Blocking subfolders in robots.txt. Happens more than you’d think. If you block
/fr/, Google never sees your French content.
Measuring Success
Track these KPIs separately per language version. Use Google Search Console to monitor impression and click data for each subfolder. Compare average position for the same keyword across languages — if German is ranking lower than French for a similar search term, your on-page optimisation might be off. Also watch for crawl errors on your hreflang mapper pages.
If you’re using subdomains, you need separate Search Console properties for each one. That’s a hassle, but it gives you granular data. With subfolders, you see everything under one property, which is simpler but requires you to segment by URL prefix.
Final Thoughts
The subdomain vs subfolder debate for multilingual sites isn’t a stalemate — it’s a decision tree. Most small teams should default to subfolders. They preserve link equity, simplify maintenance, and play nice with standard multilingual plugins. Only lean toward subdomains if you have a clear separation of brands, technical restrictions, or specific hosting requirements. At the end of the day, a decision made now is better than three months of analysis paralysis.
When it comes to actually producing the content for those subfolders, don’t rely on manual copy-paste workflows. Use a tool that handles the repetition so you can focus on strategy. SEOLetters gives you the ability to schedule multilingual campaigns that research, write, and publish on their own — in over 20 languages. That’s the kind of workflow that turns a four-person team into a global publishing operation.
Frequently Asked Questions
Does Google treat subdomains as separate sites for multilingual SEO?
Yes, generally. Google considers subdomains as distinct entities unless they are heavily interlinked and share consistent content across languages. This means link equity from your main domain does not automatically flow to your subdomain pages. Subfolders, on the other hand, keep everything under one authority umbrella.
Can I use both subdomains and subfolders for different languages?
You can, but it’s not recommended. Mixing structures confuses crawlers and complicates hreflang implementations. If you start with fr.example.com for French, keep all other languages under similar subdomains (e.g., de.example.com) rather than switching to a folder structure midway.
How do hreflang tags work differently between subdomains and subfolders?
With subfolders, hreflang tags point to relative or absolute URLs within the same domain (e.g., https://example.com/en/ and https://example.com/fr/). With subdomains, each tag is a fully qualified cross-domain URL (e.g., https://en.example.com/ to https://fr.example.com/). The latter is more error-prone because each subdomain must be separately named and accessible.
What happens if I change my structure from subdomain to subfolder later?
It’s painful but doable. You need to set up 301 redirects from each subdomain page to the corresponding subfolder, update hreflang tags across the whole site, and submit new sitemaps to Google Search Console. Expect a temporary ranking dip while search engines re-crawl your new structure. Plan for 4-6 weeks of volatility.
Is a subfolder always better for small teams?
In most cases, yes. Subfolders reduce maintenance overhead, consolidate link authority, and simplify reporting. The only exceptions are when you have unique technical constraints (e.g., separate CMS installs per language) or when your content strategy treats each language as an independent brand with zero topical overlap.
Leave a Reply