How Moving /blog from a Subdomain to a Subfolder Grew Organic Traffic by 34%

In January 2025, a SaaS company we'll call Acme — a B2B project management tool with ~180,000 monthly visitors — approached us with a familiar problem. Their blog had lived at blog.acme.com for four years. They had 340 indexed posts, a solid backlink profile, and a content team producing three pieces a week. Traffic was growing, but slowly.

Their SEO consultant had flagged the subdomain as a structural issue. Acme's engineering team had investigated a server-based reverse proxy, quoted three weeks of work, and the project stalled.

We ran the migration with Furl in 47 minutes of actual work. Ninety days later, organic traffic was up 34%.

This is the full story — with real numbers, the exact timeline, and the things that almost went wrong.

The starting point: a split domain authority problem

Before touching anything, we ran a full audit. The picture was clear.

Acme had accumulated a strong link profile over four years — Ahrefs showed 4,200 referring domains pointing to acme.com properties and 1,100 pointing specifically to blog.acme.com. Those 1,100 domains were sending their PageRank to a subdomain that Google treats as a separate entity.

Google's John Mueller has confirmed this in multiple Search Central office hours. In a 2021 session, when asked whether subdomains consolidate with root domains for ranking purposes, Mueller said: "We try to be good at figuring out what belongs together and what doesn't, but it's not perfect. If you want to be safe, use subfolders."

The keyword ranking data confirmed the leak. Acme's blog was ranking for over 600 keywords — but almost none of those rankings were lifting the main acme.com domain. The blog's authority was essentially trapped in an island.

Pre-migration baseline (January 2025)

We pulled 90-day trailing data from Search Console before touching a single DNS record.

The blog was generating meaningful traffic, but it was doing so in isolation. And because it was a subdomain, internal links from blog posts to acme.com pages were being treated as external links by Google's crawler — which means they counted for less than they should.

The migration plan

CNAME/ALIAS  @    proxy.usefurl.com
CNAME        www  proxy.usefurl.com

blog.acme.com/*  →  acme.com/blog/*  (301 Permanent)
blog.acme.com/   →  acme.com/blog/   (301 Permanent)

The 90-day timeline

This is where the numbers get interesting — and where most case studies skip the uncomfortable middle.

Days 1–7: Re-indexing begins

Googlebot followed the 301s within 48 hours. We could see it in Search Console — crawl requests to blog.acme.com URLs dropped sharply, replaced by crawl requests to acme.com/blog/ paths.

By day 5, the first acme.com/blog/ URLs appeared in Search Console's coverage report as "Submitted and indexed." The old subdomain URLs were being marked as "Redirect" in the Legacy report.

Days 7–21: The re-indexing dip

Total organic clicks (combined across both properties) dipped from ~4,400/day to ~4,050/day. The subdomain traffic was collapsing as expected — Google was actively replacing it with the new URLs — but the main domain hadn't yet picked up the full offset.

This is the moment most teams get scared and start to question the decision. Don't.

Days 22–45: Consolidation kicks in

The 1,100 referring domain backlinks began flowing their PageRank to acme.com/blog paths, which in turn flowed to acme.com. We could see this in Ahrefs — the Domain Rating of acme.com started ticking up from 61 to 63 over this period.

Keyword rankings for the main domain began improving — not just for blog content, but for the main SaaS pages too. Product pages that had been stuck at position 14–18 for competitive keywords started pushing toward the first page.

Days 46–90: The compounding effect

What actually drove the improvement

1. Link equity consolidation

The most significant factor. Those 1,100 referring domains pointing to blog URLs were previously sending authority to an island. Post-migration, their PageRank now flows through to acme.com's main authority pool. This raised the floor for every page on the domain — not just the blog.

2. Internal linking became cross-domain linking — and then it fixed itself

Before migration, when a blog post linked to acme.com/features, that was an external link in Google's model. After migration, blog posts live on acme.com — so the same link is now internal, carrying significantly more weight for the features page.

Acme had 340 blog posts, each with multiple links to their product pages. Consolidating the domain effectively gave every product page hundreds of additional internal links.

3. Crawl budget unification

Search Console showed Googlebot was splitting crawl budget between two separate root origins. After migration, the full budget was allocated to acme.com. Coverage of previously lightly-crawled pages improved significantly.

4. Canonical tag integrity

Screaming Frog's post-migration crawl confirmed that 100% of canonical tags now pointed to acme.com/blog/ paths. Pre-migration, 23% of posts had canonical inconsistencies — WordPress was self-referencing its own subdomain in some cases, and the canonical wasn't always propagating correctly through caching layers.

What almost went wrong

The HubSpot precedent

Acme isn't alone. This is a well-documented pattern at scale.

HubSpot famously migrated their blog from blog.hubspot.com to hubspot.com/blog in 2011. Co-founder Dharmesh Shah described it as "one of the best SEO decisions we've ever made." HubSpot's blog subsequently grew to become one of the highest-traffic marketing blogs in the world, ranking for hundreds of thousands of keywords. While it's impossible to isolate the subdomain migration as a single variable, HubSpot's own team has attributed meaningful long-term authority gains to the consolidation.

Moz made a similar migration of their blog in 2013. In their post-migration analysis, they documented a measurable improvement in the ranking ability of their non-blog pages within 60 days of completing the move.

Is it always this clean?

No. The 34% figure is real but not guaranteed. Outcomes depend on:

• How strong your existing backlink profile is: If you have minimal inbound links to the subdomain, the authority consolidation effect is smaller.
• How well you execute the 301 redirects: Missing redirects on even a handful of high-traffic posts can create crawl errors that persist for months.
• Your site's existing Domain Rating: Sites with DR 40–70 tend to see the clearest signal from consolidation. Very high-DR sites (80+) have enough existing authority that the marginal improvement is smaller; very low-DR sites haven't built enough to consolidate.
• How quickly Google re-crawls your site: Sites with high crawl budgets (more content, more inbound links) get re-indexed faster.

For Acme specifically, they had a mature link profile pointing to the subdomain, a fast site, and high-quality blog content. The conditions were ideal for consolidation.

The case for doing it now

The longer you wait, the more authority accumulates in the wrong place. Every backlink your blog earns today on a subdomain is PageRank that isn't flowing to your main domain. At Acme's scale, that meant 15 months of content marketing investment partially stranded on an island.

The fix used to require a server, a sysadmin, and a weekend. With Furl, the DNS changes and route setup took under an hour of actual work. The 90-day wait is unavoidable — that's Google's timeline, not yours.