Subdomain or subfolder and why the debate refuses to die
Should the blog live at blog.example.com or example.com/blog? The question is old enough to have grandchildren, and it still starts arguments because the two most quotable sources disagree. Google has said for years that both structures work fine. A noticeable number of practitioners, having migrated a subdomain into a subfolder and watched traffic climb, politely decline to believe them.
What each side actually claims
Google's position is consistent: its systems can figure out that a subdomain and a root domain belong together, and neither structure is inherently penalized. That claim deserves to be taken seriously, and on well-linked, established properties the difference may genuinely be negligible.
The practitioner case is built on migration case studies. Content moved from a subdomain into a subfolder of a strong root domain frequently performs better after the move. The usual explanation is that search engines can treat subdomains as semi-independent sites, so a subdomain does not automatically inherit the full authority of the root. Signals like links and topical relevance consolidate more reliably inside one host than across two.
Both things can be true at once. Google may handle subdomains correctly in principle, while in practice a specific subdomain with its own thin link profile behaves like the separate site it technically is.
A practical decision rule
The structure should follow the relationship between the content and the main site.
Same brand, same audience, content meant to support the main site's visibility: subfolder. Blogs, guides, help centers, and shops belong here in most cases.
Genuinely different product, audience, or purpose: subdomain (or separate domain) is legitimate. A community forum, a status page, an app with its own life.
Technical necessity: sometimes the platform hosting the blog or shop cannot sit in a subfolder without a reverse proxy. A subdomain is a reasonable price for shipping, and a proxy can be revisited later.
International sites: subfolders per language or country are the lower-maintenance choice for most businesses. Country subdomains are workable; separate country domains are the expensive option that splits authority the most.
If a migration is on the table
Moving an established subdomain into a subfolder is a real site migration with everything that implies. One-to-one 301 redirects for every URL, updated internal links, updated sitemaps, and a period of volatility while everything reprocesses. The upside seen in case studies is real but not guaranteed, and it rarely arrives overnight.
Measurement is the part most write-ups skip. Annotate the migration date, keep both properties verified in Search Console, and compare the combined clicks of old and new locations against the pre-migration baseline rather than staring at either one alone. Redirected URLs bleed impressions for weeks while the new ones ramp up, and judging the move during that overlap window produces panic that the twelve-week view usually dissolves. If the combined line has not recovered after a full quarter, something more specific than the structure is wrong, and the redirect map is the first place to look.
It is also worth saying the quiet part: structure is not strategy. A weak help center will not start ranking because it moved into a subfolder, and a strong one on a subdomain is not doomed. The consolidation question matters at the margin, and the margin is worth having, but content and links still decide the game. Pick the structure that matches the relationship, migrate carefully if migrating at all, and spend the remaining energy on the pages themselves.