Subfolder and subdomain at a glance
A subfolder, also called a subdirectory, is a path on the main host: the main domain followed by a slash and a section name such as blog, help or a country code. It is served by the same host name as the rest of the site, even if a different system generates the pages behind the scenes through a reverse proxy. Visitors and search engines see it as part of the same site.
A subdomain is a host name to the left of the main domain, such as a blog, shop, app or help prefix. It can point to entirely different servers, run a different platform and be managed by a different team. That flexibility is why so many help centres, apps, stores and community forums live on subdomains: the software that powers them is often hosted by a vendor and easiest to attach that way.
For SEOImproving visibility in unpaid search results., the debate has run for years. Google's SEO Starter Guide focuses on clear site structure and descriptive URLs rather than favouring either form, and its guidance on multi-regional sites lists both subdomains and subdirectories as acceptable ways to organise regional versions, each with trade-offs. What practitioners see in practice is that sections tightly connected to the main site tend to benefit from its strength, and subfolders make that connection easier by default. The broader principles sit in the guide to site architecture.
Side-by-side comparison
Subfolder vs Subdomain
| Row label | Subfolder | Subdomain |
|---|---|---|
| URL structure | Path under the main host name | Separate host name in front of the main domain |
| How search engines treat it | Part of the same site; Google documents both as valid structures | Can be treated as closely related or more separately, depending on how it is connected |
| Internal linking | Easy to integrate into shared navigation and templates | Often has its own navigation; links to and from the main site need deliberate effort |
| Link equity | Links earned by the section and the main site support each other naturally | Links earned by the section help it, but sharing with the main site depends on cross-linking |
| Hosting and platform | Same host, or another platform served through a reverse proxy | Can run anywhere on any platform with a DNS record |
| Team ownership | Usually the main web team, with shared release processes | Can be owned and released by a separate team or vendor |
| Analytics setup | Same property and domain; little extra configuration | Needs cross-domain or cross-subdomain settings to keep sessions joined |
| International use | Regional folders share one domain's strength; simple to manage | Regional subdomains allow separate hosting per region; more to maintain |
| Migration risk | Moving in or out requires redirects and template changes | Same, plus DNS, certificates and platform changes |
Every BacklinkA link from another site to yours. the section earns counts for something either way. The question is how easily that value and the main site's value flow between them, which comes down to internal links and consistent templates more than to the address itself.
When to choose a subfolder
Choose a subfolder when the section exists to support the main site's goals. A blog, a resource library, a guides section, comparison pages or regional versions of the same product pages all benefit from sitting inside the main site, sharing its navigation and being linked from its most important pages. Teams that want content to help product and category pages rank should keep the two close together, with the internal linking guide as the practical reference. The academy capstone on an evidence-led SEO programme for a classic car parts retailer practises deciding where a new section of fitting guides should live as one part of a year's SEO plan.
Subfolders are simpler to operate. One domain to verify in search tools, one analytics property, one set of security certificates, consistent templates and a single place to check for technical issues. Fewer moving parts mean fewer things to break when the site changes.
A subfolder remains possible even when the section runs on a different platform. A reverse proxy can serve a hosted blog or help centre under a path on the main domain, though it needs engineering effort and careful testing of caching, canonical tags and redirects. When the main argument against a subfolder is the platform, ask whether that proxy work is feasible before settling for a subdomain.
Subfolders also make reporting more honest. When the blog and the product pages share a host, a search console property and an analytics property, it is easy to see which articles lead readers towards product pages and which only attract visits that never go further. That visibility helps editorial teams decide what to update, merge or retire, and it keeps content work tied to the commercial pages it exists to support.
When to choose a subdomain
Choose a subdomain when the section is genuinely separate. A web application behind a login, a customer community, a developer documentation site with its own tooling, a store on a hosted commerce platform or a status page often belongs on its own host name. These sections have different audiences, different release cycles and sometimes different security needs, and forcing them under a path adds complexity without much gain.
Subdomains suit sections owned by another team or vendor. A separate host name lets that team deploy, configure and secure its system without touching the main site, which can be the difference between launching this quarter and never launching.
Subdomains also appear in international setups. Google's multi-regional guidance lists them as one option for regional sites, alongside country-code domains and subdirectories. Whichever is chosen, language and region versions need hreflangAnnotation for language/region versions. annotations, covered in the hreflang guide.
When a subdomain is chosen, connect it deliberately. Link to it from the main navigation and relevant pages, link back from it to the main site, keep branding consistent and set up analytics to follow users across hosts. For a software company deciding where its app, documentation and community should sit, the guide to SEO for software companies places that choice among the other page types the site needs.
A software company consolidates its blog
A project management software company runs its blog on a hosted platform at a blog subdomain, with 420 articles and its own navigation. Product pages link to the blog from only a footer link. The team serves the blog under a blog subfolder through a reverse proxy, redirects all 420 URLs one-to-one and adds contextual links between articles and the 30 most relevant product pages. Organic sessions to the blog dip by about 12% in the first month after the move, recover within ten weeks, and organic sign-ups from product pages rise by 18% over the following quarter.
Decision table
| Situation | Lean towards | Why |
|---|---|---|
| A blog or resource centre meant to support product pages | Subfolder | Shares navigation, links and reputation |
| A logged-in app or customer portal | Subdomain | Separate platform, audience and security |
| A hosted help centre that can be proxied | Subfolder if feasible | Keeps support content inside the main site |
| A store or community on a vendor platform that cannot be proxied | Subdomain | Practical hosting constraint |
| Regional versions of the same site | Subfolder, unless regions need separate hosting | Simpler to manage; subdomains acceptable per Google's guidance |
| Moving an existing section between structures | Treat as a migration | Redirects and monitoring decide the outcome |
A move between structures is a migration in its own right; the site migrations guide sets out the redirect mapping and monitoring it needs. The comparisons hub lists related decisions. Whether a brand, product line or campaign should have a domain of its own at all, rather than a section of the main site, is the earlier question answered in the guide to microsites and multiple domains.
Common mistakes
- Moving a section for a rumoured ranking boost. Restructuring without a clear reason and a migration plan often costs more traffic than it gains.
- Leaving a subdomain isolated. A subdomain with no links from the main site's navigation struggles to benefit from it.
- Forgetting redirects. Every old URL needs a one-to-one redirect to its new home, kept in place long term.
- Splitting analytics. Without cross-domain configuration, a journey from subdomain to main site shows as two visits.
- Proxying without testing. Reverse proxies can break canonical tags, caching and internal links; test before launch.
- Duplicating content across hosts. The same articles on a subdomain and in a subfolder compete with each other; choose one and redirect.
- Ignoring ownership. A section placed in a subfolder that no one on the main web team maintains decays just as fast as one on a forgotten subdomain.
