Nomlen logo

Subdomain vs Subdirectory vs Separate Domain: The SEO Decision

Subdomain vs subdirectory vs separate domain: what Google actually says, what migration data shows, and how to pick the right structure for your site.

NO
Nomlen
Nov 10, 2026·14 min read
Published November 10, 2026
Updated October 2026
Subdomain vs Subdirectory vs Separate Domain: The SEO Decision
nomlen
14-minute read
Share

Three addresses, one decision

Every growing website hits the same fork in the road. You start a blog, a help centre, a shop, or a second language — and you have to put it somewhere. Three addresses are on the table: a subdirectory (yoursite.com/blog), a subdomain (blog.yoursite.com), or a completely separate domain (yoursiteblog.com). The choice looks cosmetic. It is not. It decides how Google understands the relationship between your pages, how your analytics and Search Console are set up, and how much a future migration will cost you.

The short version: for most sites, a subdirectory is the right default. But "most" is doing a lot of work in that sentence, and the exceptions are real. This guide covers what Google actually says, what the migration data actually shows, and a framework you can apply in five minutes.

The three structures, defined

A subdirectory (also called a subfolder) is a path on your existing domain. Your blog lives at yoursite.com/blog, your docs at yoursite.com/docs. Same domain, same hosting setup, same robots.txt, one Search Console property.

A subdomain is a separate hostname in front of your domain: blog.yoursite.com, app.yoursite.com, uk.yoursite.com. Technically it is a different site. It can point at a different server, run a different CMS, and needs its own Search Console verification, its own sitemap, and its own analytics configuration.

A separate domain is a new registration entirely: yoursiteblog.com or a country-code domain like yoursite.co.uk. It shares nothing with your main domain — no authority, no analytics, no Search Console history. It is a fresh start, for better and for worse.

Nomlen itself uses the subdirectory pattern: this post lives at nomlen.com/blog/subdomain-vs-subdirectory-seo, and the tools live at paths like nomlen.com/domain-whois-checker. That is a deliberate choice — and the reasons for it are the subject of this post.

What Google actually says

Google's official position is blunt, and worth quoting in full because it is the sentence most articles misrepresent. From Google Search Central's documentation on site structure: "You should choose whatever is easiest for you to organize and manage. From an indexing and ranking perspective, Google doesn't have a preference."

John Mueller, Google's Search Advocate, has repeated the same point for years in Search Central hangouts: "In general, we see these the same." But the fuller quote matters more than the headline. In the same answer he added: "I would personally try to keep things together as much as possible. So if it's the same site then try to put them on the same site, essentially, and use subdomains where things are really kind of slightly different."

Note the word "personally". That is a preference for operational simplicity, not a statement that subdirectories rank better. There is a deeper nuance, too: there is no blanket rule at all. Google decides per site whether a subdomain is treated as part of your main site, based on integration signals — internal linking between the section and the root, consistent branding and user experience, thematically related content, and a coherent sitemap structure. Gary Illyes confirmed the flip side at Pubcon 2023: subdirectories can be treated as separate sites too. The structure you pick is a hint, not a verdict.

One more official data point: Google's site-reputation-abuse policy, updated in November 2024, made clear that moving content between subdomains, subdirectories and separate domains does not fix a spam violation. If a section was demoted for hosting low-quality third-party content, shuffling the URL structure changes nothing.

What the data actually shows

Google's official neutrality and what practitioners observe are two different things, and an honest guide has to hold both. The gap is real — but narrower and messier than the "subdirectories always win" version of the story.

Backlinko's widely cited analysis of 11.8 million Google search results found that subdirectories consistently outrank subdomains, particularly for competitive keywords. The mechanism is not a secret penalty. A new subdomain starts its ranking life at zero authority: it does not inherit the trust your root domain has built, however strong that domain is. A subdirectory page inherits it from day one.

The case studies point the same way. IWantMyName, a domain registration service, moved its blog from iwantmyname.com/blog to blog.iwantmyname.com in July 2014 — and documented a 47% drop in organic traffic after the move. G2, a software review site, moved its blog to the subdomain learn.g2.com and, according to Jakub Rudnik, former managing director of SEO at GrowthX AI, it took months for Google to build trust in the new subdomain despite G2's considerable existing authority.

But the counter-argument deserves equal airtime. Patrick Stox, writing for Ahrefs in 2021 and updating the analysis since, argues that the famous migration case studies are almost always confounded: teams that moved from subdomain to subdirectory also improved internal linking, pruned thin content, or upgraded their CMS at the same time. The traffic jump gets credited to the URL change when the other changes did at least some of the work. His advice is blunt: don't migrate for URL structure alone, because the risk usually outweighs the upside.

Both sides are right. Subdirectories have a real, structural advantage in how authority flows — and individual migration stories overstate how much of a traffic jump the URL change alone caused. The practical conclusion: choose the subdirectory when you can, but don't tear up a working subdomain on the strength of a case study alone.

Subdomain vs subdirectory vs separate domain: head to head


Subdirectory
Subdomain
Separate domain
Example
yoursite.com/blog
blog.yoursite.com
yoursiteblog.com
Authority
Inherits the root domain's authority from day one
Starts at zero; must earn its own trust
Starts at zero; fully independent
Search Console
Covered by the main property
Needs separate verification
Needs a separate property
Analytics
One setup, one view
Needs cross-hostname configuration
Entirely separate tracking
SSL
Covered by the main certificate
Needs a wildcard certificate or its own
Needs its own certificate
Hosting
Same server and stack as the main site
Can live on a different server or platform
Anywhere
Best for
Blogs, help centres, resource hubs
Apps, regional sites, different products
Separate brands, country sites, defensive registrations

When a subdomain is the right call

Subdirectories win the default. Subdomains win the exceptions — and the exceptions are common enough that most large sites use both:

  • The section is a different product. Your app lives at app.yoursite.com because it is a different application, often on a different stack, with its own login and uptime requirements. Nobody expects your web app to inherit your marketing site's SEO, and it should not share its infrastructure.
  • It needs a different platform. Your help centre runs on Zendesk, your community on Discourse, your store on Shopify. Those platforms serve content from subdomains naturally, and forcing them behind a subdirectory requires a reverse proxy — real engineering work with real failure modes. If the content's job is support rather than search traffic, the subdomain is fine.
  • It targets a different region or language. Regional sites like uk.yoursite.com or de.yoursite.com are a legitimate subdomain use — though country-code domains are often the stronger choice, as our guide to ccTLDs vs gTLDs explains.
  • It must be isolated. A status page (status.yoursite.com) or a staging environment belongs on a subdomain, because isolation is the point. If your main site goes down, your status page should not go down with it.
  • The content is genuinely a different thing. This is Mueller's own test. A developer API reference, a jobs board, or a user-generated community is not "the same site" in any meaningful sense. Put it on a subdomain and invest in it as its own property, with strong internal links back to the main site.

Notice what is not on this list: "because the blog platform suggested it". A blog's entire job is usually to bring search traffic to the main site. Parking it on a subdomain is the single most common structural SEO mistake on the internet — and it is made, over and over, because a subdomain is what the blogging tool offered by default.

When a separate domain wins

A separate domain is the most expensive option in SEO terms — you start from zero and stay at zero until you earn links — so it needs a reason stronger than structure. Three reasons qualify:

  • It is a different brand. A second product with its own name, positioning and audience deserves its own domain. Forcing it under your main domain muddies both brands. Check availability first with a search across all TLDs — the right name is worth more than the convenience of a subdirectory.
  • Regional targeting with a country-code domain. A .co.uk or .de domain is the strongest geographic signal you can send Google, stronger than any subdomain. If a market matters enough to build for, it matters enough to register properly. See our ccTLD vs gTLD comparison and the full TLD list for what is available.
  • Brand protection. Registering the obvious variants of your brand — common misspellings, the other TLDs, the hyphenated version — is cheap insurance against impersonation and typo-squatting. These domains do not need content; they redirect to your main site. Our brand protection guide works through which variants are actually worth the fee.

What does not qualify: launching a second domain because your main domain has a penalty or a spam problem. Google's November 2024 site-reputation-abuse policy closed that door explicitly — moving content to a new domain does not wash away a violation, and a fresh domain with no history is a worse starting position, not a better one.

The five-minute decision framework

Run each new section through these questions in order. The first "yes" decides it:

Question
If yes
Is this a different brand, product or company?
Separate domain
Does it target a specific country as its primary market?
Country-code domain (or a regional subdomain if budget is tight)
Does it run on a different platform that cannot live on your stack?
Subdomain — and link it tightly to the main site
Must it stay up when the main site is down?
Subdomain (status pages, critical services)
Is the content's job to bring search traffic to your main site?
Subdirectory — blogs, guides, resource hubs
None of the above, just organisation?
Subdirectory, always

Two worked examples. A SaaS company adding a blog, a help centre and a changelog: all three are subdirectories — their job is to feed the main site's authority and convert its visitors. The same company adding a login-gated web app and a status page: both subdomains, because both are different things with different infrastructure needs.

Migrating without losing your rankings

If you already have a blog on a subdomain and the framework above says it should be a subdirectory, the move is worth doing — carefully. The risk is real: every changed URL is a ranking that has to be re-earned. Keep the damage small:

  • Map every URL one-to-one. Every old subdomain URL gets a 301 redirect to its exact new subdirectory equivalent. No redirecting everything to the homepage — that throws away ranking signals page by page.
  • Keep the redirects live for at least a year. Google needs months, not days, to transfer signals. Removing redirects early is the most common way a careful migration still fails.
  • Update every internal link. Links from your main site to the subdomain should point at the new subdirectory URLs. Better internal linking is part of why consolidated sites perform better, so do it properly.
  • Update sitemaps and Search Console. Submit the new subdirectory sitemap under your main property and remove the old subdomain sitemap. Search Console's Change of Address tool is built for domain-to-domain moves, not for folding a subdomain into a subdirectory — this migration runs on redirects and sitemaps, not a one-click tool.
  • Expect turbulence, then measure. Rankings typically wobble for a few weeks while Google re-crawls and re-assigns signals. Judge the move at 60–90 days, not day seven. If traffic has not recovered by then, the problem is usually a broken redirect or a missed internal link, not the structure itself.
  • Do not migrate and redesign at the same time. If rankings drop, you need to know whether the URL change or the redesign caused it. One change at a time keeps the diagnosis honest.

And the reverse move — subdirectory to subdomain — deserves a harder look. Unless the section is becoming a genuinely different product, there is no SEO reason to do it, and the IWantMyName case shows what the cost can be: a 47% traffic drop that took months to unwind. If a platform vendor tells you the move is required, ask what the reverse-proxy option costs first.

The decision in one paragraph

Google says the structures are equivalent, and Google is describing its own crawling accurately. What the official line leaves out is everything around the crawl: authority flows cleanly through subdirectories and has to be rebuilt from scratch on subdomains and separate domains; subdirectories cost nothing extra to operate; and every migration carries real risk. So the default is a subdirectory, the exception is a subdomain for things that are genuinely different, and a separate domain is for different brands and country markets. Make the decision once, deliberately — then spend your energy on the content, which is what actually ranks.

Frequently asked questions

Does Google prefer subdirectories over subdomains for SEO?

Officially, no. Google Search Central's documentation says: "From an indexing and ranking perspective, Google doesn't have a preference." Search Advocate John Mueller has said "in general, we see these the same." In practice, though, subdirectories inherit the root domain's authority immediately while a subdomain starts from zero, and large-scale analyses — including Backlinko's study of 11.8 million search results — find subdirectories ranking better, especially for competitive keywords.

Will moving my blog from a subdomain to a subdirectory improve rankings?

Often, but not always, and not for the URL alone. Documented migrations show traffic gains after consolidation, but those migrations usually also improved internal linking and content quality at the same time. Expect a few weeks of ranking turbulence first, and judge the result at 60–90 days. Don't migrate on the strength of a case study alone — migrate because the section's job is to feed your main site.

Do subdomains hurt SEO?

No — there is no penalty for using a subdomain. Wikipedia's language editions live on subdomains (en.wikipedia.org) and rank at the top of results. The cost of a subdomain is opportunity, not punishment: it must earn its own authority, it needs separate Search Console verification, and it splits your analytics. For apps, regional sites and status pages that trade-off is correct. For a blog, it usually is not.

Is a separate domain better than a subdomain?

For SEO, no — a separate domain is the weakest starting position of the three, because it shares nothing with your main site. It is the right choice only when the section is a genuinely different brand or a country-targeted site on a ccTLD. Never launch a separate domain to escape a penalty: Google's November 2024 site-reputation-abuse policy states explicitly that moving content does not fix a spam violation.

Can I use a subdirectory if my blog runs on a different platform?

Yes, with a reverse proxy — your server fetches the platform's content and serves it from your subdirectory. It is the standard solution for running WordPress, Ghost or a headless CMS behind a subdirectory on a site hosted elsewhere. The alternative is accepting the subdomain and its authority cost. Weigh the one-time engineering work against the permanent SEO cost.

How long does it take Google to recognise a subdomain as part of my site?

There is no fixed period. Google decides per site, based on integration signals: internal links between the subdomain and the root, consistent branding, related content and a coherent sitemap. Strong integration helps; a subdomain with no links from the main site and different branding may be treated as a separate site indefinitely. There is no switch to flip — only signals to strengthen.

Should my shop be a subdomain or a subdirectory?

If the shop sells your products and its job is to convert your site's traffic, a subdirectory (yoursite.com/shop) keeps its product pages inside your domain's authority. If the shop runs on a platform like Shopify that cannot live on your stack, a subdomain is the pragmatic choice — or a separate domain if the store is a distinct brand. Either way, link the shop and the main site to each other prominently.

Does the choice affect my domain name?

Not the name itself — but it should affect how you pick one. If your plan is a subdirectory structure, a single strong, brandable .com covers everything, and you can check its availability across all TLDs with Nomlen's domain search. If you expect regional sites or a second brand, register the matching ccTLDs and variants early — they are far cheaper before someone else takes them.

Share
RC
Written by
Ram Chauhan
Founder, Nomlen

Ram builds Nomlen's domain tools and writes these guides — registrar pricing, renewals, TLDs and naming, with every price and claim checked against live registrar data before it ships.

Writes about
Domain pricingRenewalsTLD guidesNaming