← blog / SEO & GEO

Blog Subdomain vs Subdirectory: The 2026 Answer

·updated ·11 min readseosite-architecturestatic-sitespublishinggeo
Abstract Magic Share brand graphic: a field of dots with a highlighted cluster in green and teal on a near-black grid, with the Magic Share name and the label "seo".

If you are wiring a blog onto an existing marketing site today, put it at yoursite.com/blog. The exception is a stack that cannot serve it there without a proxy layer you would have to own forever; then blog.yoursite.com is a perfectly defensible choice you will not be punished for. Google has said for well over a decade that the two are treated the same, and the case studies back that up more than SEO folklore admits. What has changed in 2026 is a second scoreboard: one audit of 13 client sites found subdirectory pages pulled 2–5x more citations per page from AI engines such as ChatGPT and AI Overviews than subdomain pages. That is a real signal, from a small sample, and it still should not outrank the question of how your blog deploys.

In short:

  • Default to /blog. Google treats both structures the same, and a subdirectory keeps links, crawling and reporting in one place.
  • Accept a subdomain when your platform or deploy setup forces it. The ranking cost is small; a proxy you maintain forever is not.
  • Don't migrate a healthy subdomain for SEO alone. Migration case studies rarely isolate the URL change, and the AI-citation evidence comes from a small sample.

Here is the trade-off, with the parts most guides hand-wave.

What Google has actually said — including the part everyone drops

The official position has barely moved since the George W. Bush administration. In a 2007 post on subdomains and subdirectories, Google's Matt Cutts wrote that "historically, it's been kind of a wash about when to use subdomains vs. subdirectories" — then added his own tiebreaker: "My personal preference on subdomains vs. subdirectories is that I usually prefer the convenience of subdirectories for most of my content."

A decade later, John Mueller said the same thing with the same footnote. Ahrefs quotes him flatly stating that "Google websearch is fine with using either subdomains or subdirectories", and in a May 2018 office-hours session he expanded on it in a line that Search Engine Journal recorded: "In general, we see these the same. I would personally try to keep things together as much as possible." He suggested reserving subdomains for content that is really different from the main site.

Notice what both men did. They said the crawler doesn't care, and then both volunteered a personal preference for keeping things together. That gap is the whole article. Google's equivalence claim is about how a URL gets processed. It says nothing about what a site accumulates over three years of links, crawls, analytics configs and engineering decisions. The processing really is equivalent. The accumulation is not.

What actually differs (and what doesn't)

Strip out the folklore and a short list survives.

Backlink equity doesn't cross the host boundary for free. Bluehost's comparison puts the subdirectory side plainly: "Every external link pointing to a subdirectory strengthens the root domain." Links to a separate host do less for the main site. Picture your one great post getting picked up on Hacker News. On a subdirectory, those links strengthen the domain your pricing page lives on; on a subdomain, they mostly strengthen a host that only ever serves blog content.

Crawl attention gets fragmented. The same comparison warns that if you run several subdomains with thin or infrequently updated content, "Googlebot may deprioritize crawling them." On a 200-page marketing site with a weekly blog, this is a rounding error. On a subdomain that publishes twice a quarter, it is the difference between a post indexed on Tuesday and a post indexed in three weeks.

Third-party metrics score them separately. The same source notes that tools like Moz's Domain Authority and Ahrefs' Domain Rating "typically treat subdomains as separate entities." Those are vendor scores rather than ranking factors — but they are the numbers you'll be staring at when you judge whether the blog is working.

Measurement gets a tax. Google's own Search Console documentation is explicit that a URL-prefix property excludes other hosts: "Subdomains, such as m.example.com, are not included in this URL prefix." A Domain property does cover every subdomain, so this is a chore you can solve. You repeat it in analytics. Google Analytics 4 normally handles self-referrals across subdomains on its own, but Analytics Mania's subdomain tracking guide shows the fix for when it doesn't. Check that your own blog isn't showing up as a referral source and stealing credit for the signup it caused.

What does not differ: your ability to rank a great post. Which brings us to the newer question.

The 2026 variable: AI engines read hosts as entities

The new input is generative search. An analysis published this year tracked 13 client sites from January to March 2026 across ChatGPT search mode, Gemini, Google's AI Mode, Perplexity and AI Overviews, and found subdirectory content cited "2 to 5 times more often per page" than the subdomain equivalents. Its proposed mechanism is the interesting part: "different hosts get treated as different entities, even when they share a registered domain." A large language model (LLM) anchoring on the host string sees docs.acme.com and acme.com as two organizations that happen to rhyme.

The sharpest data point in that write-up is a near-controlled one. A SaaS company kept nearly identical guides at docs.theircompany.com and theircompany.com/docs; over 90 days the subdirectory version earned 11 citations across ChatGPT and Gemini, the subdomain version 2. Same content, same company, roughly 5x the citations. If you are betting on being the source an answer is built from rather than a blue link, that gap is the strongest argument on the subdirectory side of the ledger.

Now the caveat the authors themselves flag: it is a "small sample, far from a peer-reviewed study." The authors also say they cannot swear host structure was the only variable in the docs comparison. Thirteen clients over one quarter is a signal to weigh, not a law to plan around. Citation behaviour in these systems is still driven mostly by page-level craft. That is why our guide to earning citations from ChatGPT and AI Overviews spends its time on extractable paragraphs and named inline sources rather than on hostnames. Treat host consolidation as a tiebreaker that costs you nothing when you are starting fresh.

The honest ranking caveats

If you go looking for proof that subdirectories win, you will find migration case studies. Read them closely and most of them stop proving it.

CognitiveSEO ran the cleanest test on itself: in late June 2017 it moved explorer.cognitiveseo.com to cognitiveseo.com/site-explorer/ and reported no improvement whatsoever — rankings hovered where they had been. The famous HotPads win from February 2014, where John Doherty saw an immediate impact after moving the blog to a subfolder, came bundled with a WordPress replatform, indexation fixes and a low-quality content cull. Iwantmyname moved its blog to a subdomain in July 2014 and traffic dropped, but the recovery after reversing it couldn't be cleanly attributed either.

Ahrefs made the structural version of this critique after examining Mention.com's 2016 migration and finding minimal direct impact — the traffic gains arrived later, when the company added substantial new content. Their list of confounders is the one to keep: migrations usually ship alongside better internal linking, content edits, tracking changes, platform redesigns and indexation fixes, any of which could carry the result.

The practitioner consensus lands in a sensible place. Eric Enge notes that "Google is pretty good at seeing a subdomain as being an integrated part of the main domain," recommending subfolders for new content while cautioning against moving established blogs purely for SEO. Cyrus Shepard grants that "empirical evidence shows that oftentimes, moving content (such as a section blog living on a subdomain) to a subfolder often results in increased visibility, rankings, and traffic," then adds that "many sites go through expensive migrations to see no benefit whatsoever."

Translation for a founder: on a fresh blog, pick the subdirectory because it's free to pick. On a three-year-old subdomain with real backlinks, the SEO case alone does not clear the bar.

The engineering difference is bigger than the SEO difference

Here is the part that rarely makes it into SEO guides: the cost lands on whoever is on call.

The most useful public account of subdomain regret comes from the team behind Clubhouse (now Shortcut), who called their per-organization subdomain architecture "a mistake worth rewriting a lot of code for". Their reasons were entirely operational. Google requires a domain whitelist for OAuth (the sign-in-with-Google protocol), which makes wildcard domains awkward. Extended Validation certificates can't be assigned to a wildcard like *.clubhouse.io. And every environment needed its own URL-parsing code path. Moving the org slug into the path, so app.clubhouse.io/myorgname/stories instead of myorgname.clubhouse.io/stories, deleted all three problems at once. That's an app-architecture story rather than a blog story, but the failure modes rhyme: each additional host multiplies certificate, cookie, auth and environment configuration.

Cutting the other way, your platform may simply make the choice for you. A HubSpot-hosted blog sits most easily on a HubSpot-connected subdomain. Serving it at a subfolder of a site hosted elsewhere means a reverse proxy, and HubSpot documents one such route: a reverse-proxy switch in its WordPress plugin that maps HubSpot content to a WordPress path. GitHub Pages lets only one repository claim a given custom domain. As one reply in that thread puts it, "only one repository at a time can be associated with a given custom domain." Project repos can still appear at yoursite.com/project, but only under the custom domain of your account's GitHub Pages user or organization site. If your main site is hosted anywhere else, a GitHub Pages blog can't sit at its /blog.

If you do want /blog on a separately built site, three documented paths exist, in ascending order of what they cost you:

  1. One app, one deploy. If the blog lives inside your existing Next.js app, setting basePath in next.config.js prefixes your routes, and next/link applies it to links automatically (next/image sources need the prefix added by hand). The value is set at build time and inlined in the client bundles, so decide before you ship.
  2. Two deploys, one rewrite rule. On Vercel you can keep two projects and rewrite /blog paths to the blog deployment from the main project's vercel.json. Kevin Goedecke's write-up documents the config, and a reader comment under it reports trouble with deeper nested subfolders.
  3. A reverse proxy you now maintain. A Cloudflare Workers proxy with HTMLRewriter can fetch the blog's HTML and rewrite href, src, link and meta values so nothing leaks the origin host, plus 301s from the old domain. It works, and the same write-up warns that the blog template and CORS (cross-origin resource sharing) can add complexity.

Option 3 is a permanent piece of infrastructure that sits between users and every blog post you publish. If your answer to "who fixes this at 2am" is "me, and I also do sales," that cost is real and it recurs. It is the same convenience argument Cutts made in 2007, when he noted that content in a subdirectory is easier to find, edit and move.

The decision rule

Four questions, in order:

  1. Can your current stack serve /blog without a new proxy layer? If yes, subdirectory. Done — you just took the SEO tiebreaker and the AI-citation tiebreaker for free.
  2. Does your platform forbid it? A HubSpot blog beside a non-WordPress site, a GitHub Pages blog beside a main site hosted elsewhere, and several managed blog products default to subdomains. Constraint beats preference; ship the subdomain and move on.
  3. Is a separate team, stack or security boundary involved? Subdomains give real isolation, which is why enterprises with distinct brands and independent content teams keep them. A two-person SaaS almost never has this problem.
  4. Are you migrating an established, ranking subdomain? Then weigh it separately. Practitioner guidance on subdomain-to-subdirectory moves is a 2–4 week traffic dip while 301s are processed and full recovery within 4–6 weeks. A well-run blog migration checklist makes that predictable, though not painless: map every old URL, 301 each one, update internal links, submit fresh sitemaps and watch Search Console daily for the first few weeks. Do it when you have another reason to touch the stack, not because a blog post told you to.

Most founders reading this land on option 1 within about ninety seconds, which is the point: this decision deserves ninety seconds, not a week.

What actually decides whether the blog works

An empty subdirectory ranks worse than a subdomain that publishes every week. The URL structure works at the margins; cadence and depth do most of the work. The choice usually feels heavy because it's the last decision before the hard part starts.

That hard part is where Magic Share fits. Point the agent at your site, it builds a brand profile from your pages, researches a topic, and holds the draft until you approve it. The agent checks every cited link before handing the draft over and attaches a verification report, because a post full of dead citations damages you regardless of which host serves it. If your blog lives in a repo, the agent opens a GitHub pull request and merging it is the publish step, which pairs neatly with the pull-request review workflow for Astro and Next.js blogs we've written up separately. Whichever structure you chose, the posts land in it on a schedule you set. Our look at how often a small blog should publish explains why a cadence you can hold at full depth beats a burst you can't.

Consider running a link rot audit: your blog's dead outbound links to discover broken citations, prioritize fixes, and protect the authority of posts your agents cite.

FAQ

Is a subdomain bad for SEO? No. Google has treated the two as equivalent since at least 2007; the real differences are link consolidation, crawl attention and measurement overhead, not a ranking penalty.

Should I move my blog from a subdomain to a subdirectory? If the blog is new, yes, because the move is cheap. If it has years of backlinks and rankings, the SEO case alone is thin, so bundle the move with a replatform you were doing anyway.

Do subdirectories really get more AI citations? One small 2026 audit of 13 sites found 2–5x more citations per page for subdirectory content. Treat it as a tiebreaker; page-level structure still drives citations more than hostnames do.

How do I serve a separately deployed blog at /blog? Use basePath inside one Next.js app, a vercel.json rewrite to a second project, or a reverse proxy such as a Cloudflare Worker. The proxy works but adds a permanent component to your critical path.

Does a subdomain need its own Search Console property? Not if you use a Domain property, which covers every subdomain at once. A URL-prefix property for https://example.com/ won't report on blog.example.com.

The short version

Pick the subdirectory when your deployment allows it, accept the subdomain without guilt when your platform or your team structure demands it, and don't migrate a healthy ranking subdomain on SEO grounds alone. The evidence for subdirectories is real but modest, and consistent publishing will move your results far more.

Once the structure is settled, the bottleneck is drafting, sourcing and fact-checking every week. Start with three free posts and see what a verified draft looks like before you commit to a cadence.

More on SEO & GEO →

by email

Get new posts in your inbox

A short digest when new posts go up. Confirm once, unsubscribe from any email.

We use your address only for this digest. Privacy

Keep reading

  1. ·12 min read

    Does llms.txt Help SEO? Google's Answer, and What Next

    Google Search ignores llms.txt and says so in writing. Here's what the data shows about who actually reads the file, and when it's still worth shipping.

    seogeoai-agentsllms-txtstatic-sites

  2. ·16 min read

    How to Write a Fair SaaS Competitor Comparison Page

    How to write a competitor comparison page for SaaS that names rivals fairly, sources every claim, and converts — with the evidence and update cadence.

    content-strategyseosaas-marketingcomparison-pagesgeo

  3. ·18 min read

    Link Rot Audit: Your Blog's Dead Outbound Links

    Publish-time link checks expire. A link rot audit for your blog's outbound links: decay rates by source type, how citations die, and a rule for each.

    seolink-rotcontent-maintenancefact-checkingpublishing

Want posts like this for your site?

Magic Share researches, writes and fact-checks posts like this for any site — point it at your URL and review your first draft today.

Plant your first post