Subdomain SEO: When Subdomains Help and Hurt Rankings

Google treats a subdomain like a separate website most of the time, which means the authority you’ve built on your main domain doesn’t automatically flow to it. For SEO, that’s usually bad news. There are exactly three situations where a subdomain still makes sense, and hundreds where a subfolder would rank better.

The subdomain vs subfolder debate has been running since roughly 2010, and the answer hasn’t really changed. It’s just gotten quieter because enough people finally moved their blogs from blog.example.com to example.com/blog and saw their traffic climb. HubSpot did it. Moz did it. Shopify skipped the debate entirely.

Does Google treat subdomains as the same site?

Sometimes yes, often no, and you don’t get to pick. Google’s systems decide on a case-by-case basis whether a subdomain is part of the main site or a separate entity, and the decision depends on signals like internal linking, shared branding, overlapping content, and crawl patterns.

John Mueller has said this roughly six different ways over the last decade. The cleanest version: “Google Web Search is fine with using either subdomains or subdirectories.” That quote gets misread as “it doesn’t matter.” What Mueller actually means is Google is fine crawling either. Ranking is a separate question, and that one has a clearer answer.

When the subdomain shares the main site’s template, nav, and internal links, Google tends to merge the two in search. When the subdomain looks like a different property, like a help center with its own chrome or a careers page built in Greenhouse, Google keeps them separate. You can’t force consolidation by wishing hard.

When does a subdomain pass authority to the root domain?

Rarely, and never in a way you can count on. PageRank flows through links, and subdomains do link back to the root, so some authority transfers the same way it would from any external site. But the transfer is lossy, unpredictable, and often slow.

I’ve watched clients migrate from blog.domain.com to domain.com/blog and see traffic climb 20-40% within 90 days. Same content. Same URLs except for the hostname. Same backlink profile (via 301 redirects). The only variable that changed was the URL structure.

Moz published a case study in 2018 when they moved their blog from moz.com/blog (already a subfolder) and kept it there specifically because the subfolder was outperforming any subdomain alternative. Rand Fishkin has talked about this publicly enough times that it’s basically settled industry opinion at this point.

That said, authority flow isn’t zero. Big sites like blog.hubspot.com still rank fine because HubSpot has enough brand signals, links, and content velocity to make the subdomain strong on its own. The subdomain isn’t free-riding on hubspot.com. It’s earned its own authority over 15+ years.

Subfolder vs subdomain: which one wins for SEO?

Subfolders win 90% of the time for one reason: consolidated authority. Every backlink, every internal link, every brand mention that points to your domain helps every page on that domain, including your blog, your help docs, your resources, and your product pages. Split that across a subdomain and you’re fighting two authority battles instead of one.

The exceptions are narrow:

• You’re running a completely separate product with its own audience (different buyers, different intent, different search queries).
• You’re running an international version of the site with different language, currency, and content strategy.
• You’re running user-generated content you don’t want to commingle with your main brand (like a community or a subdomain for customer-generated subsites).

For everything else, a subfolder beats a subdomain. The blog. The knowledge base. The case studies. The pricing page. The changelog. All of it.

Why did HubSpot keep blog.hubspot.com while everyone else moved?

HubSpot is one of the loudest exceptions to the subfolder rule, and it’s worth understanding why their situation is different from yours. They started on blog.hubspot.com in 2006 and built it into a 4M+ monthly traffic juggernaut before the subfolder-is-better consensus emerged.

Migrating a blog with millions of indexed URLs and tens of thousands of high-authority backlinks is risky. If you’re HubSpot and your organic traffic pays the salaries of hundreds of people, you don’t migrate unless the upside is proven and the downside is tolerable. HubSpot ran the math and decided the migration wasn’t worth the risk.

Smaller sites don’t have that problem. If you’ve got 200 blog posts on a subdomain, you can 301 redirect the lot in a weekend and recover most of the authority within a month.

HubSpot, Moz, Backlinko, and Shopify have all weighed in on this at various points. The consensus: if you’re starting fresh, use a subfolder. If you’re already on a subdomain and the migration cost is low, move to a subfolder. If you’re on a subdomain with tens of thousands of ranking pages, run the numbers carefully before migrating.

When does a subdomain actually make sense?

Three cases, in order of strength.

International versions. fr.example.com for the French version of your site makes hreflang simpler, geo-targeting cleaner, and content management more sane. You can also use ccTLDs (example.fr) or subfolders (example.com/fr/), and each has tradeoffs. The subdomain approach works well when you’ve got a local team running the localized version with some independence from the main site.

Separate products or brands. If Atlassian sold Jira and Trello from atlassian.com, it would be confusing. trello.com and jira.atlassian.com (historically) let each product build its own authority for its own query space. The subdomain signals “related but distinct,” which is exactly the message Atlassian wanted.

User-generated content platforms. GitHub uses username.github.io. Tumblr uses username.tumblr.com. Substack uses publication.substack.com. All for the same reason: millions of UGC subsites on the root domain would dilute brand quality signals and create moderation headaches. Subdomains isolate the mess.

That’s the list. Three cases. Everything else is better on a subfolder.

What about regional subdomains like uk.example.com?

Regional subdomains work fine if you run them correctly, but they’re not automatically better than subfolders with hreflang. Google reads both patterns, and the choice mostly comes down to operational preference.

I’ve worked with e-commerce clients running us.shopify-example.com, uk.shopify-example.com, and au.shopify-example.com. The setup was clean: separate inventory, separate currency, separate tax handling, separate payment processors. Subdomains made backend routing easier because each subdomain pointed to a different app instance.

