Publishing Platforms · Explainer

Blog subdomain vs subfolder vs hosted blog: which to choose

Part of the guide How to auto publish blog posts on any CMS (2026 guide)

Put your blog in a subfolder (example.com/blog) if you can set up a reverse proxy, and on a subdomain (blog.example.com) if you cannot. Google says to "do whatever makes sense for your business", so neither is penalised, but a subfolder keeps one site, one site name and one Search Console view. Avoid publishing long term on an address you do not own.

What is the difference between a subfolder, a subdomain and a hosted blog address?

The difference is who owns the address and how the blog joins your site. A subfolder is a path on your main domain, a subdomain is a separate host under your domain, and a hosted address is a path on the blogging platform's domain.

Option Example Who owns the address Setup Counts as the same site as your homepage?
Subfolder example.com/blog/ You Reverse proxy or blog on the same platform Yes
Subdomain blog.example.com You One DNS record Treated as its own site for some features
Hosted address platform.com/b/your-blog/ The platform None No

If your blog already lives on the same CMS as your site (a WordPress site with a WordPress blog, or a Shopify store with its built-in blog), you already have a subfolder and this choice does not apply. It matters when the blog runs on a different system from the main site, which is common when a marketing site is built in one tool and articles are published by another. The publishing routes themselves are compared in our guide to automatic blog post publishing.

Does Google prefer a blog subfolder or a subdomain?

No. Google's SEO starter guide says: "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."

So the choice is about operations, not a ranking rule. Google's documentation does show three practical places where a subdomain is treated as a separate site:

  • Site names. Google's site names documentation says "a site is defined by the domain or subdomain" and that "Google Search does not support site names at the subdirectory level." A blog on blog.example.com can get its own site name in results; one at example.com/blog shares the main site's.
  • Search Console. A Domain property "includes all subdomains", while a URL-prefix property includes only URLs with that prefix. If you verify only ` as a URL prefix, a subdomain blog is not in that report.
  • Moving later. Google's Change of Address tool is only needed "when moving from one domain or subdomain to another", not for moving paths within the same domain. Moving a blog from a subdomain to a subfolder is a site move with redirects; renaming a folder is a simpler URL change.

You will read claims that subfolders "pass more authority". Google does not say that, and we have no data of our own that shows it, so we do not repeat it. The defensible reasons to prefer a subfolder are the ones above: one site, one property, fewer moves.

When does a subdomain make more sense?

Choose a subdomain when a subfolder is not possible without engineering help you do not have, or when the blog really is a separate publication.

Good reasons:

  • Your main site runs on a builder that cannot proxy a path, and nobody can set up a Cloudflare Worker or Nginx rule.
  • The blog covers a different audience or topic from the product and you want its own site name in results.
  • Different teams own the two sites and need separate deploys and permissions.

Weak reasons: "it was the default" or "it was quicker this week". A move later costs redirects, a recrawl and a period of noise in your reports, so pick the address you can keep for years.

How do you put a blog in a subfolder with a reverse proxy?

A reverse proxy makes example.com/blog/ fetch pages from the blog's real host and serve them as if they were part of your site. Visitors and crawlers only see your domain.

The general steps on any stack:

  1. Pick the path, usually /blog.
  2. Add a rule on your main site's edge or server: requests to /blog and /blog/* are forwarded to the blog host, everything else is untouched.
  3. Pass the original path through, and make sure redirects from the blog host do not bounce visitors to the blog's own domain.
  4. Check that canonical tags, the sitemap and RSS links on the blog use example.com/blog URLs, not the blog host's URLs.
  5. Test with curl as a normal browser and as a search bot. Both should get a 200 with the full article in the HTML.

Common places to add the rule are a Cloudflare Worker, an Nginx location /blog block, or rewrites in a Next.js or Vercel config. If the proxy is in place but the canonical tags still point at the blog host, Google may index the blog host's URLs instead of yours, so step 4 matters as much as step 2.

How does the Postbing hosted blog handle each option?

The Postbing hosted blog supports all three addresses, so you can start without a CMS and move to your own domain later.

Postbing option Address What you configure
Path address (default) www.postbing.com/b/your-blog/ Nothing
Custom domain or subdomain blog.example.com or example.com A TXT record named _postbing (or _postbing.<subdomain>) holding a token, then a CNAME to cname.vercel-dns.com, or for a root domain an A record to 76.76.21.21. On Cloudflare, set the record to DNS only. HTTPS is set up, "usually within one business day"
Subfolder example.com/blog/ A reverse proxy (snippets for Cloudflare Worker, Nginx and Next.js or Vercel) that sends the header X-Postbing-Proxy: 1, then save the "Folder address"

Whatever address you pick, the blog serves posts with canonical tags and Article JSON-LD, plus its own sitemap.xml, robots.txt, RSS feed, llms.txt and llms-full.txt. Postbing pings IndexNow when a post is published or unpublished, with the key file served inside the blog's own folder, which is where IndexNow expects it for URLs under that folder. Branding covers the blog name, description, author name, logo, brand colour and a choice of three typefaces.

The canonical address follows a fixed order: a verified custom domain first, then the folder address, then the path address. So when you add your own domain later, canonical tags switch to it. We have not confirmed that old path URLs redirect automatically, so if you plan to use your own domain, set it up before you publish much.

Which option should you pick?

Pick the most permanent option you can set up this month. In order of preference for most small businesses:

  1. Subfolder if someone can add a proxy rule, or if your CMS already has a blog.
  2. Subdomain if a proxy is not realistic. It takes one DNS record and keeps the address yours.
  3. Hosted path address only to try things out, or while you wait for DNS. Content published there builds an address on someone else's domain.

Whichever you choose, connect the matching property in Search Console (a Domain property covers every subdomain at once) and submit the blog's sitemap. If you would rather send articles into a site you already run, the webhook route works with custom stacks, and Shopify stores can use their built-in blog.

FAQ

Is a blog subdomain bad for SEO?

No. Google says to do whatever makes sense for your business. A subdomain is treated as its own site for site names and URL-prefix Search Console properties, which is a management difference, not a penalty.

Why do people recommend a subfolder for a blog?

Mainly for operations: one site name, one Search Console property, shared navigation and internal links, and no site move later. Claims that subfolders pass more authority are not stated in Google's documentation.

Can I move my blog from a subdomain to a subfolder later?

Yes, but it is a site move. You need a 301 redirect from every old URL to its new URL, updated canonical tags and sitemaps, and some patience while Google recrawls.

Do I need a developer for a reverse proxy?

Usually you need someone comfortable with Cloudflare Workers, Nginx or your hosting's rewrite rules. The rule itself is short; most of the work is testing canonicals, redirects and caching.

Can I start on the Postbing hosted address and switch to my own domain?

Yes. Add a custom domain or folder address at any time and canonical tags switch to it. Set your own domain up early, because automatic redirects from the old path address are not confirmed.

Sources

Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.

Try Postbing free

Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.

Try Postbing free

No card needed. No link exchanges, ever.