Subdomain vs Subdirectory for SEO in 2026: What 2,000 Top Sites Do

I have moved more than a few blogs off subdomains during site audits. The question behind each move was always the same: does Google care whether it is blog.yoursite.com or yoursite.com/blog?

Google says it does not. Most SEOs say it does. Both sides keep quoting the same three case studies from 2014 and 2015.

So this time I did two things. I went back and read those case studies properly, and I checked where the top 2,000 sites on the web actually keep their blog. The short answer: for anything you want to rank, use a subdirectory. The longer answer has a few surprises.

What is the difference between a subdomain and a subdirectory?

A subdomain sits in front of your domain name: blog.yoursite.com, shop.yoursite.com. Technically it is its own host. It can run on a different server, a different platform, even be managed by a different team.

A subdirectory, also called a subfolder, is a folder after the domain: yoursite.com/blog. It is simply part of yoursite.com.

The same article can live at either address and look identical to a reader. The difference is in how search engines connect it to the rest of your site.

A page in a subdirectory is clearly part of your site. A page on a subdomain might be treated as part of your site, or as a separate one. That "might" is the whole debate.

What does Google actually say about subdomains and subdirectories?

Google's best-known answer came from John Mueller in 2018. He said, "In general, we see these the same. I would personally try to keep things together as much as possible."

Read the second sentence again. Even the "it does not matter" quote ends with advice to keep things together.

The more useful update came in November 2024, and almost nobody in this debate mentions it. In a post about site reputation abuse, Google wrote that it has systems to understand if a section of a site is "independent or starkly different from the main content of the site," and treats those areas "as if they are standalone sites."

That changes the question. Google is not really judging the URL shape. It is judging whether a section belongs to the site.

• A subdirectory full of off-topic content can lose the main site's signals.
• A subdomain that is clearly part of the site can keep them.
• Moving risky content between a folder and a subdomain does not fix anything. Google's spam policies name that exact move as circumvention.

So the URL is not magic. It is a strong hint about whether a section belongs.

Where do the top 2,000 sites keep their blog?

Opinions are cheap, so I checked what big sites actually do.

I took the top 2,000 domains from the Tranco list (the research-grade ranking of popular sites) dated 28 September 2026. For each one, I requested site.com/blog and blog.site.com with a normal desktop browser, followed every redirect, and recorded where the blog finally lived.

I only counted a blog if the page loaded and called itself a blog or newsroom in its title. I also threw out login pages and sites that answer every made-up URL with the same page. That left 348 confirmed blogs.

Overall, 62% of blogs sit in a subdirectory, 23% on a subdomain, and 16% on a separate domain.

The pattern by rank is the interesting part. Among the top 100, subdomains lead: blog.cloudflare.com, blog.adobe.com, blog.mozilla.org. Some go further with a separate domain, like blog.google and github.blog. From rank 101 down, folders lead, and they reach 70% in the 1,001 to 2,000 band.

Which way are big sites moving their blogs?

The redirects told me more than the final addresses did.

80 sites still own a blog. subdomain but 301 it into a folder. That is the footprint of a completed move. When I checked by hand:

Only 15 sites go the other way, sending /blog out to a subdomain. HubSpot, Cloudflare, Dropbox, Yelp and TED are in that group.

My read: the very biggest brands can afford a subdomain, because their name carries every URL they publish. Almost everyone below that level has consolidated into a folder, and many of them clearly did it on purpose.

One honest limit. This census shows what sites do, not what ranks better. But it is what hundreds of teams chose after living with both, and 80 to 15 is not a close vote.

What do the famous case studies really show?

Almost every article on this topic leans on the same three stories. I went back to the originals.

Pink Cake Box (2015). The shop moved its blog from blog.pinkcakebox.com to /blog, and organic traffic rose about 40%. A detail most retellings skip: Bing and Yahoo traffic fell 16% in the same period. Still, a clean result.

iwantmyname (2014). This is the famous "47% drop" after moving a blog to a subdomain. The original URL now just redirects to their homepage, so I read the archived copy. Three things stood out:

• The chart shows total blog pageviews, not organic traffic, falling from around 13,000 a month to about 7,000.
• The slide had started in June, before the July switch.
• The new subdomain ran on GitHub Pages without HTTPS, just as Google launched HTTPS as a ranking signal. The authors raised this themselves.

They moved the blog back after six months. The post never reports a recovery.

Moz. Moving the Beginner's Guide from guides.moz.com onto the main domain made rankings rise "dramatically", according to Rand Fishkin. It is a strong quote, but there is no published data behind it.

So these are three old, small, messy examples. They point the same way as my census, which is why I still default to a folder. But none of them is proof, and anyone who calls them proof has not read them.

Can a subdomain still rank well?

Yes, and it is worth saying clearly.

Look at the US results for "subdomain vs subdirectory" itself. Two of the top-10 pages arguing for subdirectories live on blog subdomains: Cloudflare's guide on blog.cloudflare.com and HubSpot's on blog.hubspot.com.

I see the same on this site. TheGuideX runs its deal pages on subdomains, like kadencewp.theguidex.com. In the last 90 days of my Search Console data, five of those 13 pages averaged a top-10 position, between 4.7 and 9.6.

