Blog or shop on a subdomain or a subfolder?

Short answer: Google can crawl and rank both, so the choice is mostly practical. If the blog or shop runs on the same system as your main site, a subfolder (example.com/blog) is simpler to maintain and measure. If it runs on a different platform or server, a subdomain (shop.example.com) is often the only clean option, and it works fine when set up properly.

This question comes up whenever a business adds something to its website: a blog on a different CMS, a shop on a hosted platform, a help center from a support tool. SEO forums treat it like a religious war. In practice, the right answer depends on how your site is built and who maintains it.

The two options in one sentence each

Subfolder (subdirectory): the new section lives inside your main domain's path, like example.com/blog/. Same host, same site, one address.
Subdomain: the new section gets its own prefix, like blog.example.com. Technically a separate host that can run anywhere, on any platform.

What Google's documentation actually covers

Google doesn't publish a page saying one is better for rankings. The closest official comparison is in its guide to multi-regional sites, where it lists subdomains and subdirectories as two valid ways to structure country or language versions. It describes subdomains as easy to set up, allowing different server locations and easy separation of sites; and subdirectories as easy to set up and low maintenance because they share the same host, with separating sites being harder.

That guide is about international sites, but the trade-offs it lists apply to blogs and shops too: subdomains give you separation, subfolders give you simplicity.

Trade-offs table

Factor	Subfolder (example.com/blog)	Subdomain (blog.example.com)
Platform	Must run on the same system or behind a reverse proxy	Can run on any platform via a DNS record
Setup	Easy if it's the same CMS; harder if it isn't	Usually a single DNS change
Maintenance	One system, one set of updates	Two systems to update, secure and back up
Design consistency	Shared theme and navigation by default	Has to be matched manually
Search Console	Covered by the main property	Covered by a Domain property; URL-prefix properties need adding separately
Analytics	Simple, one cookie domain	Works, but cookie settings must match to avoid self-referrals
Internal linking	Natural, same menus	Needs deliberate cross-linking
Failure isolation	A problem can affect the whole site	Problems tend to stay contained

The practical issues that actually decide it

Platform reality

Hosted shops, help desks and some blogging platforms connect to your domain through DNS. DNS works at the domain and subdomain level, not the folder level. Shopify's help center, for example, describes connecting a subdomain such as shop.example.com by changing its CNAME record, so you can keep your root domain for another website. Putting a hosted platform in a subfolder instead requires a reverse proxy, which is more technical and may not be supported by the platform, so ask before committing to it.

Measurement

In Search Console, Google says a Domain property includes data for all protocol and subdomain variations, so verifying your domain that way covers www, shop and blog in one place. If you use URL-prefix properties, each subdomain needs its own.

In Google Analytics, use the same measurement ID across subdomains. Google's cross-domain help page warns that when users move between subdomains that use a different cookie domain, self-referrals can appear and traffic can be misattributed, and suggests checking that all subdomains use the same cookie domain.

Content and navigation

A blog on a subdomain often ends up looking like a different website: a different header, no link to services, no route back to "Contact us". That hurts visitors more than any ranking theory. Whichever option you pick, give the new section your main navigation and link generously in both directions.

Moving later

Changing from one to the other later means redirecting every URL. It's doable, but it's work you'd rather avoid, so decide carefully up front.

Recommendation by setup

WordPress site adding a blog: subfolder. It's the same system; there's no reason to split it.
Main site on a website builder, shop on a hosted ecommerce platform: subdomain for the shop, or move the whole site onto the shop platform if it can host your content pages well.
Software product with a help center from a support tool: subdomain such as help.example.com. Separation is useful, and support tools are built for it.
Marketing site plus web app login: subdomain for the app (app.example.com). It's a different system with different security and deployment needs.
Starting from scratch: choose a platform that can host both the content and the shop under one domain, and use subfolders.
Several country sites: follow Google's multi-regional guide; subdirectories and subdomains are both listed as valid options.

FAQ

Will a subdomain "lose" my main site's SEO value?

Google's documentation doesn't say it does. What does matter is that the subdomain is well linked from your main site, has useful content and is included in your Search Console checks.

Can I put my Shopify store at example.com/shop?

Shopify's documented route for using part of your domain is a subdomain via CNAME. Serving it in a subfolder would need a proxy setup outside Shopify's standard domain connection, so check Shopify's current help pages before planning around it.

Do I need a separate sitemap for a subdomain?

Each host usually serves its own sitemap. Submit it in Search Console under your Domain property.

Is www a subdomain?

Yes. www.example.com is technically a subdomain of example.com, which is why choosing one version and redirecting the other matters.

If you're about to add a shop, blog or help center and want the domain setup right the first time, tell us what platforms you're using.