Subdomain vs Subfolder

I default to subfolders for nearly every new project. The reason is simple: subfolders pool authority. Every page under /blog/ or /products/ shares the root domain's ranking signals. Internal links pass equity directly without crossing a hostname boundary. Google has said both structures can work, but in practice, I have seen subfolders outperform subdomains for organic traffic when the content is closely related to the main site. For example, I worked on a site that moved its blog from blog.example.com to example.com/blog/. After six months, organic traffic to blog posts rose by roughly 30%. The subdomain had been splitting crawl budget and backlink authority.

But I do choose subdomains in two scenarios. First, when the content requires separate infrastructure — a different CMS, hosting provider, or security zone. A client running a SaaS product used a subdomain for their help centre because it ran on a different platform. Second, when the audience or search intent is distinct enough that you want separate brand recognition. shop.example.com makes sense if the ecommerce section uses a subdomain for checkout security. The key rule: if you choose a subdomain, you must cross-link intentionally. I add contextual links and shared navigation to channel authority back to the root.

When the decision is borderline, I run a quick internal link audit. If most of your strongest backlinks point to the root domain, subfolders are the safer bet. If you already have strong external links to a subdomain, moving those URLs would risk losing equity. The decision rule: subfolders unless technical or organisational constraints demand separation.

The biggest mistake is assuming subdomains and subfolders are interchangeable. They are not. Subdomains create a separate hostname in Google's index. That means link equity from www.example.com does not automatically flow to blog.example.com. Many site owners split their content across subdomains without realising they have diluted their authority. I once audited a mid-size ecommerce site that had reviews.example.com, blog.example.com, support.example.com. Each subdomain had its own backlink profile, and none was strong enough to rank for competitive terms. Consolidating the blog into a subfolder lifted its positions significantly within three months.

Another pitfall is moving content without redirects. If you switch from subdomain to subfolder, set up a 301 redirect from every old URL to the new equivalent. I have seen sites lose 60% of organic traffic overnight because they forgot this step. Internal links also need updating. If you link to blog.example.com/post from your homepage, change it to example.com/blog/post. Tools like Screaming Frog can help identify cross-subdomain links.

A less obvious pitfall is treating subdomains as independent sites for [technical SEO](/technical-seo/) audits. You cannot run one [SEO audit](/seo-audit/) and assume it covers the subdomain. You need separate crawl configurations, sitemaps, and [canonical tags](/canonical-tag/). I have made this mistake myself — skipping the subdomain in a site-wide audit and missing a massive crawl issue. Similarly, do not forget to manage [duplicate content](/duplicate-content/) across subdomains; without proper canonicalisation, Google may see the same product in two places.

For years I believed subdomains were always worse for SEO. I told clients to move everything to subfolders. Then I encountered a site that had genuinely separate content: a university with courses.example.edu for degree programmes and research.example.edu for academic papers. These targets had different audiences, different search intent, and different linking strategies. Trying to stuff them under one subfolder would have created a messy information architecture and confused Google. After studying [website structure](/website-structure/) more carefully, I changed my mind: subdomains can be right when the content needs its own identity and crawl priority.

Another thing I got wrong was ignoring the role of [hreflang tags](/hreflang-tags/) for multi-regional setups. I used subfolders for languages (example.com/fr/) and assumed that was always best. But for a site targeting Canada and France separately with wholly different content, a subdomain approach (fr.example.com) allowed separate Google Search Console profiles, separate crawl budgets, and cleaner hreflang implementation. The performance was identical after six months. So the "subfolders always win" rule does not hold for internationalisation.

I also underinvested in [pagination](/pagination/) handling on subdomains. If you have a subdomain with paginated category pages, you need rel prev/next and proper canonicalisation. I treated the subdomain as an independent site and forgot to consolidate the pagination signals, leading to duplicate content warnings. Now I always audit duplicate content across any subdomain-to-subfolder boundary.