What is a subdomain? How it works and when it’s worth using
A subdomain is a separate, addressable section of your website that sits in front of your main domain name, such as blog.example.com or app.example.com. It shares the same root domain but behaves like its own space, with its own pages and, often, its own hosting and purpose. You reach for one when part of your site needs to work differently from the rest of it, whether that is a blog on a different platform, a web app, a documentation hub, or a version of your product built for a specific country.
The subdomain label sits directly in front of the domain, separated by a dot, and DNS routes it to whatever server you point it at. That routing is what makes subdomains useful: you can host one on a different server or codebase entirely, while keeping the same recognizable root domain. Below, we walk through how subdomains work, how they compare to a subfolder or a new domain, and where a subdomain fits if you are building with Sticklight.
- A subdomain is a prefix added in front of your domain, like blog.example.com, pointed at its own destination through a DNS record.
- Subdomains work through DNS, most often an A or CNAME record, and usually need their own SSL certificate or a wildcard certificate that covers them.
- A subdomain is the right call when content or a tool genuinely differs from your main site: a separate app, docs, a staging environment, or a region split.
- A subfolder, such as example.com/blog, tends to keep SEO authority more concentrated on one domain than a subdomain does.
- Sticklight lets you build what lives on a subdomain, whether that is a web app, a dashboard, or a client portal, as an additive layer alongside your existing site.
What a subdomain actually is
Every domain name has a structure: a subdomain (optional), the root domain, and a top-level domain like .com or .io. In blog.example.com, “blog” is the subdomain, “example” is the root, and “.com” is the top-level domain. The subdomain sits to the left of the root, and you can add more than one, such as beta.app.example.com, though most sites keep it to a single level for clarity.
A subdomain is not the same thing as a folder or path on your existing site. example.com/blog is a subfolder living inside the same site structure. blog.example.com is a subdomain, and to a browser, a server, and a search engine, it can be treated as its own distinct address, even though it shares your brand name.
- blog.example.com for a company blog
- app.example.com for a web application
- docs.example.com for product documentation
- shop.example.com for an online store
- support.example.com for a help center or client portal
How subdomains work behind the scenes
Subdomains work through DNS, the system that translates human-readable names into the server addresses computers use to find each other. When you create a subdomain, you add a DNS record for it, typically an A record pointing to an IP address or a CNAME record pointing to another hostname. That record tells the internet where to send visitors when they type or click a link to that subdomain.
Because a subdomain has its own DNS record, it can point somewhere completely different from your main site. Your root domain might run on one host and app.example.com might run on an entirely separate platform. Each destination generally needs its own SSL certificate, unless you use a wildcard certificate that covers the root domain and any subdomain under it.
Cookies are worth understanding too. By default, a cookie set on example.com does not automatically apply to app.example.com unless you configure the cookie’s domain setting to cover both, which matters if you want a visitor to stay logged in as they move between the two.
Subdomain vs subfolder vs a brand new domain
These three options solve a similar problem, adding a new section to your web presence, but they differ in how connected that section stays to everything else you run.
| Option | Example | Best fit |
|---|---|---|
| Subdomain | app.example.com | A section that needs its own platform, stack, or hosting, while keeping your brand name |
| Subfolder | example.com/blog | Content that should share SEO signals and authority tightly with your main site |
| New domain | example-app.com | A product or brand that stands fully apart from your original site |
A subfolder keeps everything under one roof, which tends to concentrate SEO authority and keeps internal linking simple. A subdomain gives you technical independence, useful when an app needs its own server, without the full separation of a new domain. A new domain fits a product that has its own identity and does not need to borrow trust from the original brand.
When a subdomain is the right call
Reach for a subdomain when the thing you are publishing has different technical needs, a different audience, or a different lifecycle than your main site.
- A web app or product that needs its own login, database, and hosting, separate from a marketing site (app.example.com).
- Documentation that updates on its own schedule and often uses a dedicated docs platform (docs.example.com).
- A staging or development environment for testing changes before they reach the live site (staging.example.com).
- Region or language splits, such as uk.example.com, when you want separate content per market without a full new domain per country.
- Internal tools and dashboards meant for your team or clients rather than public visitors (portal.example.com).
- A blog or knowledge base that runs on different software than the rest of your site.
If none of those apply and you are simply adding a new page or content type to your existing site, a subfolder is usually the simpler and more SEO-friendly path.
Subdomain pitfalls worth avoiding
Subdomains are a useful tool, and they come with a few tradeoffs worth planning around before you commit.
Search engines have gotten better at connecting a subdomain to its root domain, but they still often evaluate a subdomain’s content somewhat independently, which is one reason a subfolder can be the tighter choice for closely related content.
- SEO fragmentation. Spreading similar content across several subdomains can dilute signals that would otherwise concentrate on one domain.
- Cookie gaps. Without configuration, a user’s login on your main site will not automatically carry over to a subdomain.
- Certificate upkeep. Each subdomain typically needs its own SSL coverage, unless you use a wildcard certificate.
- Sprawl. It is easy to spin up a new subdomain for every side project. Without a plan, you end up with a scattered collection that is harder to maintain.
Building and publishing on a subdomain with Sticklight
Sticklight is the vibe-coding platform for professional web creators, built by the Elementor team and powered by Claude, that takes them beyond websites, into full-stack creation. It turns a plain-language prompt into a production-ready website, app, dashboard, or CMS, and a subdomain is often exactly where that build ends up living, sitting alongside a site you already run.
The flow follows three pillars: Prompt, Build, and Publish. You start by describing what you want in the main prompt box, or in Plan Mode if the project has more moving parts. During Build, you can add Skills, packaged units of expert know-how you attach in one click, including Accessibility, SEO, Performance, and Design System, so what you ship reflects real craft rather than a generic first draft.
Publish is where the subdomain question gets answered. Sticklight includes SEO built in, a security scan on every build, and custom domain connection, so you can point a subdomain like app.example.com or portal.example.com at what you built. If your main site runs on WordPress or Elementor, that stays exactly as it is. Sticklight is additive: it shares Elementor’s mission of empowering web creators to build their future, and what you build with it works alongside your existing setup rather than replacing any part of it.
Built by the Elementor team. Powered by Claude.
Let it glow.