Two caveats keep me honest. Those are low-competition branded queries, not head terms. And those pages are clearly tied to the main site by links, bylines and topic.

A subdomain is not a penalty. It starts with fewer shared signals. A huge brand barely feels that. A small or mid-sized site feels it a lot.

Why does a subdirectory usually win?

It comes down to what a new page can borrow on day one.

Search engines build trust in a site mostly from the links pointing at it. A page in /blog sits inside that site from the moment it is published. A page on blog. may get the same treatment, or may be judged more on its own.

There are plain practical wins too:

• Internal linking is simpler. Every guide can link to every service page without crossing a host boundary.
• One sitemap, one analytics setup, one Search Console view. Nothing gets forgotten on a second host.
• Links earned by the blog help the whole domain. That is often the business reason for having a blog at all.

When the low-risk option also keeps winning in practice, I do not need a lab test to pick it. This is one of the most common fixes I flag in a technical SEO audit.

When is a subdomain the right call?

Subdomains are the right tool for a genuine separation. They are the wrong default for a blog.

Apps belong on a subdomain. They are not meant to rank, and you do not want thousands of logged-in URLs in your search index.

Third-party tools are another fair reason. Many help desk and documentation platforms only host on their own subdomain, and that trade-off is usually fine.

What you should not do is put the blog on a subdomain just because a developer set it up that way. No SEO reason, just a default, and it is easy to reverse.

Can a blog on another platform still live in a subdirectory?

Yes. This is the part most guides skip, and it removes the most common reason for a blog subdomain.

The usual story goes: "Our site is on Shopify or a custom app, the blog is on WordPress, so it has to be blog." It does not. A reverse proxy lets your main server fetch the blog from wherever it runs and show it under /blog.

That is exactly how iwantmyname moved back. Their blog stayed on GitHub Pages, and an Nginx rule served it at /blog/. Here is the same idea, for a blog host that serves its posts under /blog/:

location = /blog { return 301 /blog/; }

location ^~ /blog/ {
    proxy_pass https://your-blog-host.example.com;
    proxy_set_header Host your-blog-host.example.com;
}

If your site sits behind Cloudflare, a Worker can do the same job without touching the server. Cloudflare explains the approach in its own subdomains vs subdirectories guide.

Two things to get right. Set the blog's canonical URLs to the /blog addresses. Then stop the original blog host from being indexed on its own, or you will have two copies competing.

Subdomain vs subdirectory for a multilingual site

This is the case people get stuck on. There are three real options.

• Subdirectory, example.com/de/: all authority stays on one domain, and it is the easiest to run.
• Subdomain, de.example.com: cleaner separation per language, but each builds authority more on its own.
• Country domain (ccTLD), example.de: the strongest country signal, but the most work and the most split authority.

Google says any of these can work. The ranking data leans one way, though. In SE Ranking's 2024 study of 20,000 e-commerce keywords across 15 markets, subdomains made up only about 3% of the structures in the results.

For most businesses I default to subdirectories. Country domains make sense only when you run genuinely separate operations in that country: different prices, stock or legal terms.

Whichever you pick, hreflang matters more than the URL shape. It tells Google which language version to show to whom. You can check yours with my free hreflang checker, and my international SEO guide covers the full setup.

How do you move a blog from a subdomain to a subdirectory?

If your blog is on a subdomain and underperforming, moving it is usually worth it. Just do it in one clean pass.

1. Map every URL first. Export all blog URLs from your sitemap and write the new /blog/ address next to each one.
2. Publish the content at the new URLs. Keep the slugs the same where you can.
3. Add a 301 redirect for every old URL to its exact new URL. No blanket redirects to the homepage. My guide to redirecting a WordPress page covers the plugin and server options.
4. Check the status codes yourself. Run curl -I https://blog.yoursite.com/some-post/ and confirm a 301 pointing at the new URL. When I checked, even blog.slack.com answered with a 302, a temporary redirect. For a permanent move, use 301.
5. Update internal links so they point straight at the new URLs, not through the redirect.
6. Submit the updated sitemap in Search Console. A domain property covers both hosts, so you can watch the old URLs drop and the new ones rise in one place.
7. Keep the redirects forever. Old links out on the web will keep sending visitors for years.

Expect a wobble of a few weeks while Google reprocesses the move. Most drops that last longer trace back to missed or wrong redirects, and those are fixable.

What are the common mistakes?

• A blog on a subdomain for no reason. The easiest win on this list.
• A country domain per language with no team to run them. You end up with several weak sites instead of one strong one.
• Migrating without one-to-one redirects. The new structure was right. The move threw the equity away.
• Using a folder or subdomain to hide off-topic content. Since 2024, Google judges whether a section belongs, not where it sits.
• Treating the URL as the whole job. A subdirectory gives good content a better start. It does not write the good content for you.

Final take

Google is right that a subdomain can rank. Cloudflare and HubSpot prove it for this very search term, and a few of my own subdomain pages rank too.

But the web has voted. In my census, 62% of the top sites' blogs live in a folder, and 80 sites moved a blog subdomain into one against 15 going the other way.

So unless you have a real technical reason, keep your blog, guides and language versions in subdirectories. If the blog must run elsewhere, proxy it under /blog. And if it is already on a subdomain and not pulling its weight, a clean move with one-to-one 301s is one of the better-return fixes in technical SEO.