Subdomain vs Subdirectory: Which Is Better for SEO in 2026?

You are deciding where to put a section of your site: the blog, a help centre, a store, or a second language. It comes down to two URL shapes.

A subdomain sits in front of your domain: blog.yourdomain.com. A subdirectory, also called a subfolder, is a folder after it: yourdomain.com/blog.

Google says the choice does not matter.

The companies that have actually tested it disagree. Sometimes by 40%.

I have made this call on real audits, and the answer is simple. For anything you want to rank, use a subdirectory. Here is the data behind that, and the handful of cases where a subdomain really is the right call.

What is the difference between a subdomain and a subdirectory?

A subdomain is treated as a distinct site that happens to share your root domain. It can run on a different server, a different platform, even a different team. blog.yourdomain.com and shop.yourdomain.com are examples.

A subdirectory is just a folder on the same site. yourdomain.com/blog is part of yourdomain.com, full stop.

Here is where each piece sits in a URL.

That "distinct site" versus "same site" difference is the whole debate. Everything below follows from it.

Real subdomain and subdirectory examples

It is easier to see the choice in real sites. Big brands use both, and the pattern is consistent: separate systems go on subdomains, rank-worthy content goes in subdirectories.

Notice the logic. Disney puts its store on a subdomain because it is a different platform, but content meant to pull search traffic almost always lives in a folder on the main domain. Moz is the textbook case, it moved its guide off a subdomain and onto moz.com and saw rankings rise.

Does it matter for SEO?

You will find two camps here, so let me give you both honestly.

Google's official position is that it does not matter. John Mueller has said subdomains and subdirectories are essentially equivalent, and that you should use whichever is easier to manage. Google's own multi-regional guidance says the same: keep related content together, pick what you can maintain.

Some respected voices take that at face value. Ahrefs argues the supposed subdirectory advantage is overstated and that Google genuinely handles both well.

But the people who have actually run the experiment keep getting a different result.

That is the part the "it does not matter" camp always skips. So let me put the numbers on the table.

What the data actually shows

These are documented migrations, not opinions. They are why most SEOs still default to subdirectories.

• PinkCakeBox reported roughly a 40% increase in organic traffic after moving its blog from a subdomain into a subdirectory.
• iwantmyname went the other way and saw a 47% drop in organic traffic after moving its blog to a subdomain, then recovered after moving it back.
• Moz moved its Beginner's Guide to SEO off guides.moz.com onto the main domain, and rankings rose with no other change.
• HotPads and World First both reported organic growth after consolidating onto a subdirectory.

Search Engine Journal's roundup and SE Ranking's research reach the same conclusion: subdirectories tend to win.

Two honest caveats. First, these are correlations, not a lab, since a migration changes more than the URL. Second, plenty of huge sites rank fine on subdomains, so it is not a hard rule.

But when the easy, low-risk option is also the one that keeps winning, the choice makes itself.

Why a subdirectory usually wins

The mechanism is simple once you see it.

Search engines build trust in a domain, largely from the links pointing at it. A strong domain lifts the pages inside it.

A subdirectory inherits that trust from day one. A subdomain has to go and earn its own.

There is a practical side too. With everything on one domain, your internal linking is tighter. Every related page can link to every other without crossing a boundary, and that stronger link graph is part of why subdirectories perform.

In other words, a subdirectory does not just avoid a penalty. It starts every new page a few steps ahead.

So which should you use?

For most content you want to rank, the answer is a subdirectory. Almost every time.

The rule of thumb: if it is content you want Google to rank as part of your brand, keep it in a subdirectory. If it is a genuinely separate system, a subdomain is fine, and big brands use them this way, shop.disney.com, support.google.com, events.microsoft.com.

This is one of the most common fixes I flag in a technical SEO audit, a blog quietly sitting on a subdomain for no real reason.

Subdomain vs subdirectory for a multilingual site

This is the case people get stuck on, so here are the three real options.

• Subdirectory: example.com/de/. All authority stays on one domain, and it is the easiest to run.
• Subdomain: de.example.com. A clearer separation per language, but each builds authority more on its own.
• ccTLD: example.de. The strongest signal that you target a country, but the most work and the most split authority.

Google says any of these can work. For most businesses I default to the subdirectory: one domain, one pool of authority, the simplest path.

Reach for ccTLDs only when targeting a specific country really matters and you have genuinely separate operations there, different pricing, stock, or legal terms. They send the clearest local signal, but you are running several sites.

Whichever you choose, set up hreflang. It tells Google which language and region each page is for, so the right localized version shows to each user. Get it wrong and you get the classic mess: the German page ranking for English searchers, or two versions competing. The URL structure matters less than this part being correct.

The full country-and-language setup, structures, hreflang and the usual mistakes, is what my international SEO guide covers, so read that before you commit to one.

When a subdomain is the right call

Subdomains are not the enemy. They are the right tool for a real separation, and the wrong one for a blog.

Use one when the section runs on different software, like a Shopify store in front of a WordPress site, or an app at app.yourdomain.com. Apps especially belong on a subdomain: they are not meant to rank, and you do not want their URLs in your search index.

Use one when a third-party tool requires it. Many help-centre and documentation platforms host on their own subdomain by design, and that trade-off is usually fine.

And use one for things you want out of your main index entirely, like a staging environment, or a section you deliberately want kept apart from your main brand for legal or operational reasons.

What you should not do is put your blog on a subdomain by default, then wonder why it struggles.

How to move a subdomain to a subdirectory

If your blog is already on a subdomain and underperforming, moving it is worth doing, but do it carefully. A sloppy migration loses rankings.

1. Recreate the content under the subdirectory (yourdomain.com/blog).
2. 301 redirect every old subdomain URL to its exact new URL, one to one. No lazy redirects to the homepage.
3. Update internal links to point at the new URLs directly, not through the redirect.
4. Update your sitemap and resubmit it in Search Console.
5. Keep the redirects in place permanently.

Do it in one clean pass, not in stages. Expect a short dip while Google reprocesses, usually a few weeks, then recovery, and often a lift like the case studies above.

Most ranking drops after a move like this trace back to redirects that were skipped or pointed at the wrong place. That is a technical SEO problem, not a content one, and it is avoidable.

Common mistakes

• Blog on a subdomain because the developer set it up that way. No SEO reason, just a default, and an easy win to reverse.
• A ccTLD per language without the resources to maintain them. You end up with several weak sites instead of one strong one.
• Migrating without redirects. The structure was right; the execution lost the equity.
• Treating the URL as the whole job. A subdirectory does not rank by itself. It gives good content a better start. You still have to write the good content.

Final take

Google says subdomains and subdirectories are equal, and it means it. The results on real sites, a 40% jump one way and a 47% drop the other, still lean clearly toward subdirectories.

So unless you have a real technical reason to separate a section, keep your content, your blog and your language versions in subdirectories. It is the simpler choice and the lower-risk one.

And if a section is already on a subdomain and not pulling its weight, moving it to a subdirectory with clean 301s is one of the higher-return fixes in technical SEO.