Should a Small Business Blog Live on a Subdomain or in a /blog Folder? (2026)
Should a small business blog live on a subdomain or in a /blog folder?
For most small businesses, put the blog in a folder on the main site (yoursite.com/blog), unless your blogging platform forces a subdomain. Google's John Mueller has said the two are "essentially equivalent" and that the choice depends on which is easier for your infrastructure, so there is no magic ranking bonus either way. The folder is simply less to manage: one site, one robots.txt, one sitemap and one Search Console view. This guide was checked on 2026-11-09 and ends with a 4-question test.
PilotaSEO is a done-for-you SEO blog service that writes SEO posts for your site and publishes them automatically. Where the blog lives on your domain is a decision you make before posts start going out, so it is worth settling first.
What does Google actually say about subdomain versus subfolder?
Google says either works. In a Google Webmaster Central office-hours session, Mueller answered the claim that subfolders are superior for SEO by saying the options are essentially equivalent, that you can do many things on both, and that you could even use a different domain name, so it is "essentially up to you."
A later interview summarised by GrowTraffic adds the nuance: Google tries to work out what belongs to the site, and if it decides a subdomain is part of the same website it treats it that way. Mueller would not say how an SEO could tell whether a subdomain was being treated differently, which is why many practitioners still default to a folder. A related Search Engine Roundtable report quotes Mueller saying it does not matter whether posts sit under /blog or at the root, and that SEO myths on this point are wrong.
Google's URL structure documentation says nothing about subdomains ranking differently; it asks for a crawlable structure and descriptive URLs. Our guide to blog post URL slugs covers what matters in the path itself.
What changes in practice between the two?
A subdomain behaves like a separate property for crawling and reporting even when Google may treat it as the same site for ranking. A folder shares everything with the main site by default.
| Item | Folder (/blog) | Subdomain (blog.) |
|---|---|---|
| robots.txt | One file at the site root | Its own file; Google says one on a subdomain is only valid for that subdomain |
| Sitemap | One sitemap at the root can cover the blog | A separate sitemap on the subdomain |
| Search Console | Covered by the same property | Covered by a Domain property; a URL-prefix property for the main site does not include it |
| Hosting and CMS | Same system as the site, or a path rule | Can run on a different platform |
| Internal links | Plain links within one site | Plain links across two hosts |
Google's Search Console help says a Domain property includes all subdomains and multiple protocols, while a URL-prefix property matches only the prefix you enter, so check which kind you have set up. Google's sitemap documentation says that unless you submit a sitemap in Search Console, a sitemap only affects descendants of its parent directory, which is another reason one root sitemap is simpler.
When is a subdomain the right choice?
When the blog has to run on a different platform, with different permissions or a different team, than the main site. A small business that sells through a hosted store builder, for example, may only be able to run a blog elsewhere, and a subdomain is a legitimate way to do that.
- Different platform: your main site cannot serve a /blog path.
- Separate team or access: writers must not touch the main site.
- A distinct product or audience: the content is not about the main business.
Worked example: a plumber's site is built on a hosted page builder that cannot add a /blog path. The owner can either run the blog on a subdomain such as blog.example-plumbing.com, or switch the whole site to a platform that serves /blog. The first takes an afternoon and adds a second robots.txt, sitemap and set of reports to remember. The second is a bigger job with redirects but leaves one site to manage. Neither choice is wrong; the better one is the one the owner will still maintain in a year.
If none of those apply, a folder keeps things simple. Either way, link the blog posts to your service pages with descriptive anchors; see internal linking from a blog to service pages.
The 4-question blog location test
Answer four questions in order, and stop at the first "yes" that points to a subdomain. If you reach the end with no "yes", use a folder.
- Can your main site serve a /blog path? If not, a subdomain is the practical option.
- Is the blog about the same business and customers? If yes, a folder keeps the topic together.
- Will you maintain two sets of robots.txt, sitemap and analytics? If that is more than you want, use a folder.
- Could you redirect later if you move? A move needs 301 redirects from every old URL, which Google documents in its redirects documentation; avoiding a move is easier than doing one.
The same logic applies when you plan clusters; our topic clusters guide for small business blogs assumes the blog and service pages share a site.
How does this fit a done-for-you blog?
PilotaSEO publishes through a signed webhook on your site that you authorize once, and each subscription covers one site and one content language. Decide the location first, then authorize publishing for that site; plans are Autopilot at €322/yr and Growth at €8,250/yr, billed yearly in EUR, and nobody can honestly guarantee rankings, including us. See the PilotaSEO plans for what each includes.
If your blog already lives on a subdomain, do not move it just because of this page. A move is a project with redirects, and Google says either structure is fine. Move only if the subdomain causes a real maintenance problem.
FAQ
Is a subdomain bad for SEO?
No. Google's John Mueller has said subdomains and subfolders are essentially equivalent from Google's point of view. A subdomain mainly adds maintenance, such as a separate robots.txt and sitemap, so choose it only for a practical reason.
Does a /blog folder help my main site rank?
Google has not said it gives a ranking bonus. A folder keeps the blog under the same host as your service pages, which makes it easier to link, report and manage. Rankings still depend on the content and the search query.
Can I move my blog from a subdomain to a folder?
Yes, but it needs a 301 redirect from every old URL to its new one, plus updated internal links and a new sitemap. Google documents permanent redirects in its Search Central redirects guide. Do it only if there is a real reason.
Do I need a separate Search Console property for a subdomain?
Not if you use a Domain property, which Google's help says includes all subdomains. A URL-prefix property only includes the exact prefix you enter, so a subdomain would need its own.
Sources
- Google Webmaster Central office-hours hangout (John Mueller on subdomains and subdirectories) (checked 2026-11-09)
- Google Search Central: robots.txt specifications (checked 2026-11-09)
- Search Console Help: Add a website property (checked 2026-11-09)
- Google Search Central: Build and submit a sitemap (checked 2026-11-09)
- GrowTraffic: Learnings from Distilled's interview with John Mueller (checked 2026-11-09)
- Search Engine Roundtable: Google on blog folders in URLs (checked 2026-11-09)