Subdomain vs Subdirectory for SEO: Which Structure Wins

11 min read · Technical SEO · Last updated July 2026

Quick answer: Subdirectories (example.com/blog/) consolidate all content signals under your root domain and are the default best choice for most sites. Subdomains (blog.example.com) are treated as separate sites by Google — link equity does not flow as freely, and authority must be built independently. The only cases where subdomains are clearly better: technically distinct products, separate regional sites, or third-party platforms you cannot move to a subdirectory.

Introduction

The subdomain vs subdirectory question has been debated in SEO for over a decade — and the answer has not changed much. Google has provided guidance. The data consistently points in the same direction. Yet sites continue choosing subdomains for blogs, help centres, and e-commerce sections in ways that fragment their domain authority unnecessarily.

The choice matters more than most people realise. A company that moves its blog from blog.company.com to company.com/blog/ has seen organic traffic jump 40-80% in documented case studies — not because the content changed, but because the authority signals consolidated.

What you’ll learn:
– The technical difference between subdomains and subdirectories and how Google treats each
– When subdirectories win for SEO (most cases)
– The legitimate use cases for subdomains
– How to migrate content between structures with minimal disruption
– Where ccTLDs fit and when they are worth the complexity

Table of Contents

1. The Technical Difference
2. How Google Treats Subdomains vs Subdirectories
3. Why Subdirectories Usually Win
4. Legitimate Use Cases for Subdomains
5. ccTLDs as an Alternative
6. Migration Considerations
7. Real Examples and Numbers
8. Making the Decision for Your Site
9. Frequently Asked Questions

The Technical Difference

A subdomain is a prefix before the root domain:
– blog.example.com
– shop.example.com
– help.example.com
– au.example.com

A subdirectory (also called a subfolder) is a path segment after the root domain:
– example.com/blog/
– example.com/shop/
– example.com/help/
– example.com/au/

From a DNS perspective, subdomains can point to entirely different servers and IP addresses — they are genuinely separate from the root domain at the infrastructure level. Subdirectories are always served from the same domain, even if they route to different backend applications via server configuration.

This infrastructure difference is why some organisations prefer subdomains: they can deploy entirely separate tech stacks (a Node.js help centre, a PHP blog, a Python API) without sharing a server. Subdirectories can achieve the same result through reverse proxy configuration, but it requires more infrastructure planning.

How Google Treats Subdomains vs Subdirectories

Google’s official position, stated by John Mueller and other Google Search representatives multiple times: “Google can handle [both] subdomains and subdirectories. […] With time, subdomains can be treated similarly to subdirectories.”

The key phrase is “with time.” And that time has a cost.

In practice, Google’s crawler and indexing systems treat subdomains as separate entities by default. This manifests in several ways:

Link equity flow: internal links between example.com and blog.example.com are treated more like cross-domain links than truly internal links. PageRank does not flow as freely between them as it does between example.com/page-1/ and example.com/blog/post/.

Authority accumulation: a subdomain must build its own Domain Rating (DR) in Ahrefs, its own trust signals, and its own crawl frequency from scratch. A subdirectory inherits all of these from the root domain immediately.

Crawl scheduling: Google crawls subdomains on separate schedules from the root domain. A new page on blog.example.com may wait weeks to be discovered if the subdomain has low crawl frequency, while the same content on example.com/blog/ would be crawled much faster due to the root domain’s established crawl priority.

Why Subdirectories Usually Win

The fundamental reason subdirectories outperform subdomains for SEO is authority consolidation. Every backlink your domain earns raises the entire domain’s authority signals. A blog post at example.com/blog/seo-guide/ that earns 50 backlinks contributes to example.com’s overall authority. The same post at blog.example.com/seo-guide/ earns authority for blog.example.com — a separate entity in Google’s model.

The compounding effect is significant. A root domain with 10 years of link building and 5,000 referring domains transfers all of that signal strength to new subdirectory content immediately. A new subdomain starts accumulating that signal from zero.

The help centre scenario: a SaaS company with a strong root domain (DR 72) decides to launch a help centre at help.example.com. Within six months, the help centre has accumulated a DR of 18 — because it is a new subdomain building authority from scratch. If that same content were at example.com/help/, it would immediately benefit from DR 72 and rank significantly better for support and how-to queries.

Legitimate Use Cases for Subdomains

Subdomains make sense in specific scenarios:

Technically distinct applications: if your SaaS app is at app.example.com and it is a full product requiring authentication, separate deployment, and distinct functionality, a subdomain is appropriate. This is not content competing for organic rankings — it is a different user context entirely.

Acquired brands: if you acquire a company and temporarily maintain their domain, you may operate it as a subdomain (newbrand.example.com) during a transition period. Long-term, consolidation is usually better.

API endpoints: api.example.com is a standard technical convention. These endpoints do not need organic search rankings.

Genuine regional separation with distinct tech stacks: if your Australian operation runs on different infrastructure with a different CMS, au.example.com may be technically necessary even if example.com/au/ would be better for SEO.

Third-party platforms you cannot move: Shopify stores (mystore.myshopify.com), HubSpot knowledge bases, Zendesk help centres — these platforms may enforce subdomain structures. The SEO cost is real; the alternative may be a costly platform migration.

ccTLDs as an Alternative

Country code top-level domains (ccTLDs) like .com.au, .co.nz, .co.uk, .com.np are the third option for international sites.

