Google's official stance has remained unchanged for years: Google Search handles subdomains and subfolders equally well, crawling, indexing, and ranking content regardless of which path you choose.
In practice, every site migration I've audited or executed between these two structures tells a very different story.
This isn't because Google can't technically handle subdomains. It's because of what happens to link equity, crawl budget allocation, and host-level signals the moment you partition a site across separate hostnames.
When a client moves a blog, resource centre, or international section from a subfolder to a subdomain (or vice versa), the impact isn't theoretical. It shows up immediately in server log files and Google Search Console (GSC) coverage reports.
What's actually happening under the hood?
The core difference comes down to DNS and host-level entity separation:
- Subfolder (paullovell.uk/blog/): Lives on the same host and root path. Search engines treat it as an integral branch of the primary domain tree.
- Subdomain (blog.paullovell.uk): Functions as a distinct host at the DNS level. Crawlers and indexing pipelines evaluate it as an isolated property with its own trust metrics, crawl demand, and host-level configuration.
Everything else — ranking volatility, split authority, and crawl prioritisation — stems directly from Google treating a subdomain as a standalone crawlable unit.
Where subdomains genuinely cost you traffic
1. Backlink and authority fragmentation
This is the most contested point in the debate, so it's worth being precise: Google has stated publicly that it evaluates subdomains and subfolders of the same site under one shared authority model. That's Google's official position, not a claim I'm disputing outright.
What I can say from the practitioner side is narrower — in log files and GSC data across the migrations I've personally run, consolidating a subdomain blog back into a subfolder has usually coincided with a noticeable uplift in root-domain rankings over the following couple of months. That's a correlation I've observed repeatedly, not a controlled experiment, and other explanations (better internal linking post-migration, seasonal effects, general site improvements bundled into the same project) can't be fully ruled out. Treat it as a reasonable practitioner signal to weigh, not a settled fact that overrides Google's own statement.
2. Isolated crawl budgets
Googlebot allocates crawl budget per host. A main site with three subdomains isn't sharing one master crawl budget; it's running across four separate crawl queues, each driven by its own host demand.
A content-heavy subdomain with low initial authority often gets under-crawled, delaying the indexing of new posts, while the high-authority root domain sits underutilised.
3. Analytics and governance overhead
Cross-host setups complicate your stack:
- Google Analytics 4 (GA4) domain configuration and cross-domain tracking require additional safeguards.
- Google Consent Mode v2 signals don't always propagate cleanly across separate subdomains without precise cookie-domain mapping.
- Canonical tags, hreflang annotations, and structured data validation are prone to silent breakage when engineering teams treat subdomains as "just another folder on the main site."
When subdomains are still the right choice
Subdomains aren't inherently wrong — they're just misused when applied to standard marketing content. A subdomain is the correct architecture when there is a strict technical, functional, or organisational boundary:
- Different application stacks: A SaaS application (app.domain.com), customer portal, or help desk running on external platforms (like Zendesk or Salesforce Knowledge) where reverse-proxying into a subfolder introduces unacceptable latency or security risks.
- E-commerce separation: Running a main content site on WordPress while the store operates on Shopify (shop.domain.com), where deep integration at the subfolder level isn't viable.
- Complex multi-regional implementations: Distinct international entities requiring localised hosting infrastructure, separate database compliance (GDPR/CCPA), and isolated server configurations.
The decision matrix: how to choose
| Criteria | Subfolder (example.com/folder) | Subdomain (sub.example.com) |
|---|---|---|
| Primary goal | Maximise organic growth & pool backlink authority | Isolate distinct tech stacks or business entities |
| SEO impact | Consolidates link equity & topic authority natively | Splits signals; requires separate link-building effort |
| Crawl efficiency | Unified crawl budget across main site | Separate crawl allocation per subdomain |
| Technical setup | Simplified analytics, SSL, and canonical management | Requires individual GSC properties & cross-host tracking |
Practical recommendation
Default to a subfolder unless an unavoidable technical or compliance barrier forces a subdomain.
"Marketing wants it to feel like a distinct brand experience" is not a valid technical barrier. Design templates, unique routing, and custom layout styling can achieve that exact experience within a subfolder — without fracturing your crawl budget or link equity.
If you currently operate a subdomain that is underperforming, don't rush into a risky migration immediately:
- 1Run a log file analysis to determine whether Googlebot is under-crawling the subdomain relative to its published URL volume.
- 2Audit backlink distribution to measure how much link equity is trapped on the subdomain.
- 3Test internal link architecture from your high-authority root pages into key subdomain landing pages.
If the data confirms a structural bottleneck, plan a migration to a subfolder with 1:1 301 redirects, updated sitemaps, and strict canonical alignments.
Related articles
JavaScript Hydration & SEO: Why 'Rendered HTML' Still Fails Search Engines
"Google renders JS, so it's fine" misses two things: two-wave indexing, and AI crawlers that don't render JS at all. Here's where hydration actually breaks.
How to Host Shopify or Zendesk in a Subfolder Using Cloudflare Workers
"Our tech stack won't allow a subfolder" is usually solvable with a reverse proxy at the edge, not a platform change.
The Subdomain-to-Subfolder Migration Blueprint
The structure change is the easy part. The redirects, canonicals, and GSC property setup are where migrations actually go wrong.
International SEO Architecture: Subfolders vs. Subdomains vs. ccTLDs
International expansion is one of the few legitimate reasons to reach for a subdomain or ccTLD instead of a subfolder. Here's how to actually choose.
Written by
Paul Lovell
International SEO Consultant & Founder of Always Evolving SEO. 15+ years running technical audits, log-file analysis, and root-cause fixes for multimillion-dollar businesses — speaker at SMX London, Search & Content Summit, and SEMrush events.