Навчання
Subdomain vs Subdirectory: What It Means for SEO
Google treats both as part of your site and works out the relationship. The practical difference is smaller than the debate suggests — but it is not zero, and it favours subdirectories.
Запусти свіжий аудит DomainLens і використовуй звіт як список пріоритетів.
What the two actually are
A subdirectory is a path on the same hostname: example.com/blog. A subdomain is a different hostname that happens to share a registrable domain: blog.example.com. Technically they are distinct hosts, which is why the question arises at all.
Google's stated position is that it understands both and treats them as part of the same site when the relationship is clear. That has been consistent for years and there is no penalty either way.
| Subdirectory | Subdomain | |
|---|---|---|
| Example | example.com/blog | blog.example.com |
| Shares host signals | Directly | Google infers the relationship |
| Setup | Routing on one host | DNS record plus separate config |
| Separate hosting | Harder | Easy |
| Cookie scope | Same host by default | Separate unless widened |
| Search Console | One property covers it | Often a separate property |
Why subdirectories usually win
The advantage is consolidation and simplicity rather than a ranking rule. Everything on one hostname shares one Search Console property, one set of internal links without host boundaries, and one place to configure canonical, robots and analytics. Nothing has to be inferred because nothing is separate.
The counter-evidence people cite — sites that moved from subdomain to subdirectory and grew — is real but confounded: those migrations usually came with consolidation, better internal linking and renewed attention. The structure was rarely the only change.
When a subdomain is the right call
Operational reality beats theoretical SEO advantage. A subdirectory implemented as a fragile reverse proxy that breaks under load is worse than a subdomain that works. Choose the structure you can run reliably.
- A genuinely different application that cannot share routing — a help desk, a status page, a customer portal.
- Content in a different language served by different infrastructure, where a country or language subdomain is simpler to operate.
- A staging or development environment, which should be on a subdomain and blocked from indexing entirely.
- User-generated content you want kept at arm's length from the main brand.
- A platform whose hosting simply cannot be mounted under a path.
If you do move, treat it as a migration
The decision is rarely worth a migration on its own. If you are already rebuilding, choose a subdirectory; if the current structure works, the expected gain seldom justifies the disruption. See the migration checklist before committing.
- 1Map every old URL to its new equivalent before touching anything.
- 2Redirect each one with a 301 — never bulk-redirect to the new section's home page.
- 3Update internal links to point at the new URLs directly instead of relying on the redirects.
- 4Add the new structure to your sitemap and remove the old URLs once they redirect.
- 5Keep both Search Console properties during the transition so you can watch the handover.
- 6Expect a dip for a few weeks; keep the redirects in place for at least a year.
How DomainLens contributes
Whichever structure you choose, both hostnames must resolve, serve the correct status codes and agree on their canonical form — which is where the real failures happen. Check the DNS side with the DNS checker , and see internal linking strategy for connecting a subdomain back to the main site.
- Is a subdomain bad for SEO?
- No. Google treats subdomains as part of your site and there is no penalty. Subdirectories are marginally simpler to consolidate, which is a practical advantage rather than a rule.
- Should my blog be on a subdomain or a subdirectory?
- A subdirectory, unless the platform makes it impractical. It keeps everything on one hostname with one set of signals and one Search Console property.
- Does a subdomain need its own Search Console property?
- A URL-prefix property covers only that hostname, so yes. A domain property covers the domain and all its subdomains at once, which is usually more convenient.
- Is it worth migrating from a subdomain to a subdirectory?
- Rarely on its own. The expected gain is modest and migrations carry real risk. Do it when you are already restructuring for other reasons.