Blog on a subdomain or in a subfolder: what changes for SEO
Google's documentation doesn't say one ranks better. It does document real differences in hosting, robots.txt, crawl budget and Search Console.

Should the blog live at blog.example.com or at example.com/blog? It is one of the first questions a business asks when it adds a blog, and there are plenty of confident answers online. Google's own documentation is more modest: it doesn't say that either setup ranks better for a blog. It does document practical differences in how a subdomain and a folder are crawled, configured and measured, and those differences are a better basis for the choice.
The two setups
A subdomain is a separate hostname under your domain, such as blog.example.com. You usually create it with one DNS record that points it to wherever the blog is hosted. That can be a different server, a different platform, or a service that hosts the blog for you.
A subfolder, also called a subdirectory, is a path on your main hostname, such as example.com/blog. Either the blog is part of the same website, for example the same CMS, or your server or CDN forwards every request for /blog to another system. That forwarding is called a reverse proxy, and it needs access to your hosting or CDN settings.
What Google's documentation compares
The clearest side-by-side comparison in Google's documentation is in its guide to multi-regional and multilingual sites. It lists the two as ways to give each country or language its own section:
| Subdomain (de.example.com) | Subdirectory (example.com/de/) | |
|---|---|---|
| Pros listed by Google | Easy to set up; allows different server locations; easy separation of sites | Easy to set up; low maintenance (same host) |
| Cons listed by Google | Users might not recognize from the URL alone whether "de" is a language or a country | Users might not recognize the targeting from the URL alone; single server location; separation of sites is harder |
The table was written for country and language versions, so the points about targeting don't apply to a blog. The rest does, and none of the listed pros or cons is about ranking. The trade-off it describes is separation against maintenance: a subdomain can be run as its own site on its own server, while a subdirectory stays on the same host and is simpler to keep together.
Where the two differ in practice
Crawling: each hostname is its own site
Google's crawl budget guide says its crawling infrastructure defines a site as a unique hostname, and that www.example.com and code.example.com are separate sites with separate crawl budgets. A blog on a subdomain is therefore crawled as a site of its own. For most small sites this changes little, because the guide is written for large sites: those with a million or more pages that change about weekly, or ten thousand or more that change daily.
robots.txt: one file per host
A robots.txt file applies only to the host it sits on. Google's robots.txt specification says: "A robots.txt on a subdomain is only valid for that subdomain." A blog on blog.example.com needs its own robots.txt, while a blog in example.com/blog follows the rules in example.com/robots.txt. If your main robots.txt blocks a path by accident, a folder blog inherits the mistake.
Sitemaps
Google's sitemap guide says a sitemap affects only the files below the directory where it is posted, unless you submit it through Search Console, and recommends putting it at the site root. A subdomain blog normally gets its own sitemap at its own root. A folder blog's URLs can go into the main site's sitemap, or into a separate one submitted in Search Console. Google also documents how to cross-submit sitemaps when you run several verified sites.
Search Console
Search Console has two kinds of website property. A Domain property includes all subdomains and protocols, and it is verified with a DNS record. A URL-prefix property includes only URLs that start with a given prefix, which makes it a good way to look at example.com/blog/ or blog.example.com on its own. With a Domain property, a subdomain blog shows up in the same reports as the rest of the site.
Links between the site and the blog
Whatever you choose, the blog only helps if people and crawlers can reach it. Google's link guide says every page you care about should have a link from at least one other page on your site. Put the blog in your main navigation, link from articles to the product or service pages they mention, and use ordinary HTML links in both directions.
What stays the same either way
Most of what decides whether blog articles get found doesn't depend on this choice. Each article needs its own URL that returns the full text, a link from at least one other page and a place in a sitemap. Titles and descriptions need to be specific to each article.
Duplicates need care in both setups. If the same article can be reached at two addresses, for example on a subdomain and in a folder while you test a migration, choose one and point the other to it with a redirect or a canonical tag. Google's guide to canonical URLs says that if you don't state a preference, Google picks the version it considers best on its own, which may not be the one you want.
The setup only decides where the articles live and how they are crawled. Whether they rank depends on whether they are worth reading.
How to choose
A folder is the simpler long-term setup when your site can host it. That is the case if the blog can run inside your existing CMS, or if your site sits behind something that supports a reverse proxy rule. You get one host, one robots.txt and one set of settings to look after.
A subdomain is the practical choice when your site builder doesn't let you forward a path to another system, or when you want the blog on separate infrastructure that your main site doesn't depend on. You will have a second host to keep an eye on, though a Domain property in Search Console covers it.
Ranketto supports both: a subdomain needs one DNS record, and a folder needs one rule in Cloudflare, Nginx, Vercel, Netlify or Next.js, for which we provide the snippet.
If you switch later
Moving a blog from a subdomain to a folder, or the other way, changes every article URL. Each old URL then needs a redirect to its new address. Google's guide to site moves warns that rankings can fluctuate while it recrawls and reindexes a site, and says that for medium-sized sites it can take a few weeks or more before the new URLs gradually replace the old ones in results. That is a real cost, so it is worth picking the setup you can keep before the blog has many articles.
Questions and answers
Does Google rank a blog on a subdomain lower than one in a folder?
Google's documentation doesn't say so. The differences it documents are technical: a subdomain is a separate host for crawling and for robots.txt, and Search Console can cover both setups.
Do I need a separate Search Console property for a blog subdomain?
Not if you use a Domain property, which includes all subdomains. A separate URL-prefix property for the subdomain or the folder is still useful when you want to look at the blog's data on its own.
Will moving my blog from a subdomain to a folder improve rankings?
No Google document promises that. A move changes every URL and needs redirects, and Google warns that rankings can fluctuate while it recrawls the site. Plan a move only if you have another good reason for it.
Sources
- Managing multi-regional and multilingual sites
- Optimize your crawl budget
- How Google interprets the robots.txt specification
- Build and submit a sitemap
- Add a website or platform property to Search Console
- Link best practices for Google
- How to specify a canonical URL with rel="canonical" and other methods
- How to move a site
Read next
4 ways to add a blog to any website, and the trade-offs of each
A subdomain, a folder behind a reverse proxy, a script or a WordPress plugin: how each way of adding a blog works and what it changes for search engines.
hreflang explained: adding languages without duplicate content
When translated pages count as duplicates, what hreflang tells Google, the rules that trip people up, and a minimal example for a site in three languages.
How long does it take for a new article to appear in Google?
Google's own documentation gives ranges from hours to weeks, with no guarantee. What decides the wait, how to check a page, and what you can speed up.