Subdomain or subfolder for SEO? What Google says, how crawling, authority and Search Console differ, when a subdomain makes sense, and how to migrate safely.

In short
Google says it treats subdomains and subfolders roughly the same, but a subfolder (example.com/blog) is the safer default because every link, page and signal reinforces a single site. A subdomain (blog.example.com) is crawled as a separate site with its own crawl budget and has to earn its own visibility through links from the main domain. Use a subdomain only when the content runs on a different platform, serves a different audience or must stay technically isolated.
Want to go further? Ask
The subdomain vs subfolder SEO debate comes back every time a company launches a blog, a store, a help center or a new language. Google's own position is relaxed: asked about it in 2018, John Mueller of Google answered "In general, we see these the same", while adding that he "would personally try to keep things together as much as possible" (Search Engine Journal, May 2018). This guide explains what changes in practice, case by case.
Both are ways to organize a section of a website, at two different levels of the URL:
| Criterion | Subfolder (example.com/blog) | Subdomain (blog.example.com) |
|---|---|---|
| Technical setup | Same host and usually same CMS | DNS record, can run on another server or platform |
| Crawling | Shares the crawl budget of the main site | Treated as a separate site with its own crawl budget |
| Links and authority | Every backlink strengthens the whole domain | Must be connected to the main site through links |
| Internal linking | Natural, one navigation | Requires deliberate cross-links |
| Search Console | Included in the main property | Included in a Domain property, separate in a URL-prefix property |
| Maintenance | One site to monitor | Two sites: sitemaps, robots.txt, audits |
| Best for | Blog, guides, categories, languages | App, separate platform, distinct audience, user spaces |
Google has never announced a ranking penalty for subdomains, and its public statements point the same way: both structures can rank. Three official facts matter more than opinions.
Google's crawl budget documentation states that "Google's crawling infrastructure defines a site as a unique hostname", and gives the example of two subdomains of the same domain that are treated as separate sites with separate crawl budgets. For most sites this is neutral; for a site with hundreds of thousands of pages, it changes how crawling is shared.
According to Search Console Help, a Domain property "aggregates data for all subdomains, protocols, and subpaths" and is verified through DNS, while a URL-prefix property only includes URLs that start with the exact prefix. With a Domain property, blog.example.com and example.com appear in the same reports; with URL-prefix properties, you need one per subdomain.
John Mueller's 2018 advice, as reported by Search Engine Journal: keep related content together as much as possible, and use a subdomain when the content is truly different from the rest of the site. Google's explanation of how search engines work also shows why: Google has to understand that two hostnames belong to the same entity, and links are its main clue.
Google may "see these the same", but the mechanics of SEO favor the subfolder in most situations:
Many published case studies describe traffic gains after moving a blog from a subdomain to a subfolder. They are encouraging but anecdotal: a migration often comes with other improvements, so the gain cannot be attributed to the URL structure alone. Our guide to domain authority explains how these third-party scores are calculated and why they are not a Google metric.
A subdomain is the right choice when keeping the content in a subfolder would be technically difficult or would mix two different products.
| Use case | Typical URL | Recommendation |
|---|---|---|
| Web application or customer area | app.example.com | Subdomain, usually blocked from indexing |
| Help center on a dedicated platform | help.example.com | Subdomain acceptable, link it from the main site |
| Hosted store on another platform | shop.example.com | Subdomain if no reverse proxy is possible |
| User-generated spaces | username.example.com | Subdomain, isolates each user's content |
| Staging or test environment | staging.example.com | Subdomain, password-protected |
| Blog or guides | example.com/blog | Subfolder |
| Languages and countries | example.com/fr/ | Subfolder in most cases |
Software companies are the typical example: the marketing site, the blog and the documentation belong in subfolders, while the product itself lives on app.example.com. Our page on SEO and GEO for SaaS companies details this split.
A subfolder, almost always. The blog is where you earn links and answer the questions your buyers ask; you want that authority on the domain that sells. If your blog runs on a separate CMS, a reverse proxy can serve it under example.com/blog without moving the platform. On WordPress, the blog sits in a subfolder by default (see our WordPress SEO and GEO guide).
Google's guide to managing multi-regional sites compares the options. Subdirectories are "easy to set up" and "low maintenance (same host)"; subdomains are also easy to set up, allow "different server locations" and make separation of sites easier. URL parameters are not recommended. For most companies, example.com/fr/ with hreflang tags is the simplest structure to run. Our international SEO guide covers the full choice, including country domains.
If your e-commerce platform can run on the main domain, use subfolders for categories and products. If it imposes a subdomain, accept it and compensate with strong cross-linking: links from the blog to categories, from the home page to the store, and a consistent header across both.
Moving blog.example.com to example.com/blog is a migration in its own right. Follow the same discipline as any SEO migration:
Expect a few weeks of fluctuation. A drop that lasts usually points to missing redirects or lost content.
ChatGPT, Gemini and Perplexity cite URLs, and the hostname is part of what readers see in the citation. When your guides live in a subfolder, every citation displays your main domain and reinforces the brand that sells. On a subdomain, the same citation can look like a separate site. Whatever the structure, the same rules apply as in classic SEO: crawlable pages, links between sections, and authority built over time. A domain authority tracker shows how that authority evolves, and Sorank's backlink acquisition obtains natural backlinks automatically from its network of 5,000+ users.
Choose a subfolder by default, and a subdomain only for a separate product, platform or audience. If you already run a subdomain that works, link it tightly to the main site before considering a migration. Then put your energy where rankings are decided: content and links. Sorank publishes optimized articles directly in your blog subfolder on autopilot, with internal links to the pages that sell.
Not automatically in the way a subfolder does. Google crawls a subdomain as a separate site, so its pages benefit from the main domain mainly through the links between the two. Strong cross-links, a shared navigation and a Domain property in Search Console help Google connect them.
No. Google has said it generally treats subdomains and subfolders the same, and many subdomains rank well. The drawback is practical: signals and links are split between two sites, which makes a subdomain slower to grow when it hosts content that could have lived on the main domain.
Subfolders such as example.com/fr/ are the simplest option for most sites: one host, low maintenance and authority shared across languages. Subdomains or country domains make sense when each market needs a separate server, team or platform. In every case, add hreflang tags between equivalent pages.
THEY TRIED SORANK BEFORE YOU
