When should your business use a subdomain?
A subdomain is useful when part of your online service needs a different application, access policy or operational owner. For a blog that supports the same business as your main website, a subfolder is often simpler. Choose the structure you can maintain consistently, rather than treating the address alone as an SEO shortcut.
For example, support.example.com can run a help centre on a separate platform, while example.com/guides/ keeps articles within the main website. Both can work. The important question is what practical separation your business needs.
Subdomain, subfolder or separate domain?
| Structure | Example | Typical purpose |
|---|---|---|
| Subdomain | portal.example.com |
A distinct application or customer portal |
| Subfolder | example.com/blog/ |
Content within the main website |
| Separate domain | example-services.com |
A separately managed brand |
A subdomain belongs beneath your registered domain. It does not normally require another domain registration, but the application, hosting or certificate arrangement may carry additional costs. A new DNS record does not create the service behind it.
If the terminology is unfamiliar, start with domains, DNS and SSL explained.
Situations where separation makes sense
A customer portal may need its own release schedule and authentication. Technical documentation might use a different publishing tool from the marketing website. An online shop may be operated by a specialist platform that supports a custom subdomain. These are concrete reasons to consider separate hostnames.
A staging environment is another good example. It allows changes to be tested before customers see them. Protect staging with access controls: a robots.txt instruction is not a password and does not keep confidential material private.
Language versions can use subdomains, subfolders or separate domains. For a smaller European business publishing translations of the same pages, language folders can make navigation and administration easier. Whichever structure you choose, give each language a stable URL and link matching translations correctly.
What this means for SEO
Do not assume that a subdomain starts with an automatic ranking penalty or that moving a blog into a folder guarantees higher rankings. Google says to choose the organisation that makes sense for the business and is easiest to manage. Google Search Central's crawling and indexing FAQ addresses this directly.
The practical work remains: useful content, descriptive titles, crawlable links, suitable canonical URLs and a navigation structure visitors understand. Splitting a small collection of articles across several applications adds more places to keep these details consistent.
If your team publishes occasional articles about the same products it sells, keeping them within the main site is a sensible operational default. Use a subdomain when its benefits justify the extra maintenance.
Configure the whole route
First create the destination application and tell it which hostname it will serve. Then add the DNS record specified by the provider. An A record points to an IPv4 address, an AAAA record to an IPv6 address, and a CNAME makes one hostname an alias of another.
Edit the authoritative DNS service, which is not necessarily the company that registered your domain. Our DNS settings guide explains that distinction and the checks to make before changing records.
The destination also needs a valid certificate covering the hostname. This may be an individual certificate, a certificate containing several names, or an appropriate wildcard. Do not assume one wildcard covers every nested hostname or the bare domain. Check certificate coverage and renewal with your provider; SSL certificate management is part of planning the service.
Test before sharing the address
Open the full HTTPS address and check navigation, login, forms and any cross-domain integrations. Confirm analytics and consent behaviour where applicable. Check that the new hostname serves the intended content and that the old address does not create an unintended duplicate.
When retiring a subdomain, arrange redirects to relevant replacements while the old hostname still resolves and can serve HTTPS. Removing its DNS record first makes a web redirect impossible. Remove obsolete records pointing to cancelled third-party services so that the domain no longer refers to a destination you do not control.
ResaHost's domain service provides a place to discuss DNS and hosting together. Bring the name of the application and your intended address: that is enough to establish whether a subdomain solves a real problem and what work it needs.