Subdomain

What Is a Subdomain?

A subdomain is a prefix added before your main domain name, separated by a dot. In blog.example.com, "blog" is the subdomain. It creates a distinct section of your website with its own content, while still being part of the parent domain.

Common subdomain examples:

• blog.example.com — company blog
• shop.example.com — e-commerce store
• app.example.com — web application
• docs.example.com — documentation
• api.example.com — API endpoints
• mail.example.com — email server
• staging.example.com — pre-production environment

Subdomains are free to create — you don't need to register anything new. If you own example.com, you can create unlimited subdomains through your DNS settings.

How Subdomains Work

Subdomains are configured through DNS records. When you create a subdomain, you're adding a new DNS entry that points to a specific server or IP address.

The DNS hierarchy:

.com                    ← TLD (top-level domain)
  example.com           ← domain (second-level)
    blog.example.com    ← subdomain (third-level)
      us.blog.example.com ← sub-subdomain (fourth-level)

Each level is separated by a dot. Technically, www is also a subdomain — www.example.com is a subdomain of example.com. Most sites today redirect www to the bare domain or vice versa.

Setting up a subdomain:

1. Log into your DNS provider or registrar dashboard
2. Add an A record or CNAME record for the subdomain
3. Point it to the IP address or hostname of the server hosting that content
4. Wait for DNS propagation (usually minutes, sometimes up to 48 hours)

Subdomains vs. Subdirectories

One of the most common decisions in web architecture: should you use blog.example.com (subdomain) or example.com/blog (subdirectory)?

Subdirectories (paths):

When to use subdirectories:

Most of the time. Google's John Mueller has confirmed that subdirectories benefit from the parent domain's authority. For blogs, documentation, and most content sections, subdirectories are the simpler and more SEO-friendly choice.

When subdomains make sense:

• Different tech stacks: Your main site is Next.js but your docs use a static site generator
• Separate applications: A web app at app.example.com that's a completely different codebase
• Multi-region sites: uk.example.com for UK-specific content
• Third-party services: support.example.com pointing to Zendesk or similar
• Development/staging: staging.example.com for pre-production testing

Subdomains and SEO

Google treats subdomains as mostly separate entities from the root domain. This has practical implications:

Authority inheritance:

Subdomains don't automatically inherit all the domain authority of the parent domain. Backlinks to blog.example.com primarily benefit the subdomain, not example.com. This is why most SEO professionals recommend subdirectories for content you want to rank.

Separate indexing:

Google may index and rank subdomains independently. A subdomain can rank for different keywords than the main domain, which can be beneficial for distinct product lines but problematic if you're trying to consolidate authority.

When subdomains help SEO:

• Targeting different countries with localized content
• Separating fundamentally different types of content (a SaaS tool vs. a blog)
• When the subdomain itself builds substantial authority

Common Subdomain Uses

www — The original subdomain:

The www subdomain was originally used to distinguish web servers from other services (mail, FTP). Today it's largely redundant. Most sites either redirect www to the bare domain or vice versa. Both approaches work fine.

mail and email subdomains:

Email infrastructure often uses subdomains for routing and authentication:

• mail.example.com — mail server
• MX records often point to subdomains
• SPF, DKIM, and DMARC records use subdomains for email authentication

api — API endpoints:

Many companies serve their API from a subdomain (api.stripe.com, api.github.com). This allows separate scaling, rate limiting, and infrastructure from the main website.

cdn — Content delivery:

Static assets (images, CSS, JavaScript) are sometimes served from a CDN subdomain like cdn.example.com or static.example.com to enable parallel downloads and separate caching.

Wildcard Subdomains

A wildcard DNS record (*.example.com) routes all subdomains to the same server. This enables:

• Multi-tenant SaaS: Each customer gets customer-name.example.com
• User profiles: username.example.com (like Tumblr, WordPress.com)
• Dynamic routing: Handle arbitrary subdomains in application code

Wildcard subdomains are configured with a * A record or CNAME record in DNS settings.

Subdomain Limits and Rules

Naming rules:

• Can contain letters (a-z), numbers (0-9), and hyphens (-)
• Cannot start or end with a hyphen
• Maximum 63 characters per subdomain label
• Total domain name (including all subdomains) cannot exceed 253 characters
• Case-insensitive: Blog.Example.com and blog.example.com are the same

Practical limits:

There's no hard limit on how many subdomains you can create. DNS providers may impose their own limits, but technically you can have thousands of subdomains on a single domain.

Nesting subdomains:

You can create subdomains of subdomains: us.blog.example.com. Each level adds complexity to DNS management. Most sites don't go beyond two levels deep.

Choosing a Domain for Subdomains

If you're planning to use subdomains extensively, your root domain choice matters:

• Short root domains work best — app.co reads better than app.mylongcompanyname.com
• .com remains the most recognized root for subdomain-heavy sites
• ccTLDs like .io or .ai work well for tech companies using api.company.io patterns

Search for available domains if you're setting up a new project that will use subdomains.