We inherited a client last year โ a multi-location dental group โ that had their blog on blog.brightsmile.com, their patient portal on portal.brightsmile.com, and their main site on www.brightsmile.com. Three subdomains, all treated by Google as essentially separate websites.
The blog had 60+ well-written articles. Strong content. Decent backlinks. But none of that authority was flowing back to the main site where the service pages lived โ the pages that actually converted visitors into patients. In Google's eyes, the blog was a separate entity from the practice.
We migrated the blog from blog.brightsmile.com to brightsmile.com/blog/. Same content. Same URLs (minus the subdomain prefix). Within eight weeks, the main site's service pages saw a 34% ranking improvement across their target keywords. The blog content's authority was finally flowing to the pages that needed it.
That's the subdomain problem in a nutshell โ and why this question matters more than most people realize.
Before we get into the SEO implications, let's make sure we're talking about the same thing. These two URL structures look similar but are treated very differently:
The distinction matters because of how Google handles authority. Backlinks, content signals, and domain-level trust all flow differently depending on which structure you use.
Google's official position is that they can handle subdomains and subdirectories equally well. John Mueller has said on multiple occasions that Google is "generally fine" with either approach and can understand that a subdomain belongs to the same organization as the root domain.
That's the official line. Here's what we actually observe in practice:
Google treats subdomains as semi-separate entities. They share some authority signals with the root domain, but not all of them. A subdomain has its own crawl stats in Search Console, its own backlink profile in most SEO tools, and can rank independently from the main site. Subdirectories, by contrast, are fully part of the main domain. Every backlink to a subdirectory page strengthens the entire domain. Every piece of content in a subdirectory contributes to the site's overall topical authority.
The practical difference isn't theoretical. We've seen it play out across dozens of client migrations. Content on subdomains consistently underperforms the same content moved to subdirectories โ because the subdirectory version benefits from the full weight of the domain's authority.
This is the core reason we almost always recommend subdirectories over subdomains. Here's what happens to your link authority under each structure:
Authority is fragmented across separate entities
All authority consolidated under one domain
The math is simple. With subdomains, backlinks to your blog don't fully strengthen your service pages. With subdirectories, every backlink to any page on your site strengthens every other page. For most businesses โ especially those competing in challenging markets โ that consolidated authority is the difference between page 1 and page 3.
We're not saying subdomains are always wrong. There are legitimate use cases where separating content onto a subdomain is the right call:
shop.example.com might be the most practical option. Forcing two different platforms into the same subdirectory structure can create serious technical headaches.enterprise.example.com and developers.example.com โ subdomains can make organizational sense. Google, Atlassian, and HubSpot all use this approach.staging.example.com for development previews is fine โ as long as it's password-protected or noindexed. This is a technical utility, not a content strategy.Notice what's not on this list: blogs, location pages, service pages, landing pages, or any content designed to rank in search results. Those should always be on your main domain as subdirectories.
This is the most common one, and it's the most costly. Your blog exists to build topical authority, earn backlinks, and support your service pages through internal linking. On a subdomain, that authority is siloed away from the pages that need it most. We've migrated dozens of blogs from subdomains to subdirectories, and the result is the same every time โ measurable ranking improvements within 4โ8 weeks.
Some multi-location businesses create austin.example.com, dallas.example.com, houston.example.com instead of example.com/locations/austin/. Each subdomain starts from scratch with zero authority. The subdirectory approach lets every location benefit from the domain's existing authority.
This is a technical convenience decision masquerading as a strategic one. Yes, it's sometimes easier to spin up a separate WordPress install on a subdomain than to integrate content into an existing site. But "easier to set up" and "better for SEO" are very different things. The short-term setup convenience costs long-term ranking potential.
Many hosting setups support reverse proxies, which let you serve content from a separate platform (like a Headless CMS or Shopify) through a subdirectory URL on your main domain. It requires more technical setup upfront, but it preserves the SEO benefits of consolidated authority. We've set this up for multiple clients who needed separate platforms without sacrificing SEO.
If your blog, location pages, or other important content is currently on a subdomain and you want to consolidate, here's the process we follow:
Crawl the subdomain to identify all pages, their rankings, traffic, and backlinks. This becomes your migration map. Don't move content that's getting zero traffic โ consolidate or delete it instead.
Set up the same content on the main domain in the appropriate subdirectory. blog.example.com/dental-implants-guide/ becomes example.com/blog/dental-implants-guide/. Keep URLs as similar as possible to minimize confusion.
Every old subdomain URL must 301 redirect to its new subdirectory URL. This is the critical step that transfers the old page's link equity and ranking signals to the new location. Missing redirects means lost authority.
Update all internal links across your site to point to the new subdirectory URLs. Submit the updated sitemap. Add the new URL structure in Search Console. Update your Google Business Profile if any linked pages moved.
Traffic may dip slightly in the first 1โ2 weeks as Google processes the redirects. This is normal. By week 4โ6, you should see the consolidation benefit โ service pages ranking higher as the migrated content's authority flows to them. If anything breaks, catch it early.
Our recommendation for almost every business: Unless you have a specific technical reason that requires platform isolation, keep everything on your root domain in subdirectories. Your blog at /blog/. Your locations at /locations/. Your services at /services/. Every page strengthens every other page, and nothing gets left behind on an authority island.
Subdomains aren't inherently bad. Google can handle them. They have legitimate use cases for application isolation, separate platforms, and organizational separation. But for content that's designed to rank in search results and support your business goals โ blogs, service pages, location pages, resource centers โ subdirectories are the stronger choice in nearly every scenario.
The reason is simple: consolidated authority beats fragmented authority. A domain with all its content, backlinks, and topical signals unified under one roof will outperform the same content scattered across subdomains that don't fully share their strength with each other.
If your site currently uses subdomains for content that should be driving rankings, a migration to subdirectories is one of the highest-ROI technical changes available. We've done it for dozens of clients, and the results are consistent: stronger rankings, more traffic, better authority consolidation โ from a structural change that requires no new content and no new backlinks.
Not sure if your subdomain setup is costing you rankings? Our free SEO audit includes a site architecture analysis that identifies authority fragmentation, subdomain issues, and consolidation opportunities.
Our free audit identifies subdomain fragmentation, authority dilution, and consolidation opportunities โ plus a migration plan if one is needed.