But the SEO side was harder. Each regional subdomain had to build its own authority. Link-building campaigns had to be regional. Content had to be duplicated across all three sites with hreflang annotations, or rewritten for each region.

The subfolder approach (example.com/us/, example.com/uk/) consolidates authority to the root domain, which means a strong link earned for the UK site also helps the US site rank. For most businesses, that’s the better tradeoff.

How do I migrate from a subdomain to a subfolder without losing traffic?

Plan the migration in five phases: inventory, URL mapping, 301 redirects, Search Console, and monitoring. Skipping any of them causes 30-90 day traffic drops that take months to recover from.

Start with a full URL inventory. Use Screaming Frog or Sitebulb to crawl every URL on the subdomain. Export the list. Cross-reference with Google Search Console top pages to make sure nothing ranking well gets orphaned.

Build a URL mapping spreadsheet. Every old URL on blog.example.com/post-name maps to example.com/blog/post-name. Sounds simple. Gets complicated when you have date-based archives, author pages, category hierarchies, and paginated URLs. Get this right or redirect loops eat your traffic.

Set up 301 redirects at the server level, not in a WordPress plugin. Cloudflare Workers, nginx config, or Apache rewrite rules all work. Avoid redirect chains. A single 301 hop from old URL to new URL. Anything more, Google discounts the authority.

Submit the new sitemap in Google Search Console. Keep the old property verified so you can monitor the migration. Watch crawl stats, indexed pages, and impressions daily for the first 30 days.

Expect a 10-25% traffic dip in weeks 2-4, then recovery by weeks 8-12. If recovery stalls, audit the redirects. Broken 301s account for most failed migrations I’ve diagnosed.

Does subdomain vs subfolder affect Core Web Vitals?

No directly, but it affects how easily you can optimize Core Web Vitals at scale. A subdomain usually runs on its own stack (different CMS, different hosting, different CDN config), which means every performance fix has to be applied twice.

A subfolder shares the same stack as the root domain. One caching config. One CDN. One image optimization pipeline. One theme. Every performance improvement benefits the whole site.

Running blog.example.com on WordPress and example.com on a headless Next.js stack is operationally expensive. Two deployment pipelines. Two monitoring setups. Two teams (or one team context-switching). The performance side usually suffers because nobody has time to optimize both stacks equally.

What does John Mueller actually say about subdomain SEO?

Mueller has been consistent since at least 2017: Google can handle either structure, but the site owner should pick based on operational and branding considerations rather than expecting a ranking boost from one over the other.

His most quoted line, from a 2017 Webmaster Hangout: “Google Web Search is fine with using either subdomains or subdirectories. Making changes to site’s URL structure tends to take a bit of time to settle down in search, so I’d pick a set up that you can keep for longer.”

The subtle part of that quote is “tends to take a bit of time to settle down.” Translation: pick one and stick with it. The churn of moving is worse than the structure you didn’t pick.

Mueller has also said repeatedly that Google’s understanding of subdomains has improved over time. In 2021: “We generally can figure out, if a subdomain is essentially the same site as the main site, and we’ll kind of treat it that way.” Kind of. That’s the key word. It works sometimes, and you can’t predict when.

Common subdomain SEO mistakes I see constantly

The biggest mistake: assuming a subdomain automatically inherits authority from the root domain. It doesn’t. You have to earn it.

Second: forgetting to verify the subdomain separately in Google Search Console. example.com and blog.example.com are separate properties. Rankings, impressions, clicks, and issues for the subdomain won’t show up in the root property.

Third: inconsistent branding. Subdomain with different logo, different nav, different footer makes Google more likely to treat it as separate. If you want consolidation signals, share the chrome.

Fourth: pointing backlinks at the root when you want to boost the subdomain (or vice versa). If you’re building links to example.com/ expecting them to help blog.example.com rank for recipe queries, they won’t, or at least not directly.

Fifth: using www.blog.example.com or other triple-level subdomains. Technically works. Practically a mess. Google handles it, users don’t. Nobody types three dots.

Sixth: letting the subdomain duplicate content with the root. Same posts on blog.example.com/recipe and example.com/recipe means you compete with yourself. Canonical tags help but don’t fix the underlying sloppiness.

What about subdomains for SaaS documentation?

Documentation subdomains like docs.example.com are almost always better as subfolders (example.com/docs), unless you’re running the docs on a third-party platform (GitBook, ReadMe, Docusaurus on Vercel) that doesn’t easily integrate with your main stack.

The case for the subdomain is operational: docs tooling usually runs on its own stack and deploying docs through the marketing CMS is painful. The case for the subfolder is SEO: docs rank for high-intent product queries, and those rankings benefit from root-domain authority.

Stripe uses stripe.com/docs. Vercel uses vercel.com/docs. Linear uses linear.app/docs. Notion uses www.notion.so/help. All subfolders. All ranking well for high-commercial-intent queries.

The ones using subdomains (docs.github.com, developers.cloudflare.com) have enough brand authority that either approach works for them. They’re exceptions, not role models.

Subdomain SEO FAQ

The decision rule

Default to a subfolder. Use a subdomain only when the content is genuinely separate (different audience, different product, different language) or when operational constraints force your hand.

If you’re already on a subdomain and your site is under 500 pages, migrate. The short-term pain is worth the long-term authority consolidation. If you’re on a subdomain with 10,000+ ranking pages, run the numbers and probably stay put. The migration risk at that scale usually exceeds the authority upside.

And if you’re starting fresh today, you already know the answer. One domain. One stack. One authority pool. Everything the business publishes, everything that ranks, all lined up to help each other.