Google states it has no ranking or indexing preference between a folder vs. a subdomain, but real migrations from subdomain to subfolder keep showing traffic gains. For most company blogs and international content, use a subfolder; reserve subdomains for a different audience, tech stack, owner, or compliance requirement.
- Google says it has no ranking preference between subdomains and subfolders, and no independent controlled test has proven otherwise.
- A subdomain is crawled as a distinct host, so it doesn't inherit the root domain's trust and link equity on day one the way a subfolder does — that ramp-up is likely what drives the migration gains practitioners keep reporting.
- Portent's case study reported a 40% session increase after a blog moved to a subfolder and Furl reported 34%, but both changed internal linking and technical fixes at the same time, so neither number is a formula for your site.
- Use a subfolder unless the content has a genuinely different audience, tech stack, owner, or a compliance requirement forcing separation — a company blog almost never qualifies.
- For international content and brand-new sites, default to subfolders; subdomains mean building a separate backlink profile for every region.
You're staring at a migration ticket: move blog.yourcompany.com into yourcompany.com/blog, or leave it alone. Google's own documentation says the structure doesn't matter. Every case study you can find says otherwise. Somewhere in a forum thread, John Mueller appears to have said both things. That's the real tangle behind the folder vs. subdomain question, and it's worth sorting out before anyone touches a redirect.
Folder vs. subdomain for SEO: the quick answer
Google's Search Central documentation states it has no ranking or indexing preference between subdomains and subfolders, according to reporting from Search Engine Journal. That's Google's current stated position, full stop — not a loophole, not a nuance buried in fine print.
And yet. Real-world migrations and practitioner case studies keep showing traffic gains after a business consolidates a subdomain into a subfolder. Not occasionally — repeatedly, across different sites and different years.
So is a subdomain or a subfolder better for SEO? The honest answer is that no controlled, independent test has settled this. What exists is a clear statement from Google on one side, and a handful of individual migration case studies on the other. Nobody has published a clean experiment that isolates URL structure as the only variable changed. The dispute isn't really about facts — it's about how much weight you give an official statement about how ranking systems treat a category of URL structure, versus anecdotal evidence about what happens when specific, real sites actually move. Separate those two things, and the picture stops looking like a contradiction. More on that below.
What's actually different between a subdomain and a subfolder?
A subdomain — blog.example.com — is technically treated by crawlers as a distinct host. Not a separate domain in the ownership or DNS sense, but a separate thing Googlebot has to discover, crawl, and evaluate somewhat independently of the root domain. A subfolder — example.com/blog — carries no such ambiguity. It's unambiguously part of the same host from the very first crawl.
That distinction has real operational consequences. A subdomain needs its own verification as a separate Google Search Console property, and it has to be discovered and crawled on its own, apart from the root domain's existing crawl patterns. A subfolder never requires any of that — it rides along with the verification and crawl history the root domain already has.
This is also where the "does a subdomain hurt domain authority" question usually comes from. A subdomain doesn't actively damage the root domain's standing. It's more that a subdomain doesn't automatically inherit the root domain's accumulated trust and link equity the way a subfolder does. Googlebot has to learn to crawl a new subdomain, and according to reporting from Search Engine Roundtable, Mueller has described this crawl-discovery process as mostly a formality for the first few days — a short ramp-up, not a lasting penalty. But a formality still takes time, and that short window is exactly where a lot of the real-world gap between subdomains and subfolders seems to live.
What Google officially says, and what Mueller actually means
Google's Search Central guidance is unambiguous on paper: no ranking or indexing preference between the two structures. Mueller has backed that up directly in Office Hours — per Search Engine Journal, he has repeated that Google generally treats subdomains and subfolders the same for ranking purposes. So does Google rank subdomains differently than subdirectories? By Google's own account, no — not as a structural category.
Here's where it gets more interesting. Mueller has also said, separately, that he personally prefers keeping content together on one domain for operational simplicity rather than for any ranking advantage. That's a workflow opinion, not an algorithmic claim, and the distinction matters.
And then there's the part most coverage skips past too quickly: Mueller has acknowledged, according to Search Engine Roundtable, that moving content from a subdomain to a subdirectory often results in improved rankings in practice. Put that next to "we see these the same" and it looks like a flat contradiction. It isn't, once you look at the mechanism that's probably driving it.
Why practitioners keep seeing subfolder wins anyway: the ramp-up theory
This is the part most articles on this topic treat as an unsolved mystery. It doesn't have to be — there's a plausible, straightforward explanation, even though it's a practitioner interpretation rather than something Google has confirmed in detail.
The reasoning goes like this: a brand-new subdomain sitting under a trusted root domain doesn't automatically carry that domain's full trust and ranking history the moment it goes live. Before a subdomain gets treated as a seamless extension of the root domain, Google's systems likely need some signal that it's genuinely affiliated — internally well-linked, consistent in quality, and clearly part of the same operation. That takes crawling and time, the same kind of ramp-up any new section of a site goes through, with an extra layer of host-level discovery stacked on top.
A subfolder never faces that ambiguity. Because it's part of the same host from day one, it can draw on the root domain's existing authority without that separate discovery period.
Treat this as a working hypothesis, not a confirmed mechanism — Google hasn't spelled out exactly how it evaluates subdomain affiliation. But it's the explanation that best reconciles "Google says no preference" with "sites see traffic gains after migrating," without requiring you to believe Google is misrepresenting its own algorithm or hiding a subdomain penalty. The system may genuinely not discriminate against subdomains as a category. A specific subdomain, at a specific point in its life, may simply not yet carry the signals a subfolder inherits on day one.

Real case studies: what migrations actually showed
The two most-cited examples in this debate are worth looking at directly, limits included.
Portent's documented case, referencing Jesse Heap, involved moving a blog from blog.pinkcakebox.com to www.pinkcakebox.com/blog. The result, according to Portent, was a 40% increase in sessions after the move. It's a real, specific result, and the original migration is a number of years old now — it's also been recycled across newer articles as though it were definitive proof rather than one site's outcome at one point in time.
A more recent example, published on the Furl blog, reports a 34% organic traffic increase after a similar subdomain-to-subfolder blog migration. Different site, different year, same general direction.
Does moving a blog from a subdomain to a subfolder increase traffic? In these two cases, yes. But both are individual case studies, not controlled experiments, and neither isolates URL structure as the only variable that changed during the migration — internal linking usually gets rebuilt during a project like this, technical issues often get cleaned up at the same time, and the site's authority at the moment of migration varies enormously from one business to the next. None of that makes the results fake. It does mean you shouldn't treat either number as a formula for what will happen to your site.
Subdomain vs. subfolder for international SEO
This is the one corner of the debate where current guidance is fairly settled. Semrush's international SEO guidance, published September 25, 2025, recommends generally using subfolders for international SEO because they consolidate domain authority and are easier to manage.
The reasoning tracks with the ramp-up theory above. Semrush notes that an international subdomain — fr.example.com, de.example.com — functions essentially as a separate website: it has to build its own backlink profile to compete in its local search results, because it isn't automatically drawing on the authority of the root domain or your other regional pages. That's a real resource cost, not a theoretical one. It means separate link-building effort, multiplied across every market you operate in.
Subdomains can still work for multilingual or multi-region sites — some large, well-resourced companies run exactly this setup. But if you don't have the budget or team to build authority independently for every regional subdomain, subfolders (example.com/fr/, example.com/de/) are the lower-risk default for a business weighing subdomain vs. subfolder for international SEO today.
When to use a subdomain instead of a subfolder
None of this makes subdomains a mistake. There are legitimate reasons to use one, and they cluster around a handful of specific situations:
- A genuinely different audience or purpose — a help center, a jobs portal, or a customer-facing app that doesn't share content intent with your marketing site.
- A different technology stack or hosting environment that genuinely can't live on the same server or CMS as your main site. This is the common pattern with SaaS docs and blog setups, where docs.example.com runs on a dedicated documentation platform incompatible with the main site's CMS.
- Different ownership — a separate team managing content independently, with its own publishing workflow.
- A hard regulatory or data-residency requirement forcing technical separation.
Outside those four cases, current guidance favors keeping closely related, centrally managed content in a subfolder. A company blog is the clearest example: docs might justify a subdomain on technical grounds, but a blog usually doesn't, because it typically shares the same audience, the same team, and the same marketing intent as the rest of the site.

