SEO subdomain or subdirectory? A decision guide for client sites.

Blog on blog.example.com or example.com/blog? Shop on a subdomain or inside the main site? The question comes up in almost every rebuild, and it deserves an answer based on documentation and the client's setup, not on forum folklore.

Key takeaways

  • Google's SEO Starter Guide says to do what makes sense for the business; it states no ranking preference.
  • The real differences are operational: robots.txt, Search Console properties, site names, hosting and who maintains what.
  • Moving a section between a subdomain and a subdirectory is a site move: map URLs and use permanent redirects.
  • Decide on maintenance, platform and measurement first, then document the choice for the client.

The SEO subdomain question is really a site architecture question. We answer it as part of every white label technical SEO project that involves a new blog, store, help center or country version, and the answer depends far more on the client's platform and team than on any rule of thumb.

What is the difference between a subdomain and a subdirectory?

A subdomain is a separate hostname in front of the main domain, such as blog.example.com. A subdirectory is a folder on the same hostname, such as example.com/blog/. Subdomains can live on different servers and platforms; subdirectories share the main site's host. For search engines, both can be crawled, indexed and ranked normally.

Does Google prefer subdomains or subdirectories?

Google does not state a preference. Its SEO Starter Guide says to do whatever makes sense for the business: partitioning topics into subdomains can make sense in some cases, while subdirectories can make a site easier to manage in others. So the decision rests on maintenance, platform limits and measurement, not on a documented ranking rule.

You will read strong opinions in both directions. Some practitioners report that content moved into a subdirectory performed better; others report the opposite. Those are observations about specific sites, often mixed with other changes made at the same time, so we do not present either as a rule to clients. What we can state is what Google documents, quoted in its SEO Starter Guide, and the technical differences below.

What actually changes with a subdomain

AreaSubdomain (blog.example.com)Subdirectory (example.com/blog/)
robots.txtNeeds its own file; the main domain's file does not applyCovered by the main site's robots.txt
Search ConsoleIncluded in a Domain property; needs its own URL-prefix property for separate reportsIncluded in both; filter by path
Site name in resultsCan have its own site nameUses the domain's site name; subdirectory site names are not supported
Hosting and platformCan run on a different server or CMSMust be served from the same host (or a reverse proxy)
AnalyticsCross-domain or subdomain settings to checkSame property by default

The sources for each row: Google's robots.txt specification says a file on a subdomain is only valid for that subdomain. Search Console Help on adding a property explains that a Domain property includes all subdomains and protocols and needs DNS verification, while a URL-prefix property covers only URLs that start with that prefix. And Google's documentation on site names supports a site name at the domain or subdomain level, but not at the subdirectory level.

Subdomains for country and language versions

For international sites, Google's guide to managing multi-regional and multilingual sites compares the options. Subdomains with a generic domain are easy to set up, allow different server locations and keep sites separate, but users may not recognize the targeting from the URL alone. Subdirectories are easy to set up and low maintenance on the same host, but separating the sites is harder. Google marks URL parameters such as ?loc=de as not recommended. Either structure needs hreflang and consistent internal linking to work well.

How should an agency decide for a client?

Start with four questions. Which platform will host the section, and can it be served under the main domain? Who maintains it? Does it need its own site name, robots rules or Search Console reports? How will analytics track users between sections? If the answers point to the same platform and team, a subdirectory is usually simpler to run.

  • Same CMS, same team: a subdirectory keeps one robots.txt, one sitemap index and one analytics setup.
  • Separate platform (a hosted help center, job board or store): a subdomain is often the only option unless the client can afford a reverse proxy.
  • Distinct brand or audience: a subdomain with its own site name may be the clearer choice.
  • Country versions: follow the multi-regional comparison above and plan hreflang from day one.
  • Existing traffic: if the section already ranks where it is, the cost of moving it is a real part of the decision.

How do you move a subdomain into a subdirectory?

Treat it as a site move with URL changes. Crawl the subdomain, map every old URL to its new path, deploy server-side permanent redirects, update internal links, canonicals and sitemaps, and monitor Search Console. Google says rankings can fluctuate while it recrawls and recommends keeping redirects in place for at least one year.

Google's site move guide covers the details, including that the Change of Address tool applies when moving from one domain or subdomain to another. The same steps apply in the other direction. We run it with the website redesign SEO checklist: benchmark first, map every URL, launch with redirects, then watch the data for at least eight weeks.

Three situations we see often

A blog on a hosted platform. The client wants an easy editor, the platform only offers a subdomain. Either accept the subdomain and link it well from the main site, or budget a reverse proxy. A store added to a service business. If the store runs on another platform, a subdomain is the practical choice; keep navigation, branding and analytics consistent. A legacy subdomain nobody maintains. Old help centers and microsites often hold outdated pages. Merging the useful ones into the main site and redirecting the rest is usually cleaner than keeping two sites half alive.

Presenting the decision to the client

Write the decision down in one page: the option chosen, why, what it costs to maintain, and what would make you revisit it. Clients remember architecture decisions only when traffic changes, so a dated note saves an awkward call later. Slug and parameter rules for the new section are covered in SEO-friendly URLs, and the wider audit in the technical SEO audit checklist.

If you need a specialist to plan or run the move under your brand, see white label technical SEO, part of our white label SEO services.

Frequently asked questions

Do subdomains share authority with the main domain?

Google does not document a rule either way, so we avoid promising it. Internal links between the two help users and crawlers find both.

Is a subdomain a separate site in Search Console?

It is part of a Domain property, and can also be added as its own URL-prefix property for separate reports.

Can a blog on a hosted platform use a subdirectory?

Only if it can be served under the main domain, usually through a reverse proxy set up by the hosting team.

Will moving a blog into a subdirectory increase traffic?

No one can promise that. Any move carries a period of fluctuation, so it needs a clear reason beyond expected rankings.

Does each subdomain need its own sitemap?

It needs its sitemap URLs listed somewhere Google can find, such as its own robots.txt or a Search Console submission.

Juan José Giraldo, senior white label SEO specialist

About the author

Juan José Giraldo is a senior SEO specialist with 5+ years of experience. He works on technical and local SEO for 600+ US car dealerships and supervises the SEO of 18 US e-commerce stores. He runs White Label SEO LATAM from Medellín, Colombia, and delivers white label SEO for agencies in the US, UK, Canada and Australia. Read more · LinkedIn.

Sources

  1. Google Search Central, SEO Starter Guide
  2. Search Console Help, Add a website property to Search Console
  3. Google Search Central, How Google interprets the robots.txt specification
  4. Google Search Central, Managing multi-regional and multilingual sites
  5. Google Search Central, Site names in Google Search
  6. Google Search Central, Site moves and migrations

Ready to test a pilot client?

Book a 30-minute call. You get an honest read on fit, scope and price, with no obligation.