Subdirectory vs Subdomain

SEO

Also: Subfolder vs Subdomain · Folder vs Subdomain

The choiceyoursite.com/blog vs blog.yoursite.com
SEO consensusSubdirectories usually consolidate authority better
Watch forSubdomains can be treated as separate sites
When subdomains winDifferent tech stack or team ownership

Quick definition

A subdirectory is a folder within your main website, like yoursite.com/blog. A subdomain is a separate section that sits in front of your domain, like blog.yoursite.com. Both organise content, but search engines sometimes treat them very differently for ranking purposes.

How it varies across Australia

Australian businesses migrating a subdomain blog into a subdirectory typically see organic traffic move upward over following months as authority consolidates. The size of the gain varies by how much content and backlink equity the subdomain had built up separately.

See technical SEO patterns across Australian industries

The two structures

Subdirectory

A folder path under your root domain. Shares the domain's authority, cookies and technical setup by default.

yoursite.com/blog
Subdomain

A distinct host under your domain. Google can crawl and rank it as a related but separate entity.

blog.yoursite.com

What it actually means

Picture your website as a house. A subdirectory is a room inside that house, like yoursite.com/blog. Walk through the front door and you're already there. A subdomain is more like a granny flat out the back, technically on the same property but with its own entrance, like blog.yoursite.com. Visitors barely notice the difference. Search engines sometimes do.

Historically, Google has said it treats subdomains and subdirectories the same for ranking. In practice, many site migrations tell a different story. When businesses move a blog from a subdomain into a subdirectory, organic traffic often climbs because the content now shares the root domain's backlink profile and domain authority directly, rather than needing to build its own separate signal.

This matters most for content marketing and technical SEO decisions. A help centre, blog or resource hub sitting on a subdomain is effectively asking Google to evaluate it as its own site. If that subdomain has thin content or few backlinks, it can underperform compared to the same content living inside the main domain's site architecture.

The decision isn't purely technical. Team ownership, platform limitations and crawl budget all play into it too.

A subdomain is a separate house on the same street. A subdirectory is a room in your house. Google treats them differently even when your visitors don't notice at all.

How it shows up

It shows up in Search Console as two separate properties needing verification and tracking rather than one unified view. It shows up in backlink audits where valuable links point to a subdomain that isn't consolidating authority with the main site. It shows up when marketing launches a content hub on help.yoursite.com and wonders months later why it isn't ranking the way the main site does for comparable topics.

The Australian context

Australian businesses running .com.au domains alongside global .com properties often layer subdomain decisions on top of an already fragmented domain structure. A common pattern is a support subdomain built on a third-party platform (Zendesk, Intercom) that can't easily live inside the main site architecture. That's a legitimate technical constraint, not a strategic choice, and it should be reviewed periodically as platforms add subdirectory-mapping options.

Where people get this wrong

Assuming Google always treats subdomains identically to subdirectories.Official guidance says they're treated the same, but Google's crawlers and ranking systems have shown inconsistent behaviour across many real migrations. Test with your own data rather than relying purely on the stated policy.
Choosing a subdomain purely for technical convenience.A separate CMS or hosting environment often defaults to a subdomain because it's easier to set up. That convenience can cost organic visibility that's expensive to earn back later.
Migrating without proper redirects and canonical tags.Moving content between a subdomain and subdirectory without careful 301 redirects and canonical tag cleanup can cause temporary or permanent ranking loss on top of the intended consolidation gain.

Related terms

Common questions

Should I put my blog on a subdirectory or a subdomain?

Subdirectory in almost every case. It shares your root domain's authority and backlink profile directly, which usually helps content rank faster than the same content on a separate subdomain.

Does Google really rank subdomains separately from the main site?

Google states it treats them the same, but real-world migrations frequently show traffic gains when content moves from a subdomain into a subdirectory. Treat the official guidance as a starting point, not a guarantee.

Why do platforms like help desks default to subdomains?

Third-party software often can't integrate directly into your main site's folder structure, so a subdomain is the easiest technical setup for the vendor. It's a convenience decision, not an SEO recommendation.

Is it worth migrating an existing subdomain into a subdirectory?

Usually yes if the subdomain holds meaningful content and backlinks, but the migration needs careful 301 redirects and canonical tag handling. Poorly executed migrations can lose ranking rather than gain it.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →