Subdomain or subfolder for your blog

Ten minutes into planning a company blog, someone asks the question that has kept SEO forums busy for fifteen years: should it live at blog.yoursite.com or at yoursite.com/blog?

Here is the honest answer, including the part most articles on this topic skip: why so many teams end up on a subdomain even when they wanted the subfolder.

What Google actually says

Google's position has been consistent for years: it can crawl, index, and rank both. Google's John Mueller put it plainly: "Using subdomains or subfolders doesn't make any difference to Google."

The same Ahrefs analysis makes a second point worth keeping: the famous "we moved to a subfolder and traffic doubled" case studies almost never isolate the move itself. Sites that migrate usually fix internal linking, prune dead pages, and refresh content in the same project, so the structure change cannot be credited alone.

So no, there is no secret ranking bonus for subfolders. The real differences live one level down.

Where the real differences are

Interconnection is not automatic. A subdomain only benefits from your main site's authority if the two are actually linked together. As Ahrefs notes, subdomains that are not interlinked with the main site can be treated as separate sites. A subfolder never has this problem, because there is nothing to connect: it is the same site.

You maintain two properties in practice. A subdomain means a second thing to configure everywhere: its own Search Console view, its own analytics setup, often its own deployment and SSL story. None of this is fatal. All of it is friction that a subfolder simply does not have.

Links you earn concentrate in one place. Every mention of a subfolder post points at your main domain. With a subdomain, you are asking Google to understand a relationship instead of just seeing one site with one internal link graph.

The practical summary: pick the subfolder when you can. Not because Google hands out a reward, but because it removes an entire class of questions you would otherwise have to keep answering.

So why do so many blogs end up on subdomains?

Because of engineering, not strategy.

Your main site is usually an application: a Next.js app, a Rails app, a storefront. Mounting a CMS inside it at /blog means routing rules, build pipeline changes, and a dependency your product team now owns forever. Creating blog.yoursite.com, by contrast, is one DNS record and zero risk to the main app.

That is how the decision really gets made at most companies. The structure that is best for content loses to the structure that is easiest to deploy, and everyone quietly agrees not to reopen the topic.

Getting the subfolder without rebuilding your site

This trade-off is exactly what BeeRanked removes. Your content section is written and managed in BeeRanked, and served under any path of your own domain, yoursite.com/blog, /resources, /learn, whatever fits. Your main application is not touched: depending on your stack it is a single reverse proxy rule, a connector, or a small self-hosted agent.

The result is the structure you wanted on day one: one domain, one link graph, one property, with the blog running on its own infrastructure. We wrote more about that setup in Keep your website, grow your traffic.

If your blog already lives on a subdomain

Do not panic-migrate. First, interlink generously in both directions, from your main navigation to the blog and from posts back to product pages, so the two are clearly one entity. If you do decide to move, keep the path structure identical where possible and 301 every old URL to its new home, the same discipline we describe in Keep your rankings when URLs change. And set your expectations honestly: the move consolidates your setup and your future links, it is not a traffic cheat code.

Choose the structure once, choose the simple one, and get back to publishing. The posts you ship are worth more than the URL scheme they live under.