utillyUtilly home
How it worksPricingFor WebflowFor WordPress
Log in
How it worksPricingFor WebflowFor WordPressLog in

Subdomain vs. subfolder: what it means for your SEO.

Should the blog live at blog.yourdomain.com or yourdomain.com/blog? This guide covers how search engines treat each structure, the cases where a subdomain is genuinely the right call, and how teams move once they decide.

The short answer: subfolders, for anything meant to rank

subdomainssubfolders
blog.yourdomain.com→ yourdomain.com/blog
docs.yourdomain.com→ yourdomain.com/docs
shop.yourdomain.com→ yourdomain.com/shop

one domain, compounding authority

Backlinks pool in one place
Every link your blog earns at /blog strengthens the domain that your product pages rank on. The same link pointing at a blog subdomain mostly strengthens the subdomain.
One site to crawl and understand
Subfolders keep your content, docs, and shop inside one site structure, so topical relevance builds up on a single host instead of being split across several.
One analytics property
Sessions do not break when a visitor moves from the blog to the pricing page, so attribution finally reflects the real journey.

What search engines actually do

Google's public guidance is that both structures are fine and its systems can handle either. Take that seriously: a subdomain will not get you penalized, and plenty of large sites rank well with them.

But "can handle" is not "treats identically." A subdomain is a separate host: it accumulates its own link equity, gets crawled as its own site, and has to earn trust on its own. That is why the practitioner playbook has been stable for a decade: SEO teams that migrate content from subdomains into subfolders keep reporting consolidated authority and stronger visibility for the main domain. Google disputes the mechanism; the pattern keeps showing up in migration case studies.

The honest framing: a subfolder gives every piece of content the full weight of your domain from day one, and gives your domain the full weight of every link that content earns. A subdomain does neither by default. If the content exists to build your brand and rankings, the structure should let it.

When a subdomain is the right call

The app itself

Dashboards, login screens, and account pages should not rank. We practice this ourselves: the product lives at app.utilly.co.

A genuinely separate brand

A different product for a different audience can deserve its own site, its own authority, and its own subdomain or domain.

Risk isolation

User-generated content and regional or legal separations sometimes need a hard boundary from the main site.

Why teams end up on subdomains anyway

Almost never by choice. The marketing site is on Webflow, the blog is on WordPress, the shop is on Shopify, and none of those platforms can serve a path on a domain that another platform already occupies. A subdomain is the only thing DNS alone can give each platform, so subdomains it is.

The fix is a reverse proxy: one service answers for the whole domain and routes each path to the platform that serves it. /blog goes to WordPress, /shop to Shopify, everything else to the marketing site, and every platform keeps its own editor and hosting.

How a managed proxy worksThe request lifecycle, what is preserved, and how rollback works.Set one up for WebflowThe DIY routes and the managed one, compared honestly.

Subdomain vs. subfolder FAQs

Does Google treat a subdomain as a separate website?

Google says it can understand both structures. In practice, a subdomain earns its own authority: links pointing at blog.yourdomain.com strengthen that host, and the main domain benefits far less than it would if the same content lived at /blog.

Will moving my blog to a subfolder improve rankings?

No one can promise a number, and you should distrust anyone who does. What is well documented: after subdomain-to-subfolder migrations, SEO teams repeatedly report consolidated authority and improved visibility for the main domain, which is why the migration remains standard advice.

Can I lose SEO during the move?

Only if the migration is sloppy. Keep URLs stable where possible, 301-redirect every old subdomain URL to its new subfolder path, update your sitemap, and watch Search Console for crawl errors in the weeks after.

Is app.yourdomain.com a mistake then?

No. Application dashboards, login screens, and other content that should not rank are exactly what subdomains are for. We follow the same rule: this site lives at utilly.co and the product lives at app.utilly.co.

Move to subfolders without a migration project.

Utilly routes each path of your domain to the platform that serves it. One DNS change, and rollback is the same change in reverse.

utilly

One domain for every site you run. Utilly reverse-proxies Webflow, WordPress, and custom apps into subfolders of your main domain.

Product

  • How it works
  • Pricing
  • Webflow Reverse Proxy
  • WordPress Reverse Proxy
  • Framer Reverse Proxy
  • Shopify Reverse Proxy

Learn

  • Subdomain vs. subfolder
  • Webflow proxy setup guide
  • vs. Cloudflare Workers DIY
  • vs. self-hosted nginx

Legal

  • Privacy Policy
  • Refund Policy
  • Terms of Service

Get started

  • Log in
  • Start free trial

© 2026 Utilly. All rights reserved.

utilly.co/*