A subdomain is an additional level of a domain name, placed before the root domain, such as blog.example.com or shop.example.com. Technically, it is a separate host within the Domain Name System (DNS), which means it can point to a different server, platform or application than the main website.
Key Points
- A subdomain sits before the root domain: sub.example.com.
- It is configured through DNS and can run on a separate platform.
- Search engines may treat subdomains more independently than subfolders.
- Subfolders (example.com/blog/) keep content under one host and one property.
- Subdomains are useful for separate apps, regions or platforms such as help centers.
Practical Example
A B2B company runs its blog on blog.company.com using a different CMS. Most links point to the main domain, and the blog grows slowly. After migrating the blog to company.com/blog/ with 301 redirects, the content is consolidated under one host and benefits from the main site’s internal linking.
Why It Matters
The choice between a subdomain and a subfolder affects how authority, internal links and analytics are organized. For marketing content that should support the main site, a subfolder is usually simpler to manage. Subdomains make sense when a section is technically or commercially separate. The decision should be made before launching, because migrating later requires redirects and carries risk.
Frequently Asked Questions
Is a subdomain bad for SEO?
No. Google can crawl and rank subdomains normally. The practical question is whether the content benefits from being consolidated with the main site, which a subfolder makes easier.
Does a subdomain need its own Search Console property?
A domain property in Google Search Console covers all subdomains. A URL-prefix property covers only the exact host you add.
Related Terms
Sources
- IETF, Domain Names: Concepts and Facilities (RFC 1034), https://www.rfc-editor.org/rfc/rfc1034
- Google Search Console Help, Add a website property, https://support.google.com/webmasters/answer/34592