You are about to launch a blog, a store, or a help center, and your platform asks one deceptively small question: should it live at blog.example.com (a subdomain) or example.com/blog (a subdirectory)? It feels like a hosting detail. It is actually a site-architecture decision that shapes how easily that section ranks and how much of your domain's hard-won authority it inherits.
The takeaway up front: for most sites, a subdirectory is the safer default, because it keeps your content under one domain where authority, internal links, and crawl signals compound. A subdomain is not a penalty and it does not "lose" your rankings — but it tends to behave more like a separate site, so the new section often has to earn its standing more independently. Choose a subdomain when there is a concrete technical or organizational reason for the separation, not by accident.
The actual difference: one site, or two?
A subdirectory (or subfolder) is a path on your existing domain: example.com/blog, example.com/shop. To a search engine it is unambiguously part of example.com, so everything that built the domain's reputation — backlinks, brand signals, the internal link graph — surrounds that folder by default.
A subdomain is a host that sits in front of your domain: blog.example.com, shop.example.com. It can point to entirely different infrastructure — a different server, CMS, even a different team's stack — and that flexibility is the whole appeal. The catch is that search engines have historically treated subdomains with more independence, so the root domain's authority does not always flow into one as freely as it flows into a folder.
That is the heart of the decision. A subfolder says this is the same site. A subdomain says this is related, but it may stand on its own.
How Google actually treats each
Be careful with absolutes here, because the topic attracts more myth than fact. Google's public position is that it can crawl, index, and rank content on subdomains and subdirectories alike, and that you should use whichever structure makes sense for your site. There is no ranking bonus for a subfolder written into the algorithm, and no penalty for a subdomain.
The nuance is in how consolidation works in practice. Authority is built from signals — links, relevance, internal structure — that accrue to URLs and the sites around them. In a subfolder, your content is plainly inside the same site, so those signals reinforce each other for free, and a new /blog compounds faster off the domain's existing reputation. A subdomain is treated as closely associated with the root but evaluated with some independence, so it is more self-contained: it can still rank well, but you are more likely building its reputation separately rather than borrowing the parent's wholesale. None of this means subdomains are "bad for SEO" — it is a reason to use them on purpose.
Why a subdirectory is the usual default
For the common case — a marketing site adding a blog, a resource library, or a help center — the subfolder wins for reasons that are easy to state:
- Authority stays consolidated. Every link your core pages have earned surrounds the folder, so new content starts from strength rather than from zero.
- Internal linking is frictionless. Linking between
example.com/servicesandexample.com/blog/...is just same-site linking — no cross-host considerations, no diluted signal. Your internal link graph, one of the most controllable ranking levers you have, stays whole. - One property to manage. One domain to secure and renew, one analytics view, one Search Console property, one canonical brand home. Fewer moving parts means fewer places for tracking and redirects to quietly break.
If you cannot name a specific reason the section needs its own host, that absence is the answer: keep it in a subfolder.
When a subdomain is the right call
A subdomain is not a fallback; it is the correct choice when separation is a feature. Reach for one when:
- The platform forces it. Many hosted products — help desks, status pages, community platforms, knowledge bases — only run on their own host (
help.example.com,status.example.com). Pointing a subdomain with a DNS record is far cleaner than contorting a third-party app onto a subfolder via fragile reverse proxying. - The technology stack genuinely differs. If your store runs on a wholly different platform from your marketing site, a subdomain lets each live on its own infrastructure without one becoming a maintenance hazard bolted onto the other.
- The audience or risk profile is distinct. A developer portal, a careers site, or a deliberately separate brand can warrant its own space — and isolating a high-risk or experimental property keeps its issues from touching the main site.
The honest framing: choose a subdomain when the separation buys something concrete — platform compatibility, technical independence, or audience focus — and accept that the new section may need a little more deliberate work to build its standing.
A short decision checklist
Run a candidate section through two questions before you commit. Does the platform or stack require its own host? If yes, a subdomain is the pragmatic choice. Is the audience or risk profile genuinely separate from the main site? If yes, a subdomain's independence is a feature, not a cost. If neither holds, the content is core to your brand and the subfolder wins — it inherits the domain's authority and internal links by default. When the answers conflict, weight the platform question heavily; a hard technical constraint usually decides it.
Moving between them is a migration — treat it like one
The most expensive mistake is treating subdomain-versus-subfolder as a setting you can flip later. It is not. Changing blog.example.com to example.com/blog (or the reverse) changes every URL in that section, and done carelessly it breaks links, scatters crawl signals, and surrenders rankings you spent months earning.
If you must switch — usually consolidating a subdomain into a subfolder to pull its content under the main site's authority — handle it with the same rigor as moving domains: map old URLs to new ones, set permanent (301) redirects, update internal links, and expect a temporary dip while search engines recrawl and reattribute. That is the same discipline covered in how to change domains without losing your search rankings. The lesson for this decision: get the structure right the first time so you never have to run that migration at all.
FAQ
Is a subdirectory really better for SEO than a subdomain?
Not as a rule baked into the algorithm — Google says it can rank both, with no automatic bonus or penalty either way. In practice a subdirectory often performs better for site sections because it sits plainly inside your domain, so authority, internal links, and crawl signals reinforce it from day one. A subdomain can rank just as well but tends to build its standing more independently, which can take longer.
Will moving from a subdomain to a subfolder boost my rankings?
It can help when the goal is consolidation — pulling a subdomain's content under the main domain so it shares the site's authority more directly. But only if you execute the migration cleanly: map and 301-redirect every URL, update internal links, and expect a recovery period. A botched move loses more than it gains, so the boost is in the careful execution, not the switch itself.
Does a subdomain count as a separate website to Google?
Roughly, yes — search engines treat a subdomain as closely associated with the root domain but evaluate it with some independence, more like a related site than an integral folder. That is exactly why subdomains suit cases where you want separation, and make a poor default when you want a new section to inherit the main site's reputation immediately.
Where should my blog live — on a subdomain or a subfolder?
For most sites, in a subfolder at example.com/blog. A blog is usually core to your brand and topic, and a folder lets it compound with the authority and internal links you have already built. Put a blog on a subdomain only for a concrete reason — typically a blogging platform that runs on its own host, or a deliberately separate editorial property. And remember the decision is per-section: it is normal to keep brand-core content in subfolders while platform-bound properties (help desk, status page) live on subdomains.
Next step
The subdomain-versus-subdirectory question rarely deserves a snap answer, because the structure you pick is hard to change later. Default to a subfolder so new content inherits your domain's authority and internal links — and reach for a subdomain only when separation buys something concrete: a platform that demands its own host, a genuinely different stack, or a distinct audience. Decide once, decide deliberately, and you avoid an expensive migration down the line. For more practical, vendor-neutral guidance on managing domains and search visibility, visit myqsd.com.