What technical guidance recommends for new sites
For net-new sites, the guidance is more clear-cut. Carnegie Mellon's published web best-practices guidance states that subdirectories provide the best and fastest SEO authority for new external-facing websites, and it recommends subdirectories in most instances. That recommendation applies specifically to new sites or new sections — there's no existing subdomain history to weigh against migration risk, so there's no reason to take on a ramp-up period voluntarily. A company blog launching today should default to a subfolder unless one of the four conditions above genuinely applies.
The AI-search wrinkle: does this affect ChatGPT, Gemini, and AI Overviews too?
There's a newer angle in this conversation that most existing coverage hasn't caught up with, and it's worth raising even though nobody has formally tested it. Nothing here is established the way the classic ranking debate is — it's reasoning by analogy, not a documented finding.
AI Overviews and chatbot answers have to decide which source to name when they generate a response. One plausible consideration, following the same trust-concentration logic as the ramp-up theory above, is that a system doing that evaluation might have an easier time recognizing one coherent domain as the authority on a topic than a loosely connected pair of hostnames that happen to share a root name. If that turns out to be true, splitting content between example.com and blog.example.com could mean asking an AI system to infer a connection that the crawl and link structure don't make obvious. Subdomain vs. subfolder AI search visibility is a question nobody has a clean, confirmed answer to yet — but the directional logic points toward consolidation.
That's a distinct question from the Mueller-era ranking debate, and it's newer. Treat it as a reason to lean toward consolidation when you're building new content from scratch, not as a settled rule to redesign an existing, working site around.
Is migrating from subdomain to subfolder worth the risk?
If your subdomain is already performing adequately, migration is not a free action. It carries real technical risk: redirect chains that need careful mapping, backlinks pointing at the old subdomain that may not pass full value even through proper 301s, and a stretch of ranking volatility while Google re-processes the moved content. None of that is hypothetical — it's the standard cost of any URL structure migration, subdomain or not.
It's also worth being honest about what the evidence does and doesn't support. No independent party has produced a controlled test proving subfolders rank better than subdomains as a general rule. What exists is Google's stated position of no preference, plus individual case studies like Portent's and Furl's showing gains after specific migrations. That's a reasonable basis for a decision. It isn't proof of a universal rule.
Before migrating anything, export and preserve your historical performance data: rankings, traffic trends, and your current backlink profile. Without a documented baseline, any before-and-after comparison you run later is a guess dressed up as a result.
Migration is most justifiable when your subdomain fails one of the legitimate-use-case tests above — when it doesn't actually have a different audience, a different tech stack, separate ownership, or a compliance requirement forcing the split. If none of those apply and the subdomain exists mostly out of historical accident or an old CMS limitation, moving it into a subfolder is a reasonable call. If one of those conditions genuinely applies, the operational cost of migrating may not be worth an unproven ranking upside.
Decision checklist: folder or subdomain?
Run your situation against these before deciding:
- Same audience, same purpose, same team managing it → use a subfolder. This covers most company blogs.
- Different technology stack, different ownership, or a hard compliance/regional requirement → a subdomain may be justified.
- International or multilingual content → default to subfolders unless you genuinely have the resources to build each subdomain's authority and backlink profile independently.
- A new site or a new content section with no existing history → subfolders are the lower-risk, faster path to inherited authority.
- Already live on a working subdomain with no red flags from the list above → weigh the real migration risk against an unproven ranking upside before touching anything.
If you're deciding this question because you're about to start publishing content regularly, the structural call matters before the first article ever goes live. HelloSeek writes fact-checked articles in your voice and publishes them into a subfolder of your existing domain rather than a separate subdomain that has to earn its own trust from scratch, and it tracks whether your business shows up when people ask AI assistants for recommendations, alongside your regular search rankings. You can see how it fits your setup at helloseek.ai.
Frequently asked questions
Is a subdomain or a subfolder better for SEO?
Google's Search Central documentation says it has no ranking or indexing preference between the two. But no controlled, independent test has settled the question, and practitioner case studies repeatedly show traffic gains after consolidating a subdomain into a subfolder. For closely related, centrally managed content, a subfolder is the lower-risk default.
Does using a subdomain hurt your domain authority?
A subdomain doesn't actively damage the root domain's standing. The issue is that it doesn't automatically inherit the root domain's accumulated trust and link equity the way a subfolder does — Googlebot has to discover and crawl it as a distinct host first. Mueller has described that discovery process as mostly a formality for the first few days, but it still takes time.
Why does Mueller say subdomains and subfolders rank the same but also say subfolders perform better after migration?
Those two statements aren't actually a contradiction. Google's systems may genuinely not discriminate against subdomains as a category, while a specific new subdomain, at a specific point in its life, hasn't yet accumulated the signals a subfolder inherits on day one. That ramp-up period is a practitioner interpretation, not a mechanism Google has confirmed.
Should I use a subdomain or subfolder for international SEO?
Subfolders like example.com/fr/ are the safer default. Semrush's international SEO guidance recommends subfolders because they consolidate domain authority and are easier to manage. An international subdomain such as fr.example.com functions essentially as a separate website and has to build its own backlink profile for every market, which is a real resource cost.
When is it actually okay to use a subdomain instead of a subfolder?
Four situations justify one: a genuinely different audience or purpose (a help center, jobs portal, or customer app), a different technology stack or hosting environment that can't live on your main CMS, different ownership with its own publishing workflow, or a hard regulatory or data-residency requirement. Outside those cases, keep content in a subfolder.
Should a company blog live on a subdomain or in a subfolder?
A subfolder, in almost every case. A blog usually shares the same audience, the same team, and the same marketing intent as the rest of the site, so there's no reason to make it earn trust as a separate host. Docs might justify a subdomain on technical grounds; a blog rarely does.
Is it worth migrating an existing subdomain to a subfolder?
Only if the subdomain fails the legitimate-use-case tests — no different audience, tech stack, ownership, or compliance need. Migration carries real risk: redirect chains, backlinks that may not pass full value through 301s, and a stretch of ranking volatility. If your subdomain is performing adequately and one of those conditions genuinely applies, the operational cost may not be worth an unproven ranking upside. Export your rankings, traffic trends, and backlink profile before you touch anything.
Updated Nov 13, 2026
