Subdomain vs Subdirectory: Which Is Better for SEO?

blog.example.com or example.com/blog/ — the subdomain vs subdirectory question is SEO's longest-running turf war: Google insists both work fine; two decades of practitioner case studies show sites gaining traffic by moving content from subdomains into subdirectories. The resolution, as usual, is that both sides are answering different questions. Here's the actual mechanics, the honest recommendation, and the cases where a subdomain genuinely is the right call.

What the two structures mean to a search engine

A subdirectory (example.com/blog/) is unambiguously part of the site — one host, one crawl context, one pool of accumulated signals. A subdomain (blog.example.com) is technically a separate host that search engines may treat as related-but-distinct: its content, engagement history and links can consolidate with the main domain's — or partially not — depending on how strongly the two present as one entity (shared design, cross-linking, unified navigation). That "may" is the entire controversy: Google says its systems generally figure it out; the case-study record says "generally" and "figure it out" leave real equity on the table, sometimes lots of it.

Why the practitioner record favours subdirectories

1. Signal consolidation is guaranteed, not inferred. Every post at /blog/ feeds the domain's authority pool directly; every link the blog earns strengthens the money pages' host, and vice versa — no algorithmic judgment call required. The migration case studies (blog moved into subdirectory, traffic rises weeks later) are numerous and directionally consistent enough that most experienced SEOs stopped debating.
2. One crawl identity: a single host's crawl attention, freshness record and quality evaluation cover everything; a subdomain builds its own from scratch — the cold-start problem, self-inflicted on half your content.
3. Internal linking works at full strength within one host's architecture; cross-subdomain links behave more like external ones structurally.

The honest counterpoint: for a strong site whose subdomain is heavily interlinked and clearly the same brand, consolidation often works out fine — Google isn't lying. The subdirectory recommendation is about removing the "often" from that sentence.

When a subdomain is genuinely right

• Truly separate products or audiences: app.example.com (the logged-in product), docs sites with different platforms, regional/language editions under an international architecture where separation is the design.
• Content you don't want sharing your quality profile: user-generated sprawl, forums, or anything whose thin-page volume would dilute the main site's evaluation — separation as quarantine, deliberately forfeiting consolidation.
• Technical necessity: a platform (help desk, e-commerce hosted service, landing-page tool) that can only live on a subdomain — a real constraint, worth revisiting whenever reverse-proxying it into a subdirectory becomes feasible.

The decision rule: content that should help your rankings goes in a subdirectory; content that shouldn't goes on a subdomain. The blog — existing precisely to build the domain's topical authority per the strategy — is the clearest subdirectory case there is.

Already on a subdomain?

If the blog (or other ranking-intended content) lives on one: the move into a subdirectory is a standard migration — exact-counterpart 301 map, internal links updated, both properties watched in Search Console — with the usual settling weeks and, per the case-study record, a fair chance of net gain after. Weigh it like any migration: worth doing when the content is significant and the site is otherwise stable; not worth stacking onto a redesign week. And done is done — a well-executed move beats an optimal structure planned forever.

Frequently asked questions

Does Google penalise subdomains?

No — nothing about a subdomain is negative; the question is only whether its signals consolidate with the parent. Plenty of subdomains rank superbly. The subdirectory preference is about guaranteed pooling, not avoiding punishment.

What about country sites — subdomain, subdirectory, or ccTLD?

The international structure question has real trade-offs (ccTLDs signal country strongest but split authority completely; subdirectories pool authority but need hreflang discipline; subdomains sit awkwardly between). Short version: subdirectories with hreflang for most businesses, ccTLDs when country identity is commercially decisive.

Does www vs non-www matter the same way?

No — www is technically a subdomain, but you serve the site on exactly one form and 301 the other, so there's no split to worry about; the choice is cosmetic. What matters is picking once and enforcing it everywhere, per the launch checklist — consistency being, as usual, the actual ranking advice, alongside the two levers structure can't substitute for: content and earned authority (ask us about the second).