Subdomain vs Subfolder: Which Is Better for SEO?

A subfolder puts a section on your main host — example.com/blog. A subdomain puts it on a separate host — blog.example.com. Both can rank. But a subfolder shares everything your main site has already earned and needs no extra setup, while a subdomain is treated as a separate site in several places. For content meant to support your main site, choose the subfolder.

What is the difference between a subdomain and a subfolder?

It's a difference in hosts. A subfolder is a path on the same host as your homepage; a subdomain is a different hostname that happens to share your registered domain.

Google's own comparison for multi-regional sites summarizes the trade-off in the same terms: subdirectories are easy to set up with low maintenance on the same host, while subdomains allow different server locations and easy separation of sites (Google).

Does Google treat subdomains as separate sites?

In several documented ways, yes. For site names, Google defines a site by its domain or subdomain and doesn't support site names at the subdirectory level; its favicon guidelines draw the same line. Robots.txt rules apply per host, so blog.example.com needs its own file (Google's robots.txt spec).

Search Console reflects this too: a URL-prefix property covers one host, while a Domain property is the way to see a domain and all its subdomains together.

None of that is a penalty. It means a subdomain starts closer to being its own site: its pages don't automatically sit inside your main site's structure, and you have to link, configure and measure it separately. A subfolder gets all of that for free.

Does a subdomain inherit the main domain's strength?

Not automatically in the way a subfolder does, and Google doesn't publish a formula either way. What you can rely on is structure: a subfolder page is linked from your main navigation, appears in your main sitemap and gets internal links from pages that already rank. A subdomain only gets those benefits if you deliberately build them — prominent links from the main site, its own sitemap, consistent branding.

That's why "subdomains can rank just as well" and "subfolders usually win in practice" are both true. A well-supported subdomain can do fine; a neglected one, linked only from a footer, usually struggles because nothing tells crawlers it matters.

Where do real companies put their blog and docs?

Overwhelmingly, blogs live in subfolders. On October 24, 2026 we analyzed the homepages of 391 well-known sites and looked at where their blog links pointed (dataset). Of the 223 homepages that linked to a blog or resources section:

Documentation is the opposite story. Of the 218 homepages that linked to docs, help or developer content, 48.6% used only a subdomain and 24.8% only a subfolder, with the rest using both.

That split is telling. Companies keep marketing content — which exists to win search traffic for the main brand — on the main host. Docs often run on a separate platform, have a different audience and a different release process, so a subdomain is the pragmatic choice there.

When is a subfolder the right call?

When the section exists to support the main site. That covers most of what marketing teams publish:

• Blogs, guides and resources that should build the main site's topical authority.
• Landing pages and comparison pages that sit close to your product pages.
• Country or language versions when one team runs one platform.

A subfolder also keeps reporting simple: one analytics property, one Search Console property, one robots.txt, one sitemap index.

When is a subdomain the right call?

When the section is genuinely separate — technically or in audience:

• A web app (app.example.com) that shouldn't share cookies, caching or deploys with marketing pages.
• Documentation or a help center on a dedicated platform.
• Community, status or developer portals run by different tools or teams.
• Country sites that need separate servers or legal entities.

If you choose a subdomain for content you want to rank, treat it as a site in its own right: link to it prominently from the main site, give it its own sitemap and robots.txt, and add it to a Domain property in Search Console.

What about international sites?

The same trade-off, with a third option. Google's comparison for multi-regional sites lists three structures (Google):

Whichever you choose, connect the versions with hreflang annotations so Google shows each visitor the right language. For most companies with one platform and one team, subdirectories are the least work to run well.

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

Usually yes, if it's meant to support the main site and your platform can serve it under a path. Hosting platforms and reverse proxies can serve a separate blog system at /blog without changing the CMS.

Treat it as a migration. Google's guide to site moves with URL changes applies:

1. Map every old URL to its new path, one to one.
2. Set up 301 redirects from each old URL to its new one, in a single hop.
3. Update internal links, canonicals and the sitemap to the new URLs.
4. Keep the redirects in place for as long as possible, generally at least a year.
5. Watch indexing in Search Console for both hosts until the old one drains.

Expect a period of fluctuation while Google recrawls — and verify the redirects with the redirect checker before you call it done.

What are the most common mistakes?

Four come up again and again in audits:

1. The same content on both. A blog reachable at blog.example.com and example.com/blog splits signals between duplicates. Pick one and 301 the other. Among the homepages in our sample that linked to a blog, 4.9% linked to both a blog subdomain and a blog subfolder.
2. A hosted blog nobody links to. A third-party blogging platform on a subdomain, linked only from the footer, gives crawlers little reason to treat it as important.
3. Missing basics on the subdomain. No robots.txt, no sitemap, no Search Console property, so problems go unnoticed for months.
4. Indexed staging subdomains. staging. and dev. copies of the site leak into search unless they're behind a login or carry noindex.

What should I check after choosing?

Whichever structure you use, run these checks on the section:

1. robots.txt — a subdomain needs its own; test paths with the robots.txt tester.
2. Sitemap — list the section's URLs and reference the sitemap from robots.txt; validate it with the sitemap checker.
3. Internal links — link the section from your main navigation and from relevant pages, not just the footer.
4. Favicon and site name — a subdomain can show its own; make sure that's what you want with the favicon checker.

Our position is deliberately boring: the best structure is the one your team can run cleanly for years. For most companies' content, that's a subfolder.