Websites and Tech

Subdomain vs Subfolder

Also called blog.example.com vs example.com/blog

The choice between putting a blog or shop at blog.example.com or example.com/blog, which changes how search engines treat it.

Quick facts: Subdomain vs Subfolder

Category
Websites and Tech
Also called
blog.example.com vs example.com/blog
Level
Intermediate
Affects
Link equity, crawling, analytics setup, reporting effort
Where to see it
Search Console (a property per subdomain), GA4, Screaming Frog
In this article4
  1. How subdomains and subfolders differ
  2. Why the choice matters
  3. Where the decision goes wrong
  4. How to act on it

How subdomains and subfolders differ

A subfolder is a path on the same host: everything after the slash still belongs to one website, served by one server, under one name. A subdomain is a separate host name that the domain name system points wherever you like — it can run on different hardware, a different platform and a different technology stack from the main site. That flexibility is usually why teams reach for one.

Search engines can crawl and index either. Google has said consistently that it works out the relationship between a subdomain and its parent domain in most cases. The difference shows up in how reliably signals gather, not in whether the pages are eligible to rank at all. A subfolder sits inside the same house, so internal links, crawl paths and the reputation the domain has earned are pooled by default. With a subdomain, that pooling is something the search engine infers rather than something the structure guarantees.

Why the choice matters

Most of the cost is operational rather than mysterious. Each subdomain usually needs its own Search Console property, so reporting fragments. Cookies do not cross a host boundary unless configured to, so a visitor who moves from the main site to a booking subdomain can be counted as a new session from a new source — this is exactly the problem cross-domain tracking exists to solve. Consent state, tag containers and A/B testing tools all need the same treatment.

There is an editorial cost too. Content on a subdomain tends to be written by a different team, linked to less often from the main navigation, and forgotten in internal linking plans. The structure quietly encourages the neglect.

Where the decision goes wrong

The most expensive mistake is moving an established section without mapping it properly. Every old address needs a permanent redirect to its exact new equivalent, not to a category page and certainly not to the homepage, and internal links should be rewritten to point at the destination rather than bouncing through the redirect. Treat it as a site migration, because that is what it is.

The second is splitting a small site for internal reasons — one team owns the blog, another owns the shop — and ending up with several thin properties instead of one credible one. The third is country subdomains created without the language and region markup to tie them together, so the versions compete with each other. And the fourth is choosing a subdomain because a platform seemed to demand it, when a reverse proxy could have served the same software under a folder.

How to act on it

Default to a subfolder and make the subdomain justify itself. A subdomain earns its place when the section genuinely runs on software you cannot merge into the main site, or when it serves an audience that should stay separate, such as a careers portal or a customer login area.

If you keep a subdomain, close the gaps deliberately: add it as its own property, configure tracking across the boundary, and link to it from the main navigation and from relevant pages as you would any important section. Where the structure is already tangled, an audit under technical SEO is the sensible first step before anything is moved.

Do and do not

Do

  • Default to a subfolder unless something forces a subdomain
  • Add each subdomain as its own Search Console property
  • Configure tracking across the boundary before launch

Do not

  • Split a small site across several thin subdomains
  • Move an established section without mapping every redirect
  • Assume analytics stitches subdomain sessions together automatically

Questions people ask about this

Is a subfolder better than a subdomain for SEO?

In most cases yes, and for practical reasons rather than magical ones. A subfolder shares the host, so internal links, crawl paths and the reputation the domain has built all sit in one place. A subdomain can perform perfectly well, but you are more likely to end up maintaining two half-strong properties instead of one strong one.

When is a subdomain the right choice?

When the section genuinely runs on software you cannot merge — a hosted help desk, a booking engine, a separate web application — or when it serves a distinct audience that should not influence the main site, such as a careers portal or a customer login. Regional sites are a judgement call, and folders are usually simpler to manage.

Should I move my blog from a subdomain to a subfolder?

Only if you will do the migration properly. Every old address needs a permanent redirect to its exact new equivalent, internal links should be rewritten rather than left to bounce, and you should expect a settling period before performance stabilises. If the blog attracts little traffic and few links, the effort may be better spent on the content itself.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.