The subdomain vs subdirectory question decides where your blog, shop, or help center lives: blog.example.com or example.com/blog. Google’s official position, repeated by John Mueller for years, is that both work and the choice is yours. The documented migrations tell a more specific story: sites that consolidate subdomains into subdirectories regularly report organic traffic gains, with several published case studies showing increases of 20 to 40% within months of the move.
This article explains why the two structures behave differently in practice, when each one is the right call, and how to migrate a subdomain into a subdirectory without losing the rankings you have. The decision is cheap to get right at launch and expensive to fix later, so it belongs in your earliest architecture planning.
Why Subdomain vs Subdirectory Still Changes SEO Outcomes
Google treats a subdomain as a separate site in several practical systems, whatever the ranking algorithms do internally. Search Console requires separate properties or a domain-level verification, crawl budget is allocated per host, and quality signals are evaluated with the host boundary visible. A new subdomain starts with less inherited trust than a new folder on an established domain, which is why content on fresh subdomains typically takes longer to rank. Google’s URL structure documentation stays neutral on the host question and focuses on readability and consistency, which is exactly why the practical differences below decide the call.
Subdirectories keep everything on one host. Every article in example.com/blog adds to the same site-level signals that example.com/product pages benefit from, and internal links between them pass equity without crossing a host boundary. The subdomain vs subdirectory choice is really a choice about whether your content marketing and your commercial pages pool their authority or hold it in separate accounts.
The case study record leans one direction. Documented consolidations from companies like Monday.com and several agencies’ published migrations show traffic gains after moving blogs from subdomains into subdirectories, while migrations in the opposite direction are rare enough that almost nobody publishes them. Treat those numbers as directional rather than guaranteed, since each migration also shipped redirects and cleanup that contribute to the lift.
Subdirectories Are the Default for Content That Supports One Site
Choose a subdirectory whenever the content exists to support the main site’s topical authority. Blogs, guides, documentation, and resource libraries all earn links and rankings that should flow into your commercial pages, and a folder structure delivers that flow automatically. This is the same consolidation logic behind planning your URL structure before you build.
Reporting gets simpler too. One Search Console property covers the whole site, one analytics stream tracks the full user journey, and your rank tracker doesn’t split a keyword’s history across hosts. Those sound like small conveniences until you’re debugging a traffic drop across three properties at 5 p.m. on a Friday.
Technical setup is the only real obstacle. Serving a blog from example.com/blog when the blog runs on different infrastructure requires a reverse proxy, and platforms like Shopify or some SaaS help desks don’t support proxying at all. When the proxy is possible, it’s a few hours of nginx or CDN configuration. Cloudflare Workers and similar edge tools have made this practical even when your marketing site and blog run on completely separate stacks.
Four Cases Where a Subdomain Is the Right Call
Subdomains earn their separation when the content genuinely is a different site, which makes the subdomain vs subdirectory call straightforward in a handful of situations. These 4 cases cover most legitimate uses:
- A different product or audience – A developer API portal serving engineers doesn’t need to share quality signals with a consumer marketing site, and separation protects each from the other’s issues.
- User-generated content you don’t fully control – Forums, community wikis, and hosted user pages carry spam risk. A subdomain keeps that risk from bleeding into your money pages, which is exactly why platforms like WordPress.com host user sites on subdomains.
- Infrastructure that can’t be proxied – When your help desk or store platform refuses reverse proxy setups, app.example.com beats a broken folder implementation every time.
- Staging and internal tools – Anything that should never rank belongs on a noindexed subdomain, far from your indexable structure.
Multilingual sites are a special case with their own tradeoffs between subdomains, subdirectories, and country domains. Our hreflang setup guide covers that decision separately, because language targeting adds signals that change the math.
Running multiple WordPress sites under one brand adds network-level considerations on top of the URL question, and our WordPress multisite SEO guide walks through those.
How to Migrate a Subdomain into a Subdirectory Safely
A subdomain consolidation is a standard migration with one extra moving part, the proxy. Follow these 4 steps:
- Map every URL before touching anything – Crawl the subdomain, export all URLs with traffic and backlink data, and write the old-to-new mapping. Every blog.example.com/post must map to example.com/blog/post with no orphans.
- Stand up the proxy and verify rendering – Serve the content at its new path while the old host still works, then check that pages render identically, canonicals point to the new URLs, and internal links use the new structure.
- Ship 301 redirects in one pass – Redirect the entire subdomain host to the new paths in a single deployment, one hop per URL. Partial rollouts create months of mixed signals, and redirect chains leak the equity you’re trying to consolidate.
- Update everything that references old URLs – Sitemaps, internal links, Search Console properties, and your analytics filters all need the new paths. Submit the new sitemap the same day the redirects ship.
Expect 4 to 8 weeks of position wobble while Google reprocesses the URLs, with recovery visible in Search Console as impressions shift from the old property to the new paths. Hold the old DNS and redirects permanently, because backlinks to subdomain URLs keep passing equity only while the 301s stay alive. Sites that follow this sequence routinely come out ahead of where they started, which is the strongest practical answer to the subdomain vs subdirectory question. Run a fresh crawl 30 days after launch to confirm no chains or orphans survived, and the consolidation is done.