Subdirectory

A subdirectory, also called a subfolder, is a folder that lives inside a website's URL path, appearing after the domain and a slash — for example, the /blog/ in example.com/blog/ or the /help/guides/ in example.com/help/guides/. It organizes content into named sections within one domain, the same way folders organize files on a computer. The homepage sits at the root (example.com/), and each subdirectory branches off it, so a store, a blog, a help center, and a careers section can each occupy their own path while all remaining part of the same site. Subdirectories can nest inside one another to any depth, which lets a large site build a clear, hierarchical structure. Every page still belongs to the single root domain, which is the defining feature that separates a subdirectory from a subdomain.

Subdirectories matter because they shape both how humans navigate a site and how search engines understand it. A logical folder structure — example.com/services/seo/ under example.com/services/ — signals the relationship between pages, groups related content, and makes URLs readable and predictable. For SEO, the widely held view is that a subdirectory keeps a section firmly inside the main domain, so the authority and links the whole domain earns tend to support the pages in that folder. That is the practical reason many teams choose a subdirectory over a subdomain for content like a blog or resource hub. The structure is not just cosmetic: it influences internal linking, crawl paths, breadcrumb trails, and how neatly a site's information architecture maps onto its URLs.

The cousin most often confused with a subdirectory is the subdomain, and the difference sits in the URL. A subdirectory is a folder in the path after the domain — example.com/blog/ — so the content lives inside the root domain. A subdomain is a prefix before the domain — blog.example.com — which search engines and browsers treat as a distinct host, effectively a related but separate site under the same registered domain. That distinction has consequences. Content in a subdirectory generally shares the momentum of the whole domain most directly, because it is unambiguously part of it. A subdomain can be treated more independently, which is sometimes what you want (a separate app, a store on a different platform, a region with its own team) and sometimes a disadvantage (a blog that would benefit from riding the main domain's authority).

Choosing between them is a real decision, not a formality. Many SEO practitioners favor a subdirectory for content meant to strengthen the core site — a blog, guides, a knowledge base — precisely because it stays inside the domain. A subdomain earns its place when a section is genuinely separate in technology, ownership, or purpose, or must run on a platform that cannot live in the main site's path. Both are valid; the mistake is choosing blindly. Do not confuse a subdirectory with a subdomain when planning structure, and do not confuse either with a completely separate domain (a different registered name entirely), which shares none of the parent's authority. The URL tells you which one you are looking at — a slash after the domain means a subdirectory, a dot before it means a subdomain.

Using subdirectories well means designing a folder structure that mirrors how the site is actually organized — shallow enough to stay readable, deep enough to group related content, with clear, human-readable folder names (example.com/support/billing/ beats example.com/s/b/). It means keeping URLs stable, because a subdirectory path baked into links and search results is costly to change; when you must move a section, redirect the old paths. It means choosing a subdirectory over a subdomain when the content should reinforce the main domain, and reaching for a subdomain only when separation is genuinely warranted. Good structure supports navigation, breadcrumbs, internal linking, and crawlability all at once, so the effort spent on a sensible folder hierarchy pays back across the whole site.

The failures are letting the folder structure sprawl into deep, cryptic paths that neither users nor search engines can parse; scattering related content across inconsistent subdirectories; splitting a blog or resource hub onto a subdomain when a subdirectory would have kept it inside the domain's authority; and changing subdirectory paths without redirects, which breaks links and loses accumulated value. The discipline is to treat the subdirectory structure as information architecture expressed in URLs — organized, stable, and readable — reserving subdomains for genuinely separate sections, and to remember that where content sits in the path is not a cosmetic detail but a signal of how the site is built and how its parts relate.

Subdirectory — a folder in a website's URL path such as example.com/blog/ — organizes content inside a single domain, distinct from a subdomain that sits before the domain as a separate host.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where subdirectory is a core concern: