Few technical SEO questions start as many arguments as this one: should your blog, shop or help centre live on a subdomain like blog.example.com, or in a subfolder like example.com/blog/? Developers often prefer subdomains because they are easier to host separately. SEOs often push for subfolders because they keep everything under one roof.
The honest answer is that Google can rank both, and the "right" choice depends on what the section is, who runs it and how it is hosted. But the two structures do behave differently in Search Console, in site names, in internal linking and in how easily authority is shared.
This guide explains what each option is, what Google's documentation actually says, the practical pros and cons, a decision framework, and a safe process for moving content between them in 2026.
Key Takeaways
- A subdomain is a prefix to your domain (
shop.example.com); a subfolder is a path within it (example.com/shop/). - Google has said it is fine with either structure; neither is a ranking factor by itself.
- Subfolders make it simpler to share internal links, topical relevance and reporting with the main site.
- Subdomains make sense for genuinely separate products, apps, regions, platforms or audiences.
- Google treats a subdomain-to-subdomain move like a domain change, so plan redirects carefully.
Subdomain vs Subfolder: The Basics
Take the URL https://blog.example.com/seo-tips/. The root domain is example.com, blog is the subdomain, and /seo-tips/ is the path. Even www is technically a subdomain. In https://www.example.com/blog/seo-tips/, the subfolder (also called a subdirectory) is /blog/.
| Factor | Subdomain | Subfolder |
|---|---|---|
| Example | blog.example.com | example.com/blog/ |
| Hosting | Can run on a separate server, platform or CMS | Usually same server, or a reverse proxy |
| Search Console | Covered by a Domain property; needs its own URL-prefix property | Included in the main site's URL-prefix property |
| Site name in Google results | Can have its own site name | Uses the domain's site name |
| Internal linking | Often weaker cross-linking in practice | Shares navigation and links naturally |
| Analytics and cookies | Needs cross-subdomain configuration | Works out of the box |
| Setup effort | Simple DNS change | May need proxy or CMS integration |
What Google Actually Says
Google's public position, repeated by its Search Advocate John Mueller over the years, is that its web search is fine with either subdomains or subdirectories, a statement Semrush cites in its subdomain vs subdirectory guide. Google's own documentation never names one structure as a ranking advantage. What the documentation does show is that Google handles the two differently in specific places.
Site names
Google's site names documentation treats subdomains as separate sites for naming purposes:
“Currently, Google Search only supports one site name per site, where a site is defined by the domain or subdomain.”
— Google Search Central, Provide a site name to Google Search
“Google Search does not support site names at the subdirectory level.”
— Google Search Central, Provide a site name to Google Search
So help.example.com can appear in results with its own name, while example.com/help/ always appears under the main site name. That can be a reason to choose a subdomain for a distinct brand, or a subfolder if you want everything to look like one site.
Search Console
According to Search Console Help, a Domain property "aggregates data for all subdomains, protocols, and subpaths of the property", while a URL-prefix property excludes other subdomains. If you use subdomains, set up a Domain property for the full picture and individual URL-prefix properties for each subdomain.
International sites
For multi-regional sites, Google's guide to managing multi-regional sites lists both subdomains and subdirectories as valid structures. Subdomains are easy to set up and allow different server locations; subdirectories are low maintenance because they share one host. URL parameters for country versions are explicitly not recommended. Our international SEO guide and hreflang tutorial go deeper.
Spam policies
Google's spam policies mention both structures in one context: using existing or new subdomains or subdirectories to keep violating its policies counts as policy circumvention. Under the site reputation abuse policy, hosting third-party content on a section of a strong domain to exploit its ranking signals is a risk no matter which structure you choose.
Why Many SEOs Still Prefer Subfolders
Even if Google can rank both, subfolders usually win on practicality for content that supports the main business:
- One site to grow. Content, links and engagement all build up around one hostname, which makes topical authority easier to demonstrate.
- Simpler internal linking. Shared navigation, breadcrumbs and contextual links connect the blog to service pages. See our internal linking guide.
- Cleaner analytics. No cross-domain tracking, no split cookies and one property.
- Fewer technical moving parts. One sitemap set, one robots.txt and one certificate to manage.
Subdomains also have legitimate strengths. They isolate risk (a broken forum will not take down the main site), they suit different platforms (a Shopify store beside a WordPress site), and they let very large sites spread infrastructure across separate hosts. Our article on how Googlebot works explains how server health shapes crawling.
When to Use Each
| Use case | Recommended | Why |
|---|---|---|
| Company blog or resource hub | Subfolder | Supports the main site's topics and services directly |
| Product or category pages for an ecommerce store | Subfolder | Keeps the store and content on one site for store SEO |
| Web app, login area or customer portal | Subdomain | Usually not meant to rank; separate infrastructure |
| Help centre on a third-party platform | Either | Subdomain is easier; reverse proxy to a subfolder if search traffic matters |
| Country or language versions | Either (or ccTLDs) | Both are valid per Google; pick what you can maintain |
| A distinct brand or audience | Subdomain or separate domain | Can carry its own site name and identity |
| Careers, status or developer docs | Subdomain | Often different teams and tools |
How to Decide: A Step-by-Step Framework
- Define the section's purpose. Is it meant to attract search traffic that supports your core business, or is it a tool or app?
- Check the platform. If it must run on separate software, ask whether a reverse proxy can serve it at a subfolder. Decoupled stacks are covered in our headless CMS SEO guide.
- Consider the audience and brand. Does it need its own identity and site name in search results?
- Estimate maintenance. Who will manage redirects, sitemaps, tracking and linking for each option?
- Map internal links. Plan how the section will link to and from your main pages using our site architecture guide.
- Decide, document and stick with it. Switching later means a migration, so choose for the long term.
Moving From a Subdomain to a Subfolder
Many businesses consolidate an old blog. subdomain into /blog/. Google's site move documentation treats moves between hostnames as URL changes, so the usual migration rules apply:
- Crawl the subdomain and export every URL that has traffic, links or rankings.
- Build a one-to-one redirect map to the new subfolder URLs.
- Recreate content, titles, structured data and internal links on the new paths.
- Implement permanent 301 redirects and avoid redirect chains.
- Update internal links, canonical tags and XML sitemaps to the new URLs.
- Keep the redirects in place long-term and monitor indexing in Search Console.
Expect some fluctuation for a few weeks. Our website migration SEO guide has a fuller checklist.
Common Mistakes
- Moving for the sake of moving. A healthy subdomain with good traffic is rarely worth a risky migration on structure alone.
- Orphaned subdomains. A blog subdomain with no links from the main navigation gets little internal support.
- Duplicate copies. Leaving the same content live on both the subdomain and subfolder without redirects or canonicals.
- Forgetting Search Console. Not verifying a Domain property, so subdomain errors go unnoticed.
- Renting out a subfolder. Publishing unrelated third-party content to borrow your domain's strength risks site reputation abuse issues.
- Using URL parameters for country versions. Google advises against it; see our guide to URL parameters and SEO.
Related Guides
- URL Parameters and SEO: How to Handle Them
- Soft 404 Errors: What They Are and How to Fix Them
- How Googlebot Works: Crawling Explained
Frequently Asked Questions
Is a subfolder better than a subdomain for SEO?
Google says it handles both. In practice, subfolders are often easier for content that supports the main site because links, reporting and topical relevance stay on one hostname.
Do subdomains inherit authority from the main domain?
Google has not published a rule on this. Subdomains can rank well, but they usually need their own internal links and external signals, while subfolder content benefits from the main site's structure automatically.
Should my blog be on a subdomain?
Usually not, unless it runs on a separate platform you cannot proxy or targets a different audience. For most businesses, example.com/blog/ is simpler to manage and link.
Does a subdomain have its own site name in Google?
Yes, it can. Google supports site names at the domain and subdomain level, but not for subdirectories.
How do I move a subdomain to a subfolder?
Map every old URL to a new one, add 301 redirects, update internal links, canonicals and sitemaps, then monitor indexing and traffic in Search Console.
Conclusion
Subdomain vs subfolder is less about a secret ranking bonus and more about structure, ownership and maintenance. If a section exists to win search traffic for your main business, a subfolder is usually the simplest path. If it is a separate product, platform or brand, a subdomain is perfectly valid. Decide once, link it properly and monitor it in Search Console.
Planning a restructure or consolidating subdomains? Our technical SEO team can map redirects and protect your traffic. Get a free quote.
References
- Google Search Central: Provide a site name to Google Search
- Search Console Help: Add a website property
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Site moves with URL changes
- Google Search Central: Spam policies for Google web search
- Semrush: Subdomain vs. Subdirectory: What They Are & Which Is Better for SEO
