What Is a Subdomain?
A subdomain is a prefix added to your main domain to create a separate, organized section of your web presence, like shop.yourbusiness.com or blog.yourbusiness.com. It uses your existing domain, so you do not register a new one, and can point to different content, a separate app, or another server. Subdomains help structure large sites, host distinct services, and set up staging environments. The familiar www is itself a subdomain. They are configured through DNS records.
- Format
- prefix.yourdomain.com (e.g. blog.yourbusiness.com)
- Cost
- Free to create on a domain you already own
- Configured via
- DNS records (A or CNAME) on your domain
- Common uses
- Blog, shop, app, support, staging environments
What is a subdomain in simple terms? #
A subdomain is a part of your website that lives under your main domain but functions as its own distinct section, identified by a prefix before your domain name. If your domain is yourbusiness.com, then blog.yourbusiness.com and shop.yourbusiness.com are subdomains. You do not have to register these separately; they are created from the domain you already own, at no extra cost. Each subdomain can point to different content, run on a different server, or even use different technology from your main site. A helpful way to picture it: if your domain is a building, subdomains are separate floors or departments within it, each with its own space but sharing the same address. Even the familiar www at the start of many web addresses is technically a subdomain of your domain. Subdomains are a flexible tool for organizing and expanding a web presence. Understanding them helps when you want to add a store, a blog, a customer portal, or a staging site, all common needs in our /services/web-design and /services/web-app-development work.
How do subdomains fit in the domain structure? #
Subdomains sit at the front of a domain name, to the left of the registered domain, and understanding the hierarchy makes them clear. Take shop.yourbusiness.com. Reading right to left: .com is the top-level domain or TLD, explained in /wiki/what-is-a-tld; yourbusiness is the second-level domain, the unique name you register; and shop is the subdomain, a subdivision you create and control. So the naming system is a tree, with the TLD at the top, your registered domain beneath it, and subdomains branching below that. You can even nest subdomains, like store.shop.yourbusiness.com, though that is rarely needed. Because subdomains are part of your registered domain, you manage them yourself through your domain's /wiki/what-is-dns settings; there is no separate registration or fee. This is different from a subdirectory, like yourbusiness.com/shop, which is a folder within the same site rather than a separate section. The distinction between subdomains and subdirectories matters for organization and SEO, and it is one we help clients navigate when structuring their sites.
How are subdomains created and configured? #
Creating a subdomain is quick and done entirely through your domain's DNS settings, with no new registration required. To make blog.yourbusiness.com, you add a DNS record, typically an A record pointing the subdomain to a server's IP address, or a CNAME record pointing it to another hostname, in the control panel for your domain. That record tells the internet where the subdomain should lead. You can point a subdomain at the same server as your main site or at a completely different one, which is what makes subdomains so flexible: shop.yourbusiness.com could run on a dedicated ecommerce platform while yourbusiness.com stays on your main host. Many hosting control panels also offer a one-click subdomain creator that sets up the DNS and a folder for you. The example below shows the shape of the DNS records involved. Getting these records right is routine but important, since a misconfigured subdomain simply will not load, and it is part of what our /services/domains-dns-email service manages for clients.
; Point blog subdomain to a server's IP address
blog IN A 203.0.113.25
; Point shop subdomain to an external platform
shop IN CNAME shops.myecommercehost.com.
; The classic www subdomain, pointing to the main site
www IN CNAME yourbusiness.com.What are common uses for subdomains? #
Subdomains solve a range of practical needs. A blog often lives at blog.yourbusiness.com to keep content organized, though many businesses now prefer a subdirectory for SEO reasons. An online store might use shop.yourbusiness.com, especially when it runs on a separate /wiki/what-is-an-ecommerce-platform from the main marketing site. A customer login area or /services/client-portals frequently sits at a subdomain like portal.yourbusiness.com or app.yourbusiness.com, cleanly separating the application from the public site. Support and help centers commonly use support.yourbusiness.com or help.yourbusiness.com, often powered by a third-party help-desk tool. Developers use subdomains for staging and testing environments, like staging.yourbusiness.com, keeping a work-in-progress copy separate from the live site as described in our /wiki/staging-vs-production guide. Businesses with multiple locations or brands sometimes use subdomains to organize them. And regional or language variations can live on subdomains too. The common thread is separation: a subdomain gives a distinct part of your presence its own space and can even run on entirely different technology, without needing another domain.
What is the difference between a subdomain and a subdirectory? #
This distinction causes real confusion and has practical consequences. A subdomain is a prefix, like blog.yourbusiness.com, treated as a somewhat separate section with its own DNS entry. A subdirectory (or subfolder) is a path within your main site, like yourbusiness.com/blog, a folder on the same site. Both can hold a blog or a shop, so how do you choose? Technically, subdomains are better when the section runs on different software, a different server, or needs to be managed independently, since they can point anywhere. Subdirectories are simpler, living within your existing site. The debated part is SEO. Search engines have historically treated subdomains as somewhat separate entities, meaning a blog on a subdomain may not pass as much authority to the main domain as one in a subdirectory would, though search engines have grown better at connecting them. For content whose main goal is boosting the main site's rankings, like a marketing blog, a subdirectory is often the safer SEO choice. For genuinely separate applications, a subdomain makes more sense. We advise clients on this trade-off during /services/local-seo and site-structure planning.
Do subdomains help or hurt SEO? #
Subdomains are neither inherently good nor bad for SEO; what matters is using them appropriately. The key consideration is that search engines have traditionally viewed a subdomain as a partly separate site from the main domain, so authority and ranking signals do not always flow as freely between them as they do within a single site using subdirectories. This means a marketing blog placed on a subdomain might build its own authority somewhat separately, rather than fully strengthening the main domain, which is why many SEO practitioners recommend subdirectories for content meant to lift the primary site. That said, search engines have improved at understanding that subdomains and their parent domain belong to the same organization, so the gap is smaller than it once was. Subdomains are entirely appropriate when a section is genuinely distinct, such as a separate application, a help center on third-party software, or a staging site, cases where separation is the point. The practical rule: use subdirectories for content aimed at boosting the main site's rankings, and subdomains for separate services or apps. Our /services/local-seo team helps clients structure sites so SEO value is not accidentally split.
How do subdomains relate to staging and separate services? #
One of the most valuable uses of subdomains is running separate environments and services cleanly. For development, teams often set up a subdomain like staging.yourbusiness.com to host a test copy of the site, keeping unfinished work safely apart from the live site, exactly the setup described in our /wiki/staging-vs-production explainer; such staging subdomains are password-protected and hidden from search engines. Subdomains also shine for hosting third-party or separately-built services under your own brand. A help desk, a booking system, a status page, or a /services/client-portals login can each live on a subdomain that points to specialized software, so customers see a consistent yourbusiness.com address even though the underlying tool is different. This lets a business combine best-of-breed services under one branded umbrella. Because each subdomain has its own DNS record, it can point to a completely different provider or server without affecting the main site. This flexibility is why subdomains are a standard part of how we architect larger projects in /services/web-app-development, keeping the public site, the app, the portal, and the staging environment organized and independently manageable.
Do subdomains need their own SSL certificate? #
Yes, each subdomain generally needs to be covered by an SSL certificate to load securely over https, and this is worth planning for, as broken security warnings scare away visitors. There are a few ways to handle it. A standard SSL certificate covers only the exact name it is issued for, so yourbusiness.com and www.yourbusiness.com are typically covered together, but a new subdomain like shop.yourbusiness.com would need coverage too. A wildcard SSL certificate covers all subdomains of a domain at once (*.yourbusiness.com), which is convenient when you run several. Many modern hosts and services also issue free automatic certificates for each subdomain through services like Let's Encrypt, handling this behind the scenes. The key point is not to overlook it: a subdomain without a valid certificate will show visitors a security warning and may be blocked by browsers, undermining trust. Understanding this connects to our /wiki/what-is-an-ssl-certificate guide and our broader /services/website-security work. When we set up subdomains for clients, ensuring proper SSL coverage is a standard part of the configuration so every part of the site loads securely.
FAQ
What is a subdomain?
A subdomain is a prefix added to your main domain to create a separate section of your web presence, like blog.yourbusiness.com or shop.yourbusiness.com. It uses a domain you already own, so it is free to create, and can point to different content or servers. The familiar www is itself a subdomain of your domain.
Do I have to pay for a subdomain?
No. Subdomains are created from a domain you already own, so there is no separate registration or fee. You can make as many as you need through your domain's DNS settings at no extra cost. You only pay for the main domain registration, not for the subdomains you build under it.
What is the difference between a subdomain and a subdirectory?
A subdomain is a prefix like blog.yourbusiness.com, treated as a somewhat separate section with its own DNS record. A subdirectory is a folder within your main site, like yourbusiness.com/blog. Subdomains suit separate apps or services; subdirectories suit content meant to strengthen the main site, since they usually share ranking authority more directly.
Are subdomains bad for SEO?
Not inherently. Search engines have traditionally treated subdomains as somewhat separate from the main domain, so ranking authority may not flow as freely as within subdirectories. For content aimed at boosting your main site, a subdirectory is often safer. For genuinely separate apps, portals, or staging sites, a subdomain is entirely appropriate.
How do I create a subdomain?
You create a subdomain through your domain's DNS settings by adding a record, usually an A record pointing to a server's IP address or a CNAME pointing to another hostname. Many hosting control panels offer a one-click subdomain creator. No new domain registration is needed since it uses your existing domain.
Does a subdomain need its own SSL certificate?
Yes, each subdomain needs SSL coverage to load securely over https. A standard certificate covers only its exact name, so a wildcard certificate (covering all subdomains) or automatic free certificates per subdomain are common solutions. Without valid SSL, a subdomain shows visitors a security warning, so we always configure it when setting subdomains up.
Was this helpful?