Content revised 21 October 2026.
A subdomain is a hostname under a domain you control, such as support.example.com. Plan the DNS, hosting and purpose before creating or removing it.
Decide what needs separating
A support application or another distinct service may need its own deployment. Compare that with keeping content in the main website. A subdomain is not automatically a separate physical server, and it doesn't isolate performance or security simply because the address looks different.
Check the hosting workflow
The steps depend on the provider and control-panel version. Current cPanel documentation uses its Domains interface; an older standalone Subdomains tutorial may not match your account. Review the provider’s instructions and the intended document root before making changes.
Prepare the connection
- Create the intended hosting or application destination.
- Set the appropriate DNS record for that destination.
- Configure a valid HTTPS certificate and host handling.
- Test the hostname and its important routes.
Review search and access separately
A subdomain is not guaranteed faster indexing or inherited rankings from the main domain. Give public content a useful purpose and a clear discovery path. Protect private applications appropriately rather than assuming that an obscure address keeps them private.
Remove it with a plan
Check dependencies, users and links before deleting a hostname or its content. Decide whether a replacement or redirect is needed, then review the DNS and hosting configuration together. Keep backups and confirm the change with the provider if its consequences are unclear.
Official guidance: Current cPanel Domains documentation.