Subdomain vs subfolder for SEO: which to use

The short answer

A subfolder sits inside your main domain, such as example.com/blog/. A subdomain is a separate hostname, such as blog.example.com. For most small and medium sites, a subfolder is the simpler choice because the content shares one site, one set of reports and one structure. Use a subdomain when the section is run separately.

The difference in plain terms

A domain such as example.com can be split in two ways. A subfolder adds a path after the domain: example.com/blog/ or example.com/services/. A subdomain adds a word before it: blog.example.com or shop.example.com.

From a visitor's view, both look like part of the same brand. From a technical view, they differ. A subfolder is part of the same host as the rest of the site, served by the same set-up. A subdomain is treated as its own host. It can run on different software, a different server or even a different company's platform, and it has its own robots.txt file and its own set of settings.

That technical independence is the real distinction. It makes subdomains flexible and also makes them easier to isolate, which is a help when a section really is separate and a drawback when it is not.

Does Google treat subdomains differently?

Google can tell that a subdomain and its root domain are related, and its documentation does not say that one structure always ranks better than the other. In places, though, a subdomain is treated as its own site. For example, Google's guidance on site names in search says a site is defined by its domain or subdomain, and that site names are not supported at the subdirectory level.

In Search Console, you can verify a whole domain at once, which covers all subdomains, or verify a subdomain on its own. Reporting then differs in how it groups the data.

For ranking, the honest position is this. Claims that subfolders always win, or that subdomains always lose, are not supported by anything in Google's documentation. What does happen in practice is that content on a subdomain can take effort to connect with the rest of the site, because links, reports and signals are managed separately. Treat the choice as a practical one first.

If you want the current wording, check Google's documentation on site structure and Search Console property types, since reporting options change over time.

Where should a blog live?

For most business sites, the blog belongs in a subfolder, for example example.com/blog/. Three reasons are practical.

• Your articles link naturally to your service pages and back, with ordinary internal links. See our guide to search intent for how informational articles should lead to commercial pages.
• You run one site, one sitemap, one analytics set-up and one set of reports.
• Everything you publish builds one place that visitors and search engines can understand as a whole.

A blog on a subdomain is not wrong. It is common when a company uses a separate publishing platform that cannot sit under the main domain, or when a different team runs it. The cost is the extra work of connecting it: consistent navigation, links in both directions and separate monitoring.

Decide early, because the choice is awkward to reverse. Put the blog where the business will want it in five years, not where it is easiest to launch this week.

When a subdomain makes sense

The rule behind the table: if the content serves the same audience and the same purpose, keep it together. If it is a separate product with its own login, platform or team, separation is reasonable.

Online stores often raise this question. A shop on a subdomain can work, but it should link to and from the main site clearly, and the two parts should feel like one business to a visitor.

Location pages and country versions

Some owners consider a subdomain for each city or country, such as london.example.com. For most businesses this is unnecessary and adds work, since each subdomain needs its own upkeep. A subfolder per place is easier to manage, if the places really deserve their own pages at all. Our guide to location pages and doorway pages covers when they do.

For businesses serving an area from one base, the page structure matters less than the content on it. Our explanation of local SEO for service area businesses shows how to describe coverage without building a subdomain per place.

Accessibility and usability should also be consistent across both parts of a site. A subdomain run by a separate team often drifts in design and behaviour. The overlap is explained in SEO and accessibility.

The risks of moving later

Changing structure after launch is possible but carries real risk. Moving a blog from a subdomain to a subfolder, or the reverse, changes every URL in it.

1. Make a full list of old URLs and their new equivalents.
2. Set up permanent redirects from each old address to its exact new address, not just to the new home page.
3. Update internal links, canonical tags, sitemaps and structured data to the new addresses.
4. Update Search Console properties so you can watch both sides.
5. Check the move in the page indexing report in the weeks after.

Expect a settling period. Rankings and traffic can wobble for a while even when everything is done correctly, and Google gives no fixed timetable. Do not judge the move after a few days.

If a move is on the table, plan it as a project, not a settings change. An SEO service that includes migration planning can map redirects and monitor the result. Whoever does it, avoid combining a structure change with a redesign, a platform change and a rewrite of the content all at once, because you will not be able to tell which change caused what.

A final practical point is ownership. Make sure you control the domain settings and hosting for every subdomain, as well as the main site. A blog or help centre on a third-party platform can disappear from your control if the account lapses or the supplier changes. Record who owns each hostname, where its DNS is managed and who can change it, so that structure decisions are never held up by a missing login.

Related guides

• SEO services
• Http status codes explained for seo
• Url structure for seo
• Website migration checklist moving to a new host

Questions and answers

Does Google treat subdomains differently from subfolders?

Google's documentation does not say one structure ranks better. It does treat a subdomain as a separate host in some places, for example site names in search and Search Console properties. In practice a subfolder is simpler to keep connected to the rest of your site.

Where should a blog live, on a subdomain or in a subfolder?

For most business sites, a subfolder such as /blog/ is the simpler choice. It keeps articles and service pages on one site with ordinary internal links. Use a subdomain when the blog runs on separate software or is managed by a separate team.

What are the risks of moving a blog later?

Every URL changes, so you need exact redirects from old to new, updated internal links, canonicals and sitemaps, and careful monitoring. Rankings can wobble for a while even when the move is done well. Avoid combining it with other large changes.

Is a subdomain bad for SEO?

No. A subdomain can rank and is right for separate products, apps or third-party platforms. The cost is extra effort to connect it with the main site and to monitor it. The problem is a poor fit, not the subdomain itself.

Should each city or country get its own subdomain?

Usually not. A subfolder per place is easier to manage, and many businesses do not need a page per place at all. Create separate pages only where each has something genuinely different to say.

Can I use both a subdomain and subfolders on one site?

Yes. Many sites keep marketing pages and the blog in subfolders and place an app or help centre on a subdomain. Make navigation and links consistent so visitors see one business and search engines can follow the relationships.