Subfolder vs Subdomain: What the SEO Data Actually Shows

The subfolder vs subdomain debate has been running for over a decade, and it resurfaces every time a company decides to launch a blog. Should the blog live at example.com/blog or blog.example.com? Google's official position is that it can handle both. But the migration data tells a different story.

Across documented case studies, companies that moved their blog from a subdomain to a subfolder saw traffic gains. Companies that moved the other direction saw losses. The pattern is consistent enough that for most businesses, the answer is straightforward: put your blog on a subfolder.

This article breaks down why, with data.

What's the Actual Difference Between a Subfolder and a Subdomain?

A subfolder (also called a subdirectory) places your blog under your main domain's URL path:

example.com/blog/your-post-title

A subdomain places your blog on a separate hostname:

blog.example.com/your-post-title

The distinction matters because Google treats these differently. A subfolder is part of the same site as your root domain. A subdomain, according to Google's own documentation on URL structure, can be treated as a separate entity for crawling and indexing purposes. That separation has real consequences for how authority, links, and crawl resources get distributed.

Subfolder vs subdomain for SEO: Subfolders consolidate domain authority and crawl budget with your main site. Subdomains operate as separate hostnames with separate crawl budgets and siloed link equity. Migration data consistently shows traffic gains when moving from subdomain to subfolder, and losses in the other direction.

Why Subfolders Usually Win for Blog SEO

Three SEO mechanisms favor subfolders over subdomains. Each one compounds the advantage over time.

Domain Authority Consolidation

Domain authority is one of the strongest predictors of how fast new content ranks. When someone links to a blog post on example.com/blog/great-article, that backlink strengthens example.com as a whole. Every piece of link equity flows into the same domain, boosting the authority of your homepage, product pages, and every other page on the site.

When that same blog post lives on blog.example.com, the link equity stays on the subdomain. Your blog might build strong authority, but your main domain doesn't benefit directly. You're essentially building two separate authority profiles instead of one. For companies investing in content marketing to build topical authority, this fragmentation undermines the entire strategy.

Crawl Budget Efficiency

Google allocates crawl budget per hostname. This means blog.example.com gets its own separate crawl budget from example.com. For large sites, Google's crawl budget documentation confirms that each hostname is crawled independently.

With a subfolder structure, your blog shares the main domain's crawl budget. Google crawls your entire site as one unit, discovering new blog posts alongside product pages and landing pages. With a subdomain, Google has to allocate and manage crawl resources separately, which can mean slower discovery of new content, especially for smaller sites that don't generate enough signals to warrant frequent crawling.

Link Equity Flow

Internal links from your blog to your product pages (and vice versa) pass more authority when they're on the same domain. A link from example.com/blog/seo-guide to example.com/pricing is an internal link. A link from blog.example.com/seo-guide to example.com/pricing is technically a cross-domain link, and while Google says it can understand the relationship, analysis from Portent and others shows that internal links within the same hostname pass equity more reliably.

When Subdomains Actually Make Sense

Subdomains aren't always the wrong choice. There are legitimate architectural reasons to separate content onto a subdomain:

• Completely different technology stacks. If your main site runs on a platform that can't serve blog content (and no routing layer is available), a subdomain avoids replatforming. This is increasingly rare as edge routing and reverse proxy solutions have made subfolder blogs possible on virtually any stack.
• Genuinely separate products or business units. If your blog serves a fundamentally different audience than your main site (think developers.example.com for a developer portal), separation can make sense.
• User-generated content at massive scale. Platforms like Medium or WordPress.com use subdomains because each user operates an independent site. This is an architecture decision, not an SEO one.
• Regulatory or compliance isolation. Some industries require content separation for legal reasons.

Quick decision test: If the content supports the same business and serves the same audience as your main domain, use a subfolder. If it's a genuinely separate product, platform, or user base with its own technical stack and growth trajectory, a subdomain is defensible.

The Migration Data: What Happens When Companies Switch

The strongest evidence for subfolders comes from companies that actually made the switch. The results are remarkably consistent.

Subdomain to Subfolder: Traffic Gains

Sistrix's analysis of high-profile domain migrations found a clear pattern. Monster.com saw a 116% increase in search visibility after consolidating content from subdomains into the main domain's subfolder structure. Deutsche Telekom's t-online.de showed similar gains after restructuring.

In another well-documented case, a bakery e-commerce site saw a 40% increase in organic traffic within months of moving its blog from blog.pinkcakebox.com to pinkcakebox.com/blog. The content didn't change. The only difference was the URL structure.

Subfolder to Subdomain: Traffic Losses

The inverse migrations tell the same story from the other direction. When iwantmyname.com moved their blog from a subfolder to a subdomain, they documented a measurable drop in organic traffic. As Portent's analysis notes, this case is frequently cited because the team publicly shared the data, confirming what SEO practitioners had suspected: splitting content onto a subdomain dilutes the authority you've built.

What Google Says vs What the Data Shows

Google's John Mueller has repeatedly said that Google can handle both subdomains and subfolders, and that neither has an inherent SEO advantage. According to Search Engine Roundtable's coverage of Mueller and Gary Illyes' statements, Google's systems are designed to understand site relationships across subdomains.

This is technically accurate but misses the practical reality. Google can figure out that blog.example.com belongs to example.com. But "can figure out" is not the same as "treats identically." The crawl budget separation is documented. The link equity behavior is measurable. And the migration data consistently shows that consolidation wins.

How to Put Your Blog on a Subfolder (Even When Your CMS Makes It Hard)

The most common objection to subfolders is technical: "My website platform doesn't support it." This was a valid concern five years ago. It's largely solved today.

The Technical Challenge

Many website builders and CMS platforms host your site on their infrastructure. Adding a /blog path that serves content from a different system requires a routing layer between the visitor and the origin servers.

Edge Routing and Reverse Proxy Solutions

The modern solution is a routing layer that intercepts requests and directs them to the right backend based on the URL path. If a visitor requests example.com/blog/post, the router sends them to your blog system. For any other path, they get your main website.

This is exactly how companies add blogs to Webflow without using Webflow's CMS, and the same approach works for Squarespace, Shopify, or any platform. Tools like EdgeBlog handle this through edge routing, where the routing happens at the CDN level with no performance penalty. Cloudflare Workers, Vercel Edge Middleware, and Nginx reverse proxies can achieve the same result with more configuration.

The point is that "my platform doesn't support subfolders" is no longer a blocker. The routing infrastructure exists to make subfolder blogs work on any stack.

If you're choosing where to host your company blog, the data points in one direction. Subfolders consolidate authority, share crawl budget, and let every backlink strengthen your entire domain. The exceptions are real but narrow.

For companies running on platforms that default to subdomains, edge routing makes the subfolder path accessible without rebuilding your site. EdgeBlog sets this up automatically as part of its blog automation, so your content publishes to /blog on your existing domain from day one.