Subdomains vs. Subfolders: An SEO Decision Guide

For a new blog, resource library, or product section that serves your main website’s audience, a subfolder is a sensible default. Choose a subdomain when a separate platform, publishing operation, or brand identity makes it easier to run that section.

That is a practical recommendation, not a Google ranking rule. Google explicitly states that it has no indexing or ranking preference between subfolders and subdomains and recommends choosing whichever is easier to organize and manage. Source: Google’s crawling and indexing FAQ

If your content already performs well, neither structure alone provides a compelling reason to move it. First identify what the change would improve for readers or your team.

What is the difference?

A subdomain adds a name before your main domain:

blog.example.com
support.example.com

A subfolder, also called a subdirectory, adds a path after the hostname:

example.com/blog/
example.com/support/

A subdomain creates a separate hostname. A subfolder organizes URLs within the same hostname. Neither choice, by itself, determines content quality, navigation, or how well the section meets a reader’s needs.

A quick decision table

The recommendations below are operational judgments, not predictions of higher rankings.

Situation	Practical starting point	Reason
A company blog serving the same customers as the main site	Subfolder	Keeps the publishing experience and navigation together
A resource library managed in your existing CMS	Subfolder	Avoids adding another publishing setup
A help center whose platform requires a separate hostname	Subdomain	Accommodates the platform’s requirements
A publication with a distinct identity and independent team	Consider a subdomain	Supports a more separate site experience
Language versions managed by one central team	Consider subfolders	Can simplify ongoing maintenance
An established section with no clear technical or reader problem	Keep the current structure	Avoids a URL migration without a defined benefit

The useful question is: Which structure can your team maintain well over time?

What Google’s guidance does—and does not—establish

Neither structure has a built-in ranking advantage

Google’s stated lack of preference supports using either structure. It does not guarantee identical results after a migration, particularly if you also change navigation, content, templates, or technical settings.

Avoid treating statements such as “subfolders automatically inherit all domain authority” or “subdomains always start from zero” as established Google rules. Neither conclusion follows from the cited guidance.

For planning purposes, focus on things you can inspect: useful content, accessible pages, relevant links, and reliable technical implementation.

Links still matter in either structure

Putting an article inside /blog/ does not automatically connect it to relevant product pages or related guides.

Google recommends that every page you care about receive a link from at least one other page on your site. It also recommends contextual links and descriptive anchor text to help readers and Google understand your pages. Source: Google’s link best practices

Whichever structure you choose:

Make the section accessible through appropriate navigation.
Connect related articles and useful commercial pages.
Use link text that describes the destination.
Avoid leaving valuable pages discoverable only through a sitemap.

Plan those connections around reader needs. FishingSEO’s guide to 7 Ways to Align AI Content With Search Journeys provides a complementary framework.

Some search features distinguish between the two

Google supports site names in search results at the domain and subdomain level, but not at the subdirectory level. A separately branded publication could therefore have a reason to consider a subdomain.

However, Google generates site names automatically. Providing a preferred name does not guarantee that Google will display it. This is a search appearance consideration, not evidence of a ranking advantage. Source: Google’s site name documentation

When a subfolder is the better practical fit

Start with a subfolder when the new content belongs naturally within the main website’s experience.

Typical signs include:

The content serves the same audience.
Readers regularly move between articles, services, and product pages.
One team manages publishing and technical maintenance.
Your existing platform can support the section without extensive custom work.

Hypothetical example: A fishing equipment retailer launches guides about choosing rods and maintaining reels. Those guides support the same readers as its product pages. An /advice/ section is a reasonable choice because the retailer can manage and connect the content within its existing site.

The reason for this recommendation is simpler operation and a coherent reader experience. It does not depend on an assumed subfolder ranking bonus.

When a subdomain makes sense

Consider a subdomain when separation solves a concrete problem.

Hypothetical example: A software company uses a documentation platform that supports docs.example.com but cannot reliably serve content at example.com/docs/. A subdomain may be the more maintainable choice.

Before committing, establish who will own:

Navigation between the main site and the section.
Publishing templates and content updates.
Crawl settings and indexing checks.
Measurement and technical troubleshooting.

A subdomain should have a named owner and a maintenance plan. Its convenience at launch is only one part of the decision.

Technical differences worth checking

Robots.txt rules are scoped to the host

The file at https://example.com/robots.txt does not control crawling on https://blog.example.com/. Each host’s robots.txt rules apply only to that host, protocol, and port.

For subfolders, rules belong in the host’s root robots.txt file. A file at /blog/robots.txt is not a valid replacement. Source: Google’s robots.txt specification

This matters when a separate platform launches with default crawl restrictions.

Search Console can report on either structure

You do not need a subdomain simply to measure a section separately.

A Search Console Domain property includes its subdomains and protocols. URL-prefix properties can isolate a particular subdomain or subfolder, such as https://blog.example.com/ or https://example.com/blog/. Source: Search Console property documentation

Choose reporting properties to match your analysis needs, rather than choosing your URL structure around reporting.

International sites can use either option

Google documents both subdomains and subdirectories as options for multilingual or multiregional sites. Its comparison identifies easier site separation as a subdomain benefit and lower maintenance on the same host as a subdirectory benefit. Source: Google’s international site guidance

For a centrally managed site, subfolders may be convenient. Separate regional operations may prefer subdomains. Either way, language and regional targeting require planning beyond choosing /de/ or de..

Should you move an existing subdomain into a subfolder?

Only when the expected benefit justifies the migration work.

Write down the problem first. Examples include fragmented navigation, duplicate publishing work, or a platform that prevents essential improvements. Then assess whether those problems can be fixed without changing URLs.

Treat migration success stories cautiously. A before-and-after traffic increase cannot, on its own, isolate the effect of the URL structure. Content changes, new links, seasonality, and other site changes may also affect the result.

If you proceed, Google’s migration guidance recommends these core steps:

Map old URLs to their relevant new destinations.
Use permanent server-side redirects, such as 301 or 308.
Update internal links, canonical URLs, sitemaps, and applicable hreflang annotations.
Remove development-only crawl blocks and noindex rules from pages intended for search.
Test redirects and monitor both old and new URLs.
Keep redirects for at least one year, and preferably longer.

Avoid redirecting unrelated pages to the homepage. Google also recommends separating major changes and warns that rankings may fluctuate during a move. Source: Google’s site migration guide

Before launch, record a baseline for organic clicks, impressions, landing-page conversions, and indexing. After launch, compare the combined performance of the old and new locations. A decline at the old address is not enough to establish a loss if the replacement URLs are gaining traffic.

References

The main primary sources behind this guide are:

Conclusion

Use subfolders as a practical starting point for closely related content within one website. Use subdomains when separation makes the section easier to operate. For existing content, require a clear benefit before changing URLs: Google’s documented guidance supports either structure, and the implementation matters more than a presumed preference.