ccTLD advantages:
– Strongest geographic targeting signal for Google — unambiguous about which country the site targets
– Domain extension builds local trust with users in that market
– Independent from root domain — can have different content strategy per country

ccTLD disadvantages:
– Each ccTLD must build its own domain authority from scratch
– Managing 10+ ccTLDs means managing 10+ link building programmes, 10+ GSC properties, 10+ content strategies
– Higher complexity for hreflang implementation
– Not viable for emerging markets or smaller countries where local TLD is expensive or restricted

For most businesses expanding internationally, the subdirectory approach (example.com/au/, example.com/uk/) is the right starting point. Migrate to ccTLDs only when you have the resources to build authority independently for each market and the country-specific trust signal is worth the trade-off.

Key takeaway: ccTLDs are strongest for local trust and geo-targeting, but they fragment authority. Subdirectories consolidate strength and are easier to manage at scale.

Migration Considerations

Moving content from a subdomain to a subdirectory (or vice versa) is a migration — with all the risks of any migration.

Subdomain to subdirectory (the common upgrade):

1. Set up the subdirectory structure on the root domain (e.g., example.com/blog/)
2. 301-redirect every URL from blog.example.com/post/ to example.com/blog/post/
3. Update all internal links across the site to point to new URLs
4. Update GSC: add the subdirectory to your existing root domain property (it is already included if you have a domain property)
5. Submit an updated XML sitemap with new URLs
6. Monitor GSC Coverage and organic traffic for 4-6 weeks

Migration risks:
– Missed redirects (pages with backlinks that do not redirect)
– Canonical tags on the old subdomain that still reference old URLs
– Analytics configuration that was tracking subdomain as a separate property (will lose historical data comparison)
– Performance short-term drop of 4-12 weeks before traffic stabilises at new (usually higher) levels

The short-term traffic dip during migration is real and worth communicating to stakeholders. The medium-term outcome (consolidated authority, faster indexing) is typically worth it.

Real Examples and Numbers

Basecamp (now HEY): moved their blog from signalvnoise.com to m.signalvnoise.com/ (then later to hey.com/blog/). Each consolidation step brought authority gains. The pattern is well-documented: subdirectory structure outperforms subdomain for blog and content sites.

Typical migration outcome data from case studies:
– 40-80% organic traffic increase within 3-6 months of subdomain → subdirectory migration
– 20-30% faster indexation of new content after migration (due to inherited crawl frequency)
– Link equity recovery: most link equity from subdomain backlinks transfers via 301, but full consolidation takes 3-6 months

For a mid-sized company with blog.company.com receiving 10,000 organic sessions per month, moving to company.com/blog/ typically results in 14,000-18,000 sessions within 6 months — with the same content.

Making the Decision for Your Site

Use subdirectory when:
– The content belongs to the same brand and audience as the root domain
– You want to consolidate authority (almost always)
– You are launching a blog, help centre, resource library, or e-commerce section
– You have the technical capability to configure reverse proxies if needed for different tech stacks

Use subdomain when:
– The section is genuinely a different product or application
– A third-party platform forces the subdomain structure
– You are managing a fully separate business unit with distinct audiences
– The technical migration cost outweighs the SEO benefit

Use ccTLD when:
– You need maximum local trust signals in a specific country market
– You can commit to building domain authority independently per country
– The market size justifies the complexity

Frequently Asked Questions

Does Google ever treat subdomains the same as subdirectories?
Google has stated it can treat them similarly “with time.” In practice, established subdomains with years of authority (like mail.google.com or support.apple.com) perform as well as subdirectories because they have built sufficient independent authority. For new content sections, the subdirectory advantage is clear.

Can I set up a WordPress blog in a subdirectory if my main site is in React?
Yes, using a reverse proxy. Configure nginx or Apache to route example.com/blog/ to your WordPress server while example.com/ serves your React app. This is standard practice and well-documented in server configuration guides.

How much traffic drop should I expect during a migration?
A short-term dip of 15-25% for 4-8 weeks is common as Google re-crawls and reassigns rankings. Well-executed migrations with complete redirect mapping see recovery within 8-12 weeks and subsequent gains above pre-migration levels within 3-6 months.

If my help centre is on Zendesk (subdomain), can I still do SEO on it?
Yes, but with limitations. Zendesk supports custom domains, so you can map example.com/help/ to your Zendesk instance, effectively making it appear as a subdirectory. This requires your DNS and Zendesk configuration to be set up correctly but is supported. Check Zendesk’s documentation for “custom host mapping.”

Conclusion

The subdomain vs subdirectory debate has a clear default answer: subdirectories. They consolidate authority, benefit from root domain strength immediately, and require no separate SEO investment to build independent signals.

Subdomains have legitimate uses — for technically distinct products, third-party platforms, and fully separate business units. But using a subdomain for your blog, help centre, or content section because it seemed simpler is leaving measurable organic traffic on the table.

Let Ignited Nepal Handle This

Assessing your current structure, planning a migration, implementing 301 redirects at scale, and monitoring recovery is a significant technical project. Our team manages this for clients across Nepal, Australia, UAE, and beyond.

→ Request a Free Technical SEO Audit

Written by the Ignited Nepal SEO team. We build organic search systems for businesses across Nepal, Australia, UAE, USA, UK, and beyond. ignitednepal.com