Subdomains vs. subdirectories: what actually affects SEO
The subdomain versus subdirectory debate resurfaces every time a team launches a new section. Here is what really changes for SEO and what does not.
Every year someone asks whether a new blog, docs site, or help center belongs on blog.example.com or example.com/blog. The debate resurfaces with international sites and support portals too. The honest answer is that the choice matters less than most articles claim, and the reasons it does matter are not the ones usually listed.
The technical reality
Google has said for years that its systems can treat a subdomain as part of the same site when they recognize the two belong together. That recognition is not automatic. It depends on consistent branding, cross-linking, matching technical setup, and enough signals that the systems can connect the dots. A subdirectory skips that step because it never leaves the root domain in the first place.
In practice this means a subdirectory tends to be the lower-risk default, not because subdomains are penalized, but because they add a variable you have to manage correctly. Get the signals right and a subdomain can perform close to a subdirectory. Get them wrong, through inconsistent SSL, broken cross-linking, or a slow, thin launch, and it can take longer to build authority than it would have on the root domain.
why the old advice stuck around
Older SEO advice treated subdomains as separate sites by default, splitting link equity and authority. That model came from a time when search engines had cruder tools for recognizing site relationships. Some of that caution is outdated, but not all of it. Country-specific subdomains and ccTLDs for international SEO still function closer to separate properties than subdirectories do, which is a real structural difference, not a myth.
When subdirectories win
- You want new pages to inherit the trust and links your root domain already has, without a ramp-up period.
- Your team cannot guarantee consistent technical setup, like SSL, redirects, and canonical tags, across a separate subdomain.
- The content is closely tied to your core product or brand, such as a blog, changelog, or documentation section.
- You are launching on a domain that is still building authority and cannot afford to split its signals.
When subdomains make sense
- The section runs on a different platform or CMS, and folding it into a subdirectory is a real engineering project, not a routing change.
- You need to separate a genuinely different audience or business unit, like a support portal from a marketing site.
- Security, compliance, or infrastructure requirements call for isolation that a shared subdirectory cannot provide.
- You are running a large, well-linked, mature site where a new subdomain can borrow enough brand recognition to launch fast.
What AI answer engines do differently
AI answer engines build their own retrieval systems, separate from Google's index, and those systems are still young compared to two decades of search engine crawling. There is no solid public evidence yet that tools like ChatGPT or Perplexity reliably connect a subdomain back to its parent brand the way a mature search index can. Treat that as an open question, not a settled one, and do not assume a subdomain automatically inherits your brand's citation history.
The structure question matters far less than whether every page loads fast, has genuinely unique content, and is easy to link to.
How to decide, in practice
- Check whether your CMS or hosting can support a subdirectory without months of engineering work. If it can't, that cost often outweighs the theoretical SEO edge either way.
- Look at how established your root domain already is. A brand-new domain has little legacy trust to lend, so the two options sit closer together.
- If you have a mature, well-linked domain and the platform allows it, default to a subdirectory. It removes a variable instead of adding one.
- Whichever you pick, keep canonical tags, your XML sitemap, and hreflang, if it applies, consistent so crawlers and AI engines are not left guessing how the pieces fit together.
Do not spend a quarter planning a migration on the theory that a subdirectory will outrank a subdomain on its own. Put that effort into internal linking, content quality, and making sure the new section is easy to crawl instead. Those levers reliably move rankings. Where you park the URL rarely does, as long as the technical basics are in place.