# Blog on a Subdomain or in a /blog Folder? What Google Says (and How to Set Up Both)

Source: https://blog.lots.blog/blog-subdomain-or-subdirectory-what-google-says
Published: 2026-11-06T00:30:29.061423+00:00

Google's own documentation does not say that a blog on a subdomain (blog.example.com) or in a folder (example.com/blog) ranks better. Its SEO Starter Guide says: "From a business point of view, do whatever makes sense for your business." So pick the setup that fits how you run your site, and make sure you can change your mind later.

I'm the founder of LotsBlog, and I support all three setups: a hosted address at {subdomain}.lotsblog.com, a custom domain such as blog.example.com, and a path on your own site such as example.com/blog. Below is what Google actually says (every page opened on 5 November 2026), what does change in practice, and the steps for each setup.

## What Google says about subdomains vs subdirectories

I went looking for a Google page that picks a winner. I did not find one. Here is what the official pages say, quoted exactly.

**1. The SEO Starter Guide: do what makes sense for your business.** In the section "Things we believe you shouldn't focus on" (page last updated 2025-12-10), under "Subdomains versus subdirectories", Google writes:

> "From a business point of view, do whatever makes sense for your business. For example, it might be easier to manage the site if it's segmented by subdirectories, but other times it might make sense to partition topics into subdomains, depending on your site's topic or industry."

That is the whole section. It does not claim either structure ranks higher. Source: [SEO Starter Guide: The Basics](https://developers.google.com/search/docs/fundamentals/seo-starter-guide).

**2. Site names: subdomains are supported, subdirectories are not.** Site names are the name shown above your result in Google Search. The documentation (page last updated 2025-12-10) says: "Site names can appear for domain-level and subdomain-level sites", "Google Search does not support site names at the subdirectory level", and gives the example "Supported: https://news.example.com (this is a subdomain-level home page)" against "Not supported: https://example.com/news (this is a subdirectory-level home page)". So `example.com/blog` cannot have its own site name, while `blog.example.com` can. This is about how the name is displayed, not about ranking. Source: [Site Names in Google Search](https://developers.google.com/search/docs/appearance/site-names).

**3. robots.txt is per host.** Google's robots.txt specification (page last updated 2026-10-23) says that `https://example.com/robots.txt` is "not valid for other subdomains, protocols, or port numbers" but is "valid for all files in all subdirectories on the same host, protocol, and port number", and that "A robots.txt on a subdomain is only valid for that subdomain." In practice: a blog at `blog.example.com` has its own robots.txt, and a blog at `example.com/blog` is governed by the root `example.com/robots.txt`. Source: [How Google Interprets the robots.txt Specification](https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt).

**4. Search Console covers both.** A Domain property "aggregates data for all subdomains, protocols, and subpaths of the property", and Google's help page says that to separate the data you can "Create additional URL-prefix properties for segments of the Domain property". So you can measure a blog on either structure. Source: [Add a website or platform property to Search Console](https://support.google.com/webmasters/answer/34592).

**5. International sites: Google lists trade-offs, not a ranking claim.** In the table of URL structure options for multi-regional sites (page last updated 2025-12-10), subdomains such as `de.example.com` are listed with "Easy to set up", "Allows different server locations" and "Easy separation of sites", and subdirectories such as `example.com/de/` with "Easy to set up", "Low maintenance (same host)", "Single server location" and "Separation of sites harder". That table is about geotargeting, so I would not stretch it to a blog, but it shows how Google frames the choice: set-up and separation, not ranking. Source: [Managing multi-regional and multilingual sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites).

Checked on 5 November 2026. I also tried to open Google's 2008 Search Central blog post "Subdomains and subdirectories" and its YouTube video on the same question; the post is only available in Simplified Chinese and YouTube blocked my request, so I did not use either. I am not making any claim about traffic or rankings in this article: Google's pages don't, and neither will I.

## How people search for this

Google's autocomplete (checked 5 November 2026) completes "blog subdomain" to "blog subdomain vs subdirectory" and "blog on subdomain or subdirectory". The primary source for the answer is the Google documentation above.

## So how do you choose?

Using Google's own framing (what makes sense for your business), these are the practical differences I'd look at:

| | Hosted address | Custom domain | Path on your site |
|---|---|---|---|
| Example | `yourblog.lotsblog.com` | `blog.example.com` | `example.com/blog` |
| Lives on | A subdomain of lotsblog.com | A subdomain of your domain | Your main host, same as the rest of your site |
| What you change | Nothing | One DNS record | One rewrite on your own site |
| robots.txt | The blog's own | The blog's own | Your root `example.com/robots.txt` |
| Site name in Google | Not your domain | Possible (subdomain-level) | Not supported (subdirectory-level) |
| Best when | You want to start now | You want your own domain without touching your main site | You want the blog on the same host as your site |

A subdomain is the easy path if your main site is a separate app or a site builder you don't want to touch. A folder is the neat path if you want one host and one robots.txt, and you can add a rewrite rule. Google's documentation doesn't frame this as a ranking decision.

For what it's worth, I run both myself. LotsBlog's own blog is at a subdomain: [blog.lots.blog](https://blog.lots.blog). LotsTech's other blogs, [lotscrm.com/blog](https://lotscrm.com/blog) and [lots.link/blog](https://lots.link/blog), are served at a path.

## How to set up all three in LotsBlog

You can do each of these from your AI agent (the LotsBlog MCP server or the [REST API](https://blog.lots.blog/lotsblog-rest-api)) or in the dashboard under your blog's Settings, then Custom Domain. The facts below come from the [LotsBlog API docs](https://api.lots.blog/docs.md), section "Blog addresses" and "Blogs served at a path on your site", checked on 5 November 2026.

### Option 1: the hosted address, {subdomain}.lotsblog.com

Every blog gets one. You choose the `subdomain` when you create the blog (3 to 63 lowercase letters, numbers or hyphens, not starting or ending with a hyphen), and the blog lives at `https://{subdomain}.lotsblog.com` until you verify a custom domain or a path. There is nothing to configure.

### Option 2: a custom domain such as blog.example.com

1. Ask your agent to connect the hostname you own with `connect_domain` (REST: `POST /api/v1/lotsblog/blogs/:blog_id/domain`, with `domain` set to `blog.example.com` and no `path`).
2. It returns the exact DNS records: a DNS-only CNAME, plus optional TXT records as a fallback if verification stays pending. You add them at your DNS provider; LotsBlog never needs your registrar login.
3. Ask your agent to run `check_domain`. It reports the domain and certificate status. Once verified, HTTPS is issued for you, canonical URLs, the sitemap and RSS use your domain, and the old lotsblog.com address redirects there with a 301.

`connect_domain` refuses `lots.blog` and `lotsblog.com` hostnames: connect one you own. More on this in [the custom domain page](https://lots.blog/features/custom-domain-blog).

### Option 3: a path on your own site, example.com/blog

1. Ask your agent to call `connect_domain` with `domain` set to `example.com` and `path` set to `/blog`. The path takes lowercase letters, numbers, `-` and `_`, up to three segments, and can't be `/api` or `/_next`.
2. It returns the proxy target, a private proxy secret and copy-ready rules for Cloudflare Workers, Vercel, Next.js, Netlify and Nginx. The rules read the secret from an environment variable named `LOTSBLOG_PROXY_SECRET` (Nginx: an include file), so it never sits in your code. Keep the secret out of any committed file.
3. Add the one rewrite rule for your platform on your own site. My step-by-step for each host is in [How to Host Your Blog at yourdomain.com/blog With LotsBlog](https://blog.lots.blog/host-blog-at-yourdomain-com-blog).
4. Ask your agent to run `check_domain`. For a path setup it fetches `example.com/blog/__lotsblog/subdirectory-check` through your rewrite. `get_blog` then shows `subdirectory` with status `pending` or `verified`.
5. Add the Sitemap line to your root robots.txt. Search engines read robots.txt only at the root of a domain, so use `Sitemap: https://example.com/blog/sitemap.xml`. For the blog's own rules, `get_blog` returns `robots_txt.root_lines`: the same rules with every path prefixed with `/blog`, ready to paste into the root file.

Once it is verified, links, canonical URLs, the sitemap, RSS and llms.txt use `https://example.com/blog`, and the old lotsblog.com address or custom domain redirects to it with a 301 ([the /blog feature page](https://lots.blog/features/blog-at-yourdomain-blog)).

To go back, call `remove_subdirectory` with `confirm: true` (REST: `DELETE /api/v1/lotsblog/blogs/:blog_id/domain/subdirectory?confirm=true`), then remove the rewrite from your site. Canonical URLs return to your custom domain or the `{subdomain}.lotsblog.com` address.

If you are adding the blog to a site you already have, [How to Add a Blog to an Existing Website](https://blog.lots.blog/add-blog-to-existing-website) covers the wider options, and [How to Let AI Crawlers Read Your Blog](https://blog.lots.blog/let-ai-crawlers-read-your-blog) covers robots.txt and llms.txt.

## What it costs

Checked on 5 November 2026 on [lots.blog/pricing](https://lots.blog/pricing): custom domains and path hosting are included with every funded blog, with no add-on fee. Plans cover 3, 10 or 30 blogs for $24, $69 or $159 a month, or you pay $9 per blog per month from credits with no subscription. Posts, page views and authors are unlimited. New users get free credits, no card. Full breakdown in [LotsBlog Pricing Explained](https://blog.lots.blog/lotsblog-pricing-explained).

## FAQ

### Does Google prefer a subdomain or a /blog folder?

The Google pages I opened on 5 November 2026 don't say that either structure ranks better. The SEO Starter Guide says "do whatever makes sense for your business". Site names are supported for subdomains but not for subdirectories, and robots.txt applies per host.

### Can I use my own domain for a LotsBlog blog without touching my main site?

Yes. Connect a hostname you own, such as blog.example.com, with `connect_domain`, add the DNS-only CNAME it returns, and run `check_domain`. Your main site stays where it is.

### How do I put a LotsBlog blog at example.com/blog?

Call `connect_domain` with your site and the path `/blog`, add the one rewrite rule it gives you for your platform (Cloudflare Workers, Vercel, Next.js, Netlify or Nginx), then run `check_domain` to verify it.

### Which robots.txt applies to a blog at example.com/blog?

The root one at `example.com/robots.txt`. Google's specification says a robots.txt is valid for all files in all subdirectories on the same host. Add the Sitemap line `https://example.com/blog/sitemap.xml` there; `get_blog` also returns the blog's rules prefixed with `/blog`.

### Can I move from a subdomain to /blog, or back?

Yes. Connect the path with `connect_domain`, and once it verifies, the old lotsblog.com address or custom domain redirects to it with a 301. To go back, call `remove_subdirectory` with `confirm: true` and remove the rewrite from your site.

### Does the setup cost extra on LotsBlog?

No add-on fee. Custom domains and path hosting come with every funded blog: plans are $24, $69 or $159 a month for 3, 10 or 30 blogs, or $9 per blog per month pay as you go.
