WordPress,
Shopify,
Wix, Webflow and Ghost. Any other site, hosted on your own domain →Put the blog at yoursite.com/blog if your platform allows it. That is the short answer to the subdomain vs subdirectory question for blog SEO, and it is the same answer Backlinko, Moz and most working SEOs give. Google has said both work. People who have actually run the migration mostly report the subdirectory winning in practice.
The trouble is that every article covering that theory assumes you have a free choice. If your site runs on Wix, Squarespace, Shopify, Webflow or an AI builder like Lovable or Bolt, the platform often decides for you. So this article covers the evidence briefly, then the part the theory pieces skip: what each platform actually allows, what the workarounds cost, and when a subdomain is the sensible compromise.
Subdomain vs subdirectory: the blog SEO evidence in brief
First, the terms. A subdirectory (also called a subfolder) is a path on your main site: yoursite.com/blog. A subdomain is a separate host under your domain: blog.yoursite.com. To a visitor they look almost identical. To Google they are not quite the same thing: a subdomain can be crawled, evaluated and to some degree treated as its own site.
Google's official position, repeated by John Mueller over the years, is that both setups are fine and Google Search can work with either. That is true, and it is also not the whole story. Google saying it can handle something is not the same as both options performing equally for a small site with modest authority.
The migration write-ups lean one way. The domain registrar iwantmyname published one of the most cited accounts: after moving its blog from a subdomain to a subdirectory, organic search traffic to the blog content rose noticeably and stayed up, with no other changes made. GitHub ran the experiment in reverse, moving its blog off the main domain onto a subdomain, and its blog content lost search visibility; it later moved the blog again. Backlinko's own comparison piece collects several similar cases, and they point the same direction.
The likely mechanism is simple. Your homepage and service pages earn links and trust over time. Content in a subdirectory sits inside that trust from day one. Content on a subdomain has to earn more of it independently, which is slow for a small business site that gets a handful of links a year.
Rule of thumb: choose the subdirectory when your platform makes it easy or even moderately awkward. Choose a subdomain when the realistic alternative is not blogging at all. The gap between the two setups is far smaller than the gap between publishing and not publishing.
What your platform actually allows
This is the decision most owners are really facing. Not "which is better in theory" but "which is possible on the platform I already pay for". Here is the honest picture.
| Platform | Blog in a subdirectory? | How | Cost and effort |
|---|---|---|---|
| WordPress | Yes, natively | Posts live at yoursite.com/blog (or any path you set) out of the box | None |
| Shopify | Yes, natively | Built-in blog at yoursite.com/blogs/news; the /blogs/ prefix is fixed and cannot be removed | None |
| Webflow | Yes, natively | A CMS Collection published at /blog on your own site | Requires a CMS-capable plan |
| Squarespace | Yes, for its own blog | Add a Blog page at any path, such as /blog. An external blog tool cannot be proxied in; that would need a subdomain | None for the native blog |
| Wix | Yes, for its own blog | Wix Blog publishes at /blog on the same site. No reverse proxy support for anything external | None for the native blog |
| Ghost (hosted) | Not directly | Ghost(Pro) serves on a domain or subdomain; a subdirectory needs a reverse proxy you run yourself | An hour or two for someone technical, ongoing maintenance |
| Lovable, Bolt, v0, Cursor | Yes, with work | No blog exists at all by default. Options: build one in code, use a rewrite rule on your host (Vercel and Netlify support this), or point a subdomain at a blog service | Free to cheap, but someone must configure it |
A few notes on the rows that trip people up. Shopify's fixed /blogs/ prefix bothers some owners, but it is still a subdirectory and it performs like one; do not move a Shopify blog to a subdomain to get a prettier URL. On Wix and Squarespace the native blog is fine for SEO purposes, and the real limitation is publishing workflow rather than URL structure; our guide to adding a blog to a Wix or Squarespace site covers both routes. Webflow's CMS handles the subdirectory case well, and our Webflow blog setup guide walks through keeping it publishing once it exists.
The AI builders are the interesting case. A site built with Lovable, Bolt or v0 usually launches with no blog whatsoever, so you are choosing between three amounts of effort rather than two URL structures. We wrote up the options in adding a blog to a site you built with Lovable, Bolt or v0.
The reverse proxy option, in plain English
A reverse proxy is a routing rule on your domain that quietly fetches pages from another server and serves them under your own address. Your blog might physically live on a blogging service somewhere else, but visitors and Google both see yoursite.com/blog. One site, one pool of authority, no migration ever needed.
In practice it looks like this. On Vercel or Netlify, it is a few lines in a config file called a rewrite. On Cloudflare, it is a Worker or a routing rule on the free tier. The direct cost is usually nothing. The real cost is competence: someone has to set it up, make sure the blog's sitemap is reachable through the proxy, and not break it during the next redesign.
If you have a developer, or you are the founder who built the site yourself, this is an hour of work and clearly the best option. If the words "DNS record" make you want to close this tab, it is not worth paying an agency day rate for; take the subdomain instead.
When a subdomain is the pragmatic choice
A subdomain is the right call in three situations. Your platform cannot proxy and its native blog does not suit you. Nobody available can safely configure a rewrite. Or you simply want to be publishing this week rather than next month.
Two things soften the compromise. A brand new site has little accumulated authority for a subdirectory to inherit anyway, so the penalty is smallest exactly when you are most likely to take it. And the move from subdomain to subdirectory later is a well understood migration: page-by-page 301 redirects, an updated sitemap, and patience. The published case studies are mostly stories of that exact move going well.
Worked example: a plumber on Squarespace should use the built-in blog at /blog and stop thinking about this. A founder with a Lovable site on Vercel should spend the hour on a rewrite rule. A shop owner on Wix who wants an external blog engine should take the subdomain, publish consistently, and revisit the structure in a year.
Where Helio SEO fits in
Helio SEO publishes natively into the blogs on WordPress, Shopify, Webflow and Ghost, and for everything else, including AI-built sites, it offers managed hosting on your own domain through a single DNS record or routing rule, which is the reverse proxy approach described above, set up for you. If your platform already gives you a subdirectory blog and you are happy writing for it, you do not need us for this decision; the table above is the whole answer.
