Subdomain: Meaning, examples and limitations
A subdomain is a named subdivision of a domain, such as blog.example.com under example.com. It creates a distinct hostname, which can have its own hosting and configuration; it is different from a path such as example.com/blog.
At a glance
- A subdomain is part of the hostname, before the path.
- Hosting, certificates and routing must support the actual hostname.
- Using a subdomain does not automatically create a ranking advantage.
On this page

What changes in the address?
In blog.example.com/guide, blog.example.com is the hostname and /guide is the path. In example.com/blog/guide, the blog is represented by a path prefix on the main hostname. They are different public addresses even if they display the same article.
A subdomain can run a separate application or a section of the same system. Its name does not tell you which architecture is behind it.
Example: a regional publication
Imagine a business using a separate hostname for a regional publication. It needs the correct domain routing, HTTPS certificate and public links for that hostname. Language targeting also needs real localized content and appropriate language links. A regional-looking hostname alone does not translate a page.
Google's international-site guidance compares URL structures and operational trade-offs. Treat it as a decision about organization and delivery, not a promise that one structure always ranks better.
What operational boundaries matter?
Check authentication, cookies, analytics and caches deliberately. A separate hostname can create a separate browser origin, but cookie scope and related infrastructure can still connect subdomains. Do not assume a subdomain is automatically isolated from every part of the parent domain.
Public reference pages should have their own explicit delivery rules. A broad wildcard rule intended for a blog can accidentally catch account or customer hostnames if its scope is not reviewed.
How should a move be handled?
Moving content between a subdomain and a subdirectory changes URLs. Plan migration, redirects, internal links, canonicals and sitemap updates together. Verify old and new destinations rather than treating the move as a cosmetic folder change. The useful structure is the one the organization can maintain consistently while keeping content accessible.