A subdomain is a separate hostname under the same name. From a domain registrar perspective, it is one name. From a search engine perspective, it is mostly a related-but-separate site. From a maintenance perspective, it is a second site whose DNS, SSL, deploy, content and analytics will need attention forever.
What subdomains are
The familiar example is www versus apex: same registration, same ownership, often the same content. store.example.com, docs.example.com and blog.example.com are the canonical extension. Each one is a distinct hostname with its own configuration surface.
When subdomains are useful
- A genuinely separate audience or product surface.
- A platform constraint that requires a separate host (a hosted help desk, a status page, a third-party shop).
- A staging or test environment that should not live on the main host.
- A legitimate language or country split where regional infrastructure matters.
When subdomains get expensive
- Splitting content that the same audience would expect to find together.
- Putting a blog on a subdomain when the brand is small and the content cadence is light.
- Creating multiple regional subdomains for a site with no regional infrastructure.
- Spinning up subdomains because the CMS made it easy.
Patterns that work
For a small site, the practical default is to keep content on the main host. A subdomain joins the picture only when there is a reason that survives a one-sentence test: “why this content is not on the main host.” If the answer is shaky, the subdomain is a maintenance bill in waiting.
Where this fits next
Subdomain planning sits inside the broader domain profile review. For the planning sheet itself, see the checklists page.