SEO for Subdomains: When They Help and When They Hurt

SEO for subdomains is one of those topics where the technical answer and the strategic answer often point in different directions. A subdomain is a separate section of your website hosted under a prefix of your main domain, such as blog.example.com or support.example.com, and search engines can treat it as a distinct entity from your root domain. Whether that separation helps or hurts your rankings depends almost entirely on how you use it and why.

The debate has been running for years: do subdomains dilute your domain authority, or do they give you structural flexibility that a single root domain cannot? The honest answer is that both are true, under different conditions. Getting the decision wrong costs you organic visibility that is genuinely hard to recover.

What Actually Happens to SEO When You Use a Subdomain

When Google crawls blog.example.com, it has the technical capacity to associate that subdomain with the root domain example.com. In practice, it sometimes does and sometimes does not, and that inconsistency is where SEO problems begin. Google has stated publicly that it can connect subdomains to their parent domains, but “can” is doing a lot of work in that sentence. The signal flow is weaker than a subfolder structure, and in competitive niches, weaker signal flow costs you rankings.

The core issue is link equity. When a publisher links to a piece on your blog subdomain, that link builds authority for the subdomain. In a subfolder setup, that same link builds authority for the root domain. Over time, across thousands of links, the difference compounds. I have watched businesses spend years building out content on a blog subdomain and then wonder why their root domain is not ranking for commercial terms. The content was good. The links were real. The structure was working against them the entire time.

This does not mean subdomains are always the wrong call. It means the decision needs to be made deliberately, with a clear understanding of the trade-offs, not by default because your developer found it easier to set up.

If you are building out a broader SEO strategy and want to understand how subdomain decisions fit into the wider picture, the complete framework is covered in the Complete SEO Strategy hub, which pulls together the structural, technical, and content decisions that compound over time.

When Subdomains Are the Right Structural Choice

There are genuine use cases where a subdomain is the correct decision, and it is worth being specific about them rather than dismissing the structure entirely.

The clearest case is a web application that sits alongside a marketing site. If your product is a SaaS platform and your users log in at app.example.com, that is not an SEO decision, that is an infrastructure decision. The application runs on different technology, serves a different user purpose, and has no business being merged with your marketing content. The same logic applies to support portals, community forums, and developer documentation that require distinct technical environments.

International and multilingual sites are another legitimate use case. Some businesses use country-code subdomains, fr.example.com or de.example.com, as part of their international SEO structure. This is a recognised approach, though country-code top-level domains and subfolder structures each have their own trade-offs. The subdomain route is defensible when the operational complexity of managing separate domains is too high and the business needs clear geographic signal separation.

Staging and development environments belong on subdomains, blocked from indexing. That is standard practice and has no SEO implication as long as the robots.txt and noindex directives are correctly configured. Where I have seen this go wrong is when staging environments are left accessible and Google crawls them, creating duplicate content issues that take months to diagnose.

The pattern that should concern you is using a subdomain purely for content organisation when a subfolder would serve the same purpose. Blog content, resource libraries, case studies, and knowledge bases almost always belong in subfolders. The argument that “it is cleaner” or “easier to manage” is not an SEO argument. It is a convenience argument dressed up as one.

The Real Cost of the Wrong Subdomain Decision

Early in my agency career, I worked with a business that had spent three years building what was genuinely impressive editorial content on a blog subdomain. The articles were well-researched, the topics were relevant, and some pieces had attracted solid inbound links from respected publications. On paper it looked like a content programme that was working. Traffic to the blog was growing. The team was proud of it.

The problem was that the root domain, where the actual product pages lived, was barely ranking for anything competitive. The content investment had not translated into commercial visibility. When we audited the structure, the blog subdomain had accumulated meaningful authority that was largely siloed away from the pages that needed to rank. The business had been working hard and producing real output, but the structural decision made early on had quietly undermined the commercial return on that effort.

This is the kind of situation that looks fine in isolation and only reveals itself when you compare it to what the same investment, in a subfolder structure, would have produced. It is the same logic as a business growing 10% in a market that grew 20%. The absolute number looks positive. The relative number tells a different story.

Migrating that content to subfolders took several months, required careful redirect mapping, and caused a temporary dip in traffic before rankings recovered. The recovery was worth it, but the cost of the migration, in time, risk, and resource, was entirely avoidable. The original decision had been made without considering the long-term SEO implications, and someone else had to clean it up later.

How to Migrate From a Subdomain to a Subfolder Without Losing Rankings

If you have content on a subdomain that should be on the root domain, migration is the right move, but it needs to be treated as seriously as any other site migration. Cutting corners here will cost you rankings that take months to recover.

The process follows a clear sequence. First, audit what you are moving. Crawl the subdomain with a tool like Screaming Frog, identify every indexable URL, and document the current ranking positions and traffic for each page. This is your baseline. You need it to measure what happens after the migration and to identify any pages that regress.

Second, map every URL to its new subfolder equivalent before you touch anything in production. The redirect mapping document is the most important artefact in the migration. Every old URL needs a 301 redirect to its new location. Redirect chains, where a URL redirects to another redirect before reaching the destination, dilute the signal transfer and should be avoided. Each redirect should go directly from old URL to new URL in a single hop.

Third, update internal links. Once the content is in its new location, every internal link pointing to the old subdomain URLs should be updated to point directly to the new subfolder URLs. Relying on the redirects to handle internal links is lazy and wastes crawl budget. Update the links at source.

Fourth, submit updated sitemaps to Google Search Console and request re-indexing for the new URLs. Monitor crawl coverage in the days following the migration. Watch for crawl errors, redirect errors, and any pages that fail to get indexed in their new location.

Fifth, keep the redirects in place. Permanently. The instinct to clean up old redirects after six months is understandable but dangerous. External links pointing to the old subdomain URLs will continue to arrive for years. If the redirects are removed, those links stop passing equity. Leave them in place indefinitely.

The Moz guide to presenting SEO projects is worth reading before you take a subdomain migration to stakeholders. The internal sell is often harder than the technical execution, and having a structured way to frame the risk and expected return makes the conversation significantly easier.

Subdomain Authority: What Actually Transfers and What Does Not

One of the most persistent misconceptions about subdomains is that because they share a root domain, they automatically share authority. The reality is more conditional than that.

Internal links between a subdomain and the root domain pass PageRank in the same way that links between any two pages do. If your blog subdomain links to your root domain product pages, those links carry weight. The problem is that the authority accumulated by external links pointing to the subdomain does not flow to the root domain in the same way it would if the content were in a subfolder. The external links build authority for the subdomain as an entity. Internal links from the subdomain to the root domain pass some of that authority, but it is an indirect and less efficient path.

This matters most in competitive categories where you are trying to rank product or service pages against established competitors. If your competitors have built topical authority on their root domains through subfolder content, and you have built equivalent content on a subdomain, you are at a structural disadvantage that content quality alone cannot fully overcome.

I have judged enough Effie Award entries to know that the campaigns that win are rarely the ones that worked hardest. They are the ones that were structured correctly from the start so that the effort compounded efficiently. The same principle applies to SEO architecture. Working harder on content that is structurally disadvantaged is not the answer. Getting the structure right before you invest heavily is.

Subdomains and Local SEO: A Specific Case Worth Examining

Local SEO adds another dimension to the subdomain question. Businesses with multiple locations sometimes consider using subdomains to create separate presences for each city or region, for example london.example.com or manchester.example.com. The intent is to signal geographic relevance to search engines. The execution is usually counterproductive.

The better approach for most multi-location businesses is a subfolder structure with dedicated location pages, for example example.com/london/ and example.com/manchester/, supported by properly configured Google Business Profiles for each location. This keeps the authority consolidated on the root domain while still providing the geographic signals that local search requires.

The Moz local SEO research consistently shows that the fundamentals, accurate business information, location-specific content, and genuine reviews, drive local rankings more than structural choices. A subdomain will not rescue a weak local SEO programme, and a strong programme does not need subdomains to perform.

Where subdomains do appear in local SEO is in franchise and multi-brand operations where different business units genuinely operate as separate entities with separate teams, separate content strategies, and separate marketing budgets. In that context, the separation reflects a real operational reality, not just a structural preference. Even then, the decision should be made with full awareness of the authority implications.

The Subdomain Versus Subfolder Debate: What the Evidence Actually Shows

The SEO industry has been arguing about subdomains versus subfolders for well over a decade. The debate has generated more heat than light, partly because the answer depends on context and partly because Google’s own statements on the subject have been inconsistent over the years.

What the evidence consistently points toward is that subfolder structures tend to perform better for content that is meant to support the ranking of a root domain. Case studies from businesses that have migrated blog content from subdomains to subfolders generally show ranking improvements over the months following migration, once the redirects are in place and Google has re-crawled the new URLs. The improvements are not always dramatic, but they are real and they compound.

The counterargument, that Google is sophisticated enough to treat subdomains and subfolders equivalently, is technically plausible but practically unverifiable. You cannot test it on your own site without running the migration, and once you have run the migration, you cannot reverse it cleanly. The prudent position is to use subfolders for content unless there is a specific technical or operational reason that requires a subdomain.

What I find frustrating about how this debate is often framed is that it distracts from the variables that matter more. Content quality, topical depth, link acquisition, and page experience collectively have a larger impact on rankings than URL structure. Businesses that are losing organic visibility to competitors are rarely losing because of their subdomain setup. They are losing because their content is thinner, their links are weaker, or their pages are slower. Fix those things first.

The broader principles around how structure, content, and authority interact are worth understanding in context. The Complete SEO Strategy hub covers how these decisions connect across a full programme rather than in isolation, which is where most structural decisions go wrong.

Practical Questions to Ask Before Choosing a Subdomain Structure

Before committing to a subdomain for any new content or product area, run through these questions honestly.

Does this content require a genuinely different technical environment? If the answer is yes because it is a web application, a community platform, or a tool that cannot run on the same CMS as the marketing site, a subdomain is justified. If the answer is yes because it is a blog and your developer prefers WordPress while the main site runs on something else, that is a workflow problem, not a technical requirement. Solve the workflow problem differently.

Will this content be used to build topical authority that should benefit the root domain? If yes, it belongs in a subfolder. Content that is meant to rank for informational queries and funnel readers toward commercial pages needs to be on the root domain to transfer its authority efficiently.

Is this a genuinely separate business unit or brand? If the subdomain represents a product or service that operates independently, has its own identity, and is not meant to contribute to the root domain’s rankings, the separation may be appropriate. If it is simply a section of the same business, keep it on the root domain.

What is the migration cost if we get this wrong? If the content is new and has not yet accumulated links or rankings, the cost of choosing the wrong structure is low because there is nothing to migrate. If the content is established and has real organic visibility, the migration cost is significant. Factor that into the decision.

Have you checked how competitors are structured? Not to copy them, but to understand the landscape. If every strong competitor in your category runs their content in subfolders, there is a reason for that. It is worth understanding before you go in a different direction.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions