Subfolder vs Subdomain for Blogs: Which Setup Is Better for SEO and AI Discovery?

If you're setting up a blog for your business — or migrating an existing one — one of the first architectural decisions you'll face is deceptively simple-sounding: should your blog live at yoursite.com/blog or blog.yoursite.com?

It feels like a minor technical detail. It isn't. This decision affects how Google crawls your site, how your domain authority accumulates, how AI tools like ChatGPT and Perplexity discover and cite your content, and ultimately how much organic traffic your blog actually drives.

This guide breaks down everything you need to know — including what's changed now that LLMs have become a significant source of referral traffic.

The Basic Difference

A subfolder (also called a subdirectory) places your blog under the root domain:

yoursite.com/blog/post-title

A subdomain creates a separate hostname:

blog.yoursite.com/post-title

From a user perspective, both work fine. From a technical and SEO perspective, they behave very differently.

How Google Treats Subfolders vs Subdomains

When your blog lives at yoursite.com/blog, Google treats all pages — your homepage, product pages, and blog posts — as part of a single domain. Every backlink your blog post earns, every page authority it builds, feeds back into the root domain and vice versa.

This is a significant advantage. If your main site has strong domain authority because of years of inbound links, your blog immediately inherits that authority the moment it's published. A new blog post on a strong subfolder can rank faster than the same post on a fresh subdomain.

Crawl budget also works in your favour. Google allocates crawl budget per domain. With a subfolder setup, Googlebot crawls your entire site under one budget, making it more likely that new blog posts get indexed quickly — especially if your main site is already being crawled frequently.

Subdomains are technically distinct hostnames. While Google has stated it can associate subdomains with root domains in some contexts, in practice it largely treats blog.yoursite.com as a separate entity from yoursite.com.

This means:

• Domain authority does not automatically transfer
• Your blog starts with a weaker authority baseline
• Backlinks earned by the blog help the subdomain, not the root domain

• Crawl budgets are split
• Internal linking between the main site and blog carries less weight

For an established business blog, this fragmentation is often the hidden reason why blog content underperforms despite being well-written and well-optimised.

While Google hasn't published a definitive study, SEO practitioners consistently observe subfolder blogs outperforming subdomain blogs in head-to-head tests on comparable domains. John Mueller of Google has acknowledged multiple times that subfolders make it "easier" for Google to associate content with the main domain — though he's careful to say subdomains can work too.

The practical industry consensus: subfolders are the safer, stronger default for SEO.

Technical SEO Implications

With a subfolder setup, canonical URL management is straightforward. All your canonical tags point to variations of the same root domain, and there's no risk of accidental cross-domain canonicalisation. Your XML sitemap covers everything from one location. Your robots.txt controls crawl access for the entire site from one file.

With subdomains, you need separate configurations for each. A separate XML sitemap for the blog subdomain. A separate robots.txt. Separate Search Console properties. For teams without a dedicated technical SEO resource, this overhead compounds over time — and mistakes (like accidentally blocking the blog subdomain in robots.txt) are harder to catch.

Internal links are one of the most powerful signals for distributing page authority across a site. Links from high-authority pages to newer pages help them rank faster.

When your blog is on a subfolder, links from your homepage, product pages, and other high-traffic pages to blog posts carry full internal link equity. When the blog is on a subdomain, those same links are technically cross-domain links and pass reduced equity — behaving more like external links than internal ones.

This is particularly consequential for long-tail blog content. A product page linking to a related blog post on a subfolder gives that blog post a measurable ranking boost. The same link to a subdomain blog post provides a fraction of that benefit.

If you're implementing schema markup — Article, BlogPosting, BreadcrumbList, FAQ — it's significantly easier to maintain consistency when all content lives on the same domain. Search engines can better understand entity relationships when structured data shares a root. Some CMS platforms and SEO tools that automatically generate schema do so at the domain level, and subdomain setups can cause gaps or duplicate entity definitions.

A well-configured blog CMS handles schema markup automatically on every post — Article schema, author schema, breadcrumb schema — without requiring manual implementation. This is one area where the choice of publishing platform matters as much as the subdomain vs subfolder decision.

The AI Discovery Dimension

This is where the conversation has shifted meaningfully in the last two years. SEO is no longer purely about Google rankings. A growing share of discovery happens through AI tools — ChatGPT, Perplexity, Google's AI Overviews, Claude, Gemini — and these tools index, cite, and summarise web content differently from traditional search crawlers.

Large language models are trained on web crawls and updated via retrieval-augmented generation (RAG) systems that continuously index the web. When a user asks ChatGPT or Perplexity a question, the system looks for content that is:

• Clearly structured — headers, logical hierarchy, clean HTML

• Authoritative — associated with a trusted, well-linked domain
• Entity-clear — unambiguous about who wrote it, what organisation it represents, what topic it covers
• Fresh — recently published or updated, with visible freshness signals
• Summarisable — containing a clear thesis, TL;DR, and direct answers to specific questions

This is directly relevant to the subdomain vs subfolder question. When an LLM crawls blog.yoursite.com, it sees a distinct entity from yoursite.com. The trust signals, author profiles, and entity relationships established on your main domain don't automatically transfer. Your blog has to build its own credibility from scratch in the eyes of the AI crawler.

With a subfolder, the LLM sees blog content as part of the same entity as the rest of your domain — benefiting from whatever trust and entity clarity your main domain has established.

A new discipline is emerging alongside SEO: Answer Engine Optimisation (AEO) — structuring content specifically to be retrieved and cited by AI systems.

AEO best practices include:

• Including a TL;DR summary at the top of each post
• Writing in question-and-answer format where possible
• Using FAQ sections at the end of posts
• Making entity references explicit (linking to authoritative sources, including author bios with credentials)
• Ensuring clean, minimal HTML so AI crawlers can parse content without noise
• Using freshness signals (publication and last-updated dates prominently displayed)

None of these practices are incompatible with a subdomain — but they're significantly harder to implement consistently at scale without tooling that handles them automatically. Modern blog CMSs increasingly handle AEO-oriented formatting natively, generating TL;DRs, FAQ structured data, and entity markup without manual effort per post.

One nuance that's become relevant: you may want different crawl rules for different AI bots. Some businesses want ChatGPT to cite their content but not to train on it. Others want to allow Perplexity but block GPTBot.

Managing this is easier on a single domain with one robots.txt. On a subdomain, you need a separate robots.txt for the blog — and if that file isn't correctly maintained, you risk either blocking AI crawlers you want or allowing ones you don't.

Migration Considerations

If you're currently on a subdomain and considering a move to a subfolder (or vice versa), the migration needs to be handled carefully.

This is the more common migration direction for businesses that started with blog.yoursite.com and want to consolidate SEO signals.

Key steps:

1. Set up the subfolder structure on your main domain
2. Migrate all content with matching URL slugs where possible
3. Implement 301 redirects from every old subdomain URL to the new subfolder URL
4. Update your XML sitemap to include the new URLs
5. Update all internal links across the main site
6. Submit the updated sitemap to Google Search Console
7. Monitor crawl errors and ranking changes for 60–90 days

The authority transfer from 301 redirects is not immediate and not 100%. Expect a ranking dip of 2–6 weeks before recovered rankings stabilise. Do not migrate without ensuring redirects are in place before decommissioning the old subdomain.

This is less common but occasionally necessary — for example, if the main site is on a platform that can't support blog content natively, or if there are technical reasons to keep systems separate.

The same redirect logic applies in reverse, but the SEO consequences are more negative: you're explicitly fragmenting authority you've already built. This should be a last resort, not a preference.

When a Subdomain Might Still Make Sense

Despite everything above, there are legitimate use cases for subdomains:

1. The main site is on a platform that can't support a blog If your main site is a complex web app, an e-commerce platform, or a SaaS product where adding a /blog path isn't technically feasible without significant engineering work, a subdomain can be the practical choice. A dedicated blog platform on a subdomain — with strong technical SEO foundations — is significantly better than no blog at all.

2. The blog is a genuinely separate product Some companies run blogs that are editorially distinct from their main brand — different audiences, different voice, different purpose. In these cases, a subdomain (or even a separate domain) might make brand sense.

3. Multilingual sites with regional subdomains For international SEO, some organisations use country-code subdomains (us.yoursite.com, de.yoursite.com) and place blog content under each. This is a separate architectural question from the one this article addresses.

Outside these scenarios, defaulting to a subfolder is almost always the right call.

The Platform Question

The subdomain vs subfolder decision is often made by default rather than by choice — and the choice is frequently driven by what your CMS or hosting setup makes easy.

WordPress installations, for instance, can support either structure but default to /blog paths when properly configured. The challenge is that maintaining technical SEO hygiene on a WordPress blog — schema, canonical URLs, sitemap updates, robots.txt, Core Web Vitals — requires a combination of plugins, manual configuration, and ongoing maintenance.

Newer dedicated blog CMSs are designed to abstract all of that away — handling canonical URLs, schema markup, sitemaps, robots.txt, AEO formatting, internal linking suggestions, and IndexNow submission automatically on every publish, regardless of whether you're on a subfolder or subdomain. This removes the operational overhead that makes subdomain setups feel attractive (because they're easier to isolate technically).

The bottom line: if your platform makes it easy to run a well-optimised blog on a subfolder, do that. If your platform's limitations are what's driving you toward a subdomain, it may be worth reconsidering the platform first.

The Verdict

For most businesses, subfolder wins — clearly.

If you're starting fresh — choose a subfolder. If you're already on a subdomain and your blog is underperforming — a migration to a subfolder, done carefully, is almost always worth the short-term disruption.

The blog is too important a growth channel to let an architectural default silently undermine it.