A subdomain is a prefix added before a root domain name, separated by a dot — for example, blog.example.com or shop.example.com. Subdomains allow different sections of a website to run on separate servers or content management systems. In SEO, Google largely treats subdomains as separate entities from the root domain, meaning content on a subdomain must build its own authority rather than automatically inheriting the root domain's ranking power.
The subdomain vs subfolder debate is one of the most persistent questions in SEO — and for good reason. Where you host your blog, documentation, or shop determines how all the link authority those pages earn is attributed and compounded over time. Get it wrong and you could be giving away ranking power for years.
What is a subdomain?
In the domain name system (DNS), a full URL is structured as: protocol://subdomain.rootdomain.tld/path/. The "subdomain" portion sits between the protocol and the root domain, separated by dots.
Examples of common subdomains:
- www.example.com — the most common subdomain, historically used as the "world wide web" prefix
- blog.example.com — a blog on a separate subdomain
- shop.example.com or store.example.com — ecommerce hosted separately
- app.example.com — the web application interface
- docs.example.com — documentation site
- support.example.com — help centre or customer support portal
- en.example.com or us.example.com — language or geographic targeting
Technically, there is no limit to the number of subdomains you can create. DNS supports up to 127 levels of subdomains, and each can point to a different server, IP address, or web application.
How subdomains work at the DNS level
When a user visits blog.example.com, their DNS resolver makes a series of lookups. The registrar for example.com has defined a DNS A record (or CNAME) for "blog" that points to a specific IP address or hostname. The web server at that IP receives the request for blog.example.com and serves the appropriate content.
This means subdomains can point to:
- A completely different server (most common for SaaS app subdomains)
- The same server as the root domain but a different directory
- A third-party platform (e.g., help.example.com pointing to a Zendesk or Intercom instance)
- A CDN endpoint for static content
The flexibility of subdomains for technical infrastructure is a primary reason they became common — but that infrastructure flexibility does not translate into SEO flexibility.
How subdomains affect SEO
Google's official stance has evolved but remains nuanced. Google says it can understand when a subdomain and root domain belong to the same organisation and may associate them accordingly. However, the practical, observable reality in SEO testing is that:
- Subdomains start with lower authority. A new blog.example.com does not inherit the root domain's Domain Authority, Domain Rating, or PageRank. It starts from near-zero and must build independently.
- Backlinks don't automatically transfer. A link to blog.example.com is counted as a link to the subdomain, not to example.com, in third-party tools and likely in Google's link graph as well.
- Internal links between subdomain and root domain are treated somewhat like external links. This is the most consequential difference from subfolders — internal linking from the blog subdomain to the main domain passes less authority than internal links within a single domain.
- Separate crawl budgets may apply. Very large sites may find Googlebot allocating separate crawl budgets to their subdomains vs root domain.
Google's John Mueller has stated that Google "tries to understand" the relationship between subdomains and root domains but has also confirmed in multiple AMA sessions that subfolders are generally preferable for content that should contribute to the main domain's authority. This is as close to a recommendation as Google gives on the topic.
Subdomain vs subfolder — which is better for SEO?
The clearest guidance from both Google's statements and independent SEO testing is: for most content, subfolders outperform subdomains for organic search.
| Factor | Subdomain (blog.example.com) | Subfolder (example.com/blog/) |
|---|---|---|
| Authority inheritance | Starts near zero | Inherits root domain authority |
| Internal links | Treated as near-external | Full internal link equity flow |
| Link building | Links go to subdomain only | Links boost root domain too |
| Technical flexibility | Separate server, CMS, stack | Same server and CMS usually |
| Setup complexity | Simpler for separate platforms | May require CMS configuration |
| Content isolation | Complete separation | Shared sitemap and configuration |
When subdomains are the right choice
Subdomains are not always wrong. There are legitimate scenarios where the technical or organisational advantages outweigh the SEO trade-offs:
- The content genuinely serves a different audience. A support.example.com for existing customers and a main site for prospects serve different intent profiles. Keeping them separate may be strategically correct.
- Third-party platform integration. If your help centre runs on Zendesk, your community on Discourse, or your app on a completely different tech stack, pointing a subdomain at them is technically necessary and reasonable.
- International sites with different languages or regional CCTLDs. Some organisations use subdomains for language or region targeting (en.example.com, fr.example.com) as an alternative to ccTLDs or subfolders.
- UGC or community platforms. User-generated content on a subdomain provides legal and moderation isolation from the main site.
- Staging and development environments. staging.example.com, dev.example.com — these should be blocked from indexing with robots.txt or noindex, but subdomains are the correct tool here.
The www subdomain — a special case
The www prefix is technically a subdomain, but it functions differently from other subdomains. Historically, www indicated the World Wide Web version of a domain. Today, www vs non-www is a canonical preference choice, and Google treats both as equal — you just need to pick one and make it canonical.
Best practice: redirect all traffic to one canonical version (either always www or always non-www), set your preferred version in Google Search Console, and use that version consistently in all internal links, sitemaps, and structured data.
Migrating content from subdomain to subfolder
If your blog or other content currently lives on a subdomain and you want to move it to a subfolder for SEO consolidation, treat it as a full site migration:
- Set up the content at the new subfolder URLs (example.com/blog/).
- Implement 301 redirects from every old subdomain URL to its new subfolder equivalent.
- Update internal links sitewide to point to the new subfolder paths.
- Update your sitemap and submit via Search Console.
- Update all external backlinks you control (social profiles, directory listings, email campaigns).
- Monitor rankings and crawl errors for 8-12 weeks post-migration.
Subdomain-to-subfolder migrations can cause a temporary ranking dip as Google recrawls and re-attributes authority. Plan migrations for a low-traffic period and avoid doing them at the same time as other major site changes.
Subdomain best practices for SEO
- Default to subfolders for SEO-driven content. Blogs, glossaries, resource centres, and landing pages should live at example.com/blog/ not blog.example.com.
- Use canonical tags across subdomain/root domain if both exist. If you can't consolidate immediately, implement canonical tags pointing from subdomain content to preferred root domain versions where applicable.
- Ensure subdomains are in your sitemap hierarchy. If Google Search Console treats your subdomain as a separate property, add it as a separate property and submit its own sitemap.
- Block development and staging subdomains. Use robots.txt disallow or HTTP authentication to prevent test subdomains from being indexed.
- Don't create unnecessary subdomains. Each subdomain is an authority island. Every new subdomain you create is a new SEO entity that must earn its own authority from scratch.
Frequently asked questions
A subdomain doesn't inherently hurt SEO, but it fragments your domain authority. Content on a subdomain must build its own ranking power independently rather than inheriting the full strength of the root domain. For content-heavy sections like blogs, subfolders are generally recommended over subdomains.
Google says it can associate subdomains with the root domain when it understands they belong to the same organisation. In practice, SEO testing and ranking data consistently show that subdomains build authority more slowly than equivalent content on subfolders of the root domain.
Subdomains make sense when: the content is genuinely a separate product with its own audience; technical constraints require a separate stack; you are running a user-generated content platform; or the section serves a completely different geographic or language market on a different CMS.
Yes. A subdomain can independently accumulate authority and outrank the root domain for specific queries. Many large sites have subdomains (support.example.com, docs.example.com) that rank above the main site for certain terms. This typically requires significant independent link building to the subdomain.
This is contested. Backlinks to a subdomain do not automatically count as links to the root domain in most link analysis tools, and the flow of PageRank between subdomain and root domain is not confirmed by Google. In practice, consolidating content in subfolders ensures link equity stays within a single domain entity.
Related glossary terms
Sources
