Subdomain vs Subfolder for B2B SaaS Docs and Blog

The subdomain vs subfolder decision for B2B SaaS docs and blog is one of the most consequential architectural choices a marketing team makes. It is also one of the most commonly made wrongly. blog.yoursaas.com versus yoursaas.com/blog. docs.yoursaas.com versus yoursaas.com/docs. The wrong choice can cost you 20 to 40 percent of the SEO benefit you would otherwise get from the content on those surfaces. The right choice compounds over years.

This is the framework. The standard advice (subfolder wins) and why it is mostly right. The specific authority transfer math. The edge cases where subdomain might be better. The docs question (more nuanced than blog). The migration path if you are currently on the wrong side of this decision.

01The standard advice

Subfolder wins for blogs. This is consensus. It has been since at least 2017.

The mechanism: search engines treat subdomains as separate sites in subtle but meaningful ways. Authority does not flow seamlessly between a subdomain and its parent domain. Backlinks earned by your subdomain blog accumulate on the subdomain's authority pool, not on your marketing site's authority pool. The marketing site's authority is partially walled off from the blog content's ranking potential, and vice versa.

A subfolder blog (yoursaas.com/blog) inherits the marketing site's authority directly. Backlinks earned by blog posts accumulate on the same authority pool as the homepage, the product pages, the comparison pages. Every link earned by every page lifts every other page.

The accumulated effect over 18 to 36 months is significant. Sites that started with subfolder blogs typically have 20 to 40 percent more total ranking power than equivalent sites with subdomain blogs.

02The exception myth

For years, some agencies argued that subdomain vs subfolder is "the same to Google" because the algorithm has gotten more sophisticated. This argument is wrong, has been wrong for at least 8 years, and has cost a generation of B2B SaaS marketing teams meaningful ranking power.

The evidence:

• Google's John Mueller has explicitly stated subdomains are treated as separate sites in some respects.
• Migrations from subdomain to subfolder consistently produce 15 to 35 percent organic traffic increases within 6 months across hundreds of documented cases.
• The reverse migration (subfolder to subdomain) consistently produces traffic decreases.

If subdomain and subfolder were "the same to Google," neither effect would exist.

03The docs question (more nuanced)

For documentation, the answer depends on what the docs are for.

Customer-only docs

Reference documentation accessed primarily by logged-in customers. Authentication required for most pages. Search demand is low because the content is for existing users. SEO benefit is minimal regardless of architecture. Subdomain is fine here. docs.yoursaas.com keeps the docs traffic isolated from marketing analytics, which can be administratively useful.

Prospect-facing docs

Public documentation that serves potential customers researching whether the product fits their needs. Tutorial guides, getting-started content, integration walkthroughs. This content has search demand. Buyers find it through Google. SEO benefit is significant. Subfolder is the right choice here. yoursaas.com/docs inherits the marketing site's authority and the docs traffic compounds with the marketing traffic.

Hybrid docs

Most B2B SaaS docs are actually hybrid: some customer-only reference, some prospect-facing tutorial. The right architecture for hybrid docs:

• Public, prospect-facing docs at yoursaas.com/docs (or yoursaas.com/learn or similar)
• Customer-only reference at docs.yoursaas.com or under the authenticated app

This split costs more to maintain (two systems instead of one) but captures the SEO benefit of the prospect-facing content while keeping the customer-only content separate.

04The exception that justifies a subdomain

There is one B2B SaaS scenario where subdomain might be the right choice: when the docs are genuinely a separate product.

Stripe's docs are a separate product in this sense. Twilio's docs are a separate product. The docs themselves are central to the developer relations strategy, have their own content team, their own brand presence, their own search demand independent of the main product marketing site.

For these companies, docs.stripe.com or docs.twilio.com is appropriate. The docs site has accumulated its own authority over years and the SEO benefit is captured directly by the docs subdomain.

For most B2B SaaS companies (sub-$50M ARR, docs as a supporting layer of the marketing site), this exception does not apply. The default is subfolder.

05International SEO

For multi-region or multi-language sites, the subdomain vs subfolder question intersects with internationalization.

Subfolder approach

/en/, /de/, /fr/ subfolders with hreflang tags. All traffic accumulates on the same root domain. Authority transfers cleanly. The default for B2B SaaS.

Subdomain approach

en.example.com, de.example.com, fr.example.com with hreflang tags. Authority pools split. Each subdomain accumulates its own authority. Useful only when the regional sites are genuinely separate operations.

ccTLD approach

example.de, example.fr, example.co.uk. Strong local ranking signal but enormous management overhead. Useful only for companies with major regional presence and dedicated regional teams.

For most B2B SaaS companies, subfolder with hreflang is the right choice. Global content stays in /en/ (or root if English is the default). Localized content goes in /de/, /fr/, etc. One domain, unified authority.

06The migration path

For a B2B SaaS site currently on a subdomain blog or docs, the migration to subfolder typically produces 15 to 35 percent organic traffic increase within 6 months.

The migration steps:

1. URL mapping. Every subdomain URL maps to a subfolder equivalent. blog.yoursaas.com/article-1 → yoursaas.com/blog/article-1.
2. Engineering setup. The marketing site CMS or framework needs to handle the new subfolder structure. For Webflow, this is a settings change. For custom Next.js, it requires routing updates.
3. 301 redirects. Every old subdomain URL 301-redirects to the new subfolder URL. Configure at the DNS or hosting level for the subdomain.
4. Internal linking update. Every internal link inside content that pointed to subdomain URLs gets updated to subfolder URLs. Reduces redirect chains.
5. Sitemap and GSC. New sitemap with subfolder URLs. Submit to GSC. Add the subfolder URLs as a new property if previously the subdomain was a separate property.
6. Launch on a Tuesday morning. Same migration discipline as any platform migration. Engineering on standby for 72 hours. Daily GSC monitoring for 14 days.
7. Re-indexation. Expect 4 to 6 weeks for full re-indexation. Top traffic pages typically recover within 2 weeks. Long-tail pages take longer.

The recovery curve is reliable: small dip in week 1, stabilization week 2 to 3, growth from week 4 onward. By month 6, total organic traffic is meaningfully higher than the subdomain baseline.

07The decision framework

For new B2B SaaS sites, the default is always subfolder for blog. Default subfolder for docs unless docs is a separate product.

For existing B2B SaaS sites on subdomain, the migration is worth it when:

• The blog or docs has meaningful organic traffic already (1,000+ monthly sessions)
• The content team can maintain content production through the migration window
• Engineering has bandwidth for the migration work (typically 40 to 80 hours)
• A 4 to 6 week traffic stabilization period is acceptable

The migration is not worth it when:

• The subdomain blog is rarely updated and has no traffic
• The marketing site itself has bigger problems (CWV, indexation, content quality) that should be fixed first
• The company is mid-rebrand or about to migrate platforms anyway (combine the two migrations)
• The docs are genuinely a separate product as discussed above

08Part of a larger technical playbook

This article covers one specific architectural decision. For the full B2B SaaS technical SEO process, see our B2B SaaS technical SEO checklist. For related deep dives, see B2B SaaS website migrations without ranking loss and Internal linking architecture for B2B SaaS.

Where this fits in the broader playbook

This piece sits inside how we approach technical SEO for SaaS, which is one chapter of the full B2B SaaS SEO playbook. For deeper framing on the same discipline, see the technical SEO discipline for B2B SaaS programs.

Closely related reading from the same sub-pillar

• the SaaS website migration framework , the migration playbook that handles this decision.
• the internal linking playbook , how the architecture decision affects internal-link equity.
• the CWV targets , CWV implications of split architectures.

From other corners of the program

• how we earn editorial coverage , the cross-cluster discipline that compounds this work.
• the link building pillar covering all five disciplines , the upstream pillar this connects to.

When you're ready to put this into a program, schedule a discovery call or review program pricing tiers. Average response time: under 4 business hours.