Subdomain vs Subdirectory for SEO: What Actually Matters

You're launching a blog, a shop or a help centre, and the setup screen asks one quiet question: blog.yoursite.com or yoursite.com/blog? The subdomain vs subdirectory for SEO argument has run for more than a decade, and most guides still end with "it depends." That doesn't help much when you have to pick one today.

This guide gives you a straight answer, the few cases where the other option wins, and the exact setup and migration steps for both. A steady share of the support cases our engineers fix each day trace back to this choice being made in a hurry at launch. So this guide is built from cleaning up those setups, written so you can get it right yourself.

Every host sees these tickets. At Hostaccent, a UK-registered host (hosting since 2016, UK-incorporated 2018) whose engineers resolve 20 to 30 client issues a day, they usually arrive as one worried question: why did my blog traffic drop after I moved it? The honest answer is rarely "Google hates subdomains." It's almost always a missed redirect, a missing certificate, or a section that quietly split one website into two.

Quick Answer: For most websites, a subdirectory (example.com/blog) is the better SEO choice as of September 2026, because all content sits on one host, shares one backlink profile and runs from one robots.txt and one sitemap. Google says it can rank either structure. Pick a subdomain only when the section runs on different software, serves a separate audience, or needs to be isolated for security.

What Does Google Actually Say About Subdomains and Subfolders?

Google's official position is that it has no ranking preference between the two structures. Its Search Central help content tells site owners to use whatever is easiest to organise and manage, and Google's John Mueller said in 2018 that web search is fine with either option.

On the subdirectory vs subdomain Google question, that's the whole official line. But "no preference" doesn't mean "no difference." In the same statement, Mueller added that Google has to learn how to crawl a new subdomain separately, which he called a formality for the first few days. That small detail tells you how Google's systems see a subdomain: as its own host with its own crawl pattern, not as a folder of your main site.

Google's documentation confirms this elsewhere. The site names documentation for Google Search defines a "site" as a domain or subdomain, and it states that site names aren't supported at the subdirectory level. So news.example.com can show its own name in search results, while example.com/news can't.

So why do SEOs still argue about it?

Because two things are true at once. Google can rank content on either structure, and plenty of public case studies (several from well-known software brands) report organic traffic climbing after a blog moved from a subdomain into a subfolder. Those gains usually come from consolidation rather than from some hidden penalty. Links pointing at the main domain start helping the blog, internal links stop crossing between hosts, and one team maintains one set of technical settings instead of two.

As of September 2026, Google treats a subdomain such as blog.example.com as a separate site for features like site names, crawling and robots.txt, while a subdirectory such as example.com/blog is simply part of the main site. Both can rank in position 1, but a subdirectory inherits the main domain's signals with zero extra setup, which makes it the safer default for most blogs.

Two practical changes have also softened the old debate. A Search Console Domain property, verified once with a single DNS TXT record, now reports on every subdomain and protocol together, so your data is far less fragmented than it was in 2018. On the other hand, robots.txt still works per host. That means blog.example.com ignores every rule you wrote in example.com/robots.txt, and plenty of site owners only discover this after their staging subdomain shows up in search.

Subdomain vs Subdirectory for SEO: Where the Real Differences Show Up

The real differences are about how signals, settings and maintenance get split, not about a hidden ranking switch. Keep everything in one subdirectory and you run one site. A subdomain turns that into two sites that happen to share a brand name.

Link equity and topical authority

When another website links to your homepage or product pages, that authority flows most easily to pages on the same host through your internal links. A post at example.com/blog/guide sits one click away from pages that already have links pointing at them. The subdomain SEO impact shows up here first: a brand-new blog.example.com starts with its own thin link profile and has to earn trust largely on its own merits.

Crawling, robots.txt and sitemaps

Each subdomain needs its own robots.txt file, its own XML sitemap reference and its own crawl history. A subfolder shares all three with the main site. On a small site that's a minor chore. On a site with a few thousand URLs, it becomes two sets of settings that slowly drift apart as different people edit them.

Analytics, cookies and tracking

Cross-subdomain tracking needs extra configuration in GA4 and your tag manager, and cookies must be scoped to the parent domain to follow a visitor from a blog post to your checkout. A subfolder needs none of that. Every session, conversion path and scroll event lands in one property by default.

Security and performance isolation

This is where a subdomain earns its keep. It can live on a separate server, IP address or software stack, so a plugin exploit or a sudden traffic spike on the blog doesn't take your store down with it.

A subdirectory keeps every page on one host, so backlinks, crawl history, analytics and security settings stay unified, while a subdomain splits them into a second site you maintain separately. For a 20-post blog that split is a minor chore, but for a content hub with 5,000 pages it becomes a permanent second workload for whoever manages SEO.

Insider Insight: The duplicate-content problem we see most often isn't strategic at all. When a subdomain's document root sits inside public_html (a default on many older panel setups), the same files load at blog.example.com and at example.com/blog. Google can find and index both copies. Point the subdomain at a folder outside public_html, or 301 the path version, before you publish your first post.

When Is a Subdomain the Right Call?

A subdomain is the right call when the section is genuinely a different product, runs on different software, or must be isolated for security. For a normal blog on the same WordPress install as your main site, it almost never is.

The Same-Site Test

Our team runs a three-question check (we call it the Same-Site Test) before creating either structure for a client:

1. Does this section run on the same software and server as the main site?
2. Would a visitor on your homepage expect to find this content there?
3. If this section broke or got hacked, would you need the main site kept completely separate?

If you answer yes to the first two and no to the third, use a subfolder. A no on question one, or a firm yes on question three, points to a subdomain. In our experience, most blogs, resource hubs and campaign landing pages come out as subfolders within about 60 seconds of honest answers.

The Same-Site Test is a three-question rule for choosing between a subdomain and a subdirectory: does the section share the main site's software and server, would homepage visitors expect it, and does it need isolation? When the first two answers are yes and the third is no, use a subfolder such as example.com/blog; otherwise, a subdomain is justified.

Where subdomains genuinely win

There are real cases where a separate hostname is the better engineering decision:

• Web apps and dashboards (app.example.com) built on a different framework, such as a Next.js app running beside a WordPress marketing site.
• Hosted help desks or status pages that a SaaS provider runs for you and can only connect through a CNAME record.
• Staging and testing copies, kept out of search with a noindex rule plus password protection.
• Separate regional or brand teams that need their own CMS, their own release schedule and their own site name in search results.

Notice what's missing from that list. A blog that shares your theme, your server and your audience isn't on it, no matter how many posts it has.

A 2026 warning about renting out part of your domain

Whichever structure you choose, don't lease a subfolder or subdomain to a third party that publishes unrelated content, such as coupon or casino pages. Google's site reputation abuse policy, enforced since 2024, targets exactly that pattern. The structure you picked won't shield the main site if a manual action lands.

◆ Professional help available

Prefer a specialist-managed migration?

Eligible moves into Hostaccent hosting are included at no separate migration charge. Independent migrations between other providers are scoped and quoted before work begins.

Request a migration assessment→How migrations work↗Hosted elsewhere? One-time paid support is available after scope and price confirmation.

What Hosting Features Make Either Setup Easy?

Either structure works on almost any host, but five features decide whether setup takes five minutes or eats a weekend. Check them before you pay, not after.

The five-point hosting checklist

1. A control panel that creates both. Subdomains and subfolder installs should be a short form, not a ticket.
2. Free SSL on every hostname. Each subdomain needs a valid certificate. Let's Encrypt certificates are free and last 90 days, so automatic renewal matters more than the certificate itself.
3. Full DNS access. You'll add A, CNAME and TXT records for subdomains and for Search Console verification.
4. Fast storage and current PHP. NVMe SSD storage and PHP 8.x keep a growing blog responsive, whichever URL it lives on.
5. Human support that understands redirects. Migrations break at the redirect layer, where you want an engineer, not a script.

How the options compare

| Hosting option | Intro price/mo | Renewal price/mo | What the price includes | Subdomain + subfolder setup | SSL on subdomains | |---|---|---|---|---|---| | Hostaccent Economy (shared) | $1.99 | $1.99 | Control panel, NVMe storage, 24/7 human support | Both from the panel in about 5 minutes | Free Let's Encrypt | | Typical promo shared plan | ~$2.99 (usually with a multi-year prepay) | Often 2-4x the intro rate | Panel included, support level varies | From the panel | Usually free AutoSSL | | Unmanaged budget VPS | ~$4-6 | Varies by provider | Bare server only; panel licence extra, you do the admin | Manual Nginx/Apache and DNS config | You install and renew Certbot yourself | | Website builder platform | ~$15+ | Varies by provider | Hosted builder, little server access | Subdomains usually; custom subfolder proxy often impossible | Included |

The sticker price hides the real cost. Over 36 months, the Economy plan at $1.99/mo comes to about $72, with no renewal jump. An unmanaged VPS at around $5/mo is roughly $180 over the same period before you add a cPanel licence (often $30+/mo on its own) and the hours you'll spend patching Nginx, renewing certificates and writing redirect rules. A promo shared plan that starts at $2.99 and renews at, say, $9.99 looks cheaper in year one and lands near $276 by the end of year three.

The renewal-price reality

Intro prices across the hosting industry often require a 24 to 36 month prepay, and the renewal rate is frequently two to four times higher. Before you buy, find the renewal figure in the terms and multiply it by the years you'll realistically stay. That total is your real hosting cost. Our breakdown of the cheapest way to host a website runs this full 3-year math across plan types.

Why we point you to our own plan

We're a host, so weigh this recommendation with that in mind. Hostaccent has completed 4,000+ site migrations since 2016. Its Economy plan renews at the same $1.99/mo you sign up at, subdomains and subfolder installs are both created from the panel, and servers sit behind Cloudflare, then Nginx, then Apache on NVMe storage, with a 99.99% uptime guarantee. If you're hosting several client projects, compare Standard ($4.58/mo) and Ultimate ($6.50/mo) on the product page before you pick.

Best pick by use case

• One blog on your main WordPress site: a subfolder, on an entry shared plan like Economy.
• Blog plus a WooCommerce store: subfolders for both, so product and content pages share authority.
• Marketing site plus a separate web app: a subfolder for the blog and a subdomain for the app.
• Multilingual site run by one team: subfolders like /de/ and /fr/, with hreflang tags.
• Agency staging copies: subdomains, blocked from indexing.

How to Set Up a Blog Subdomain or Subfolder (Step by Step)

Both setups take about five minutes in a standard control panel. The only extra work with a subdomain is DNS and SSL, which is also where most launch-day problems begin.

Setting up a subfolder blog

If your main site already runs WordPress, you don't need a separate install. Set a static homepage under Settings, then Reading, and assign a page called Blog as your posts page. Your post archive now lives at example.com/blog/, and a custom permalink structure of /blog/%postname%/ puts every individual post under that path too.

If the main site is static or built on another platform, install WordPress into public_html/blog through your panel's app installer, or upload it manually and create a fresh MariaDB database for it. Either way, the blog shares the main site's hostname, certificate and robots.txt, so there's nothing else to configure.

Setting up a subdomain blog

1. Create the subdomain in your panel and set its document root outside public_html, for example /home/user/blog.example.com.
2. Add or confirm the DNS record. Most panels create an A record automatically, but if your DNS lives at Cloudflare or your registrar, add an A record (or a CNAME) for "blog" yourself. Our guide to DNS records explained shows which record type fits. A TTL of 300 seconds makes mistakes quick to correct.
3. Issue SSL only after DNS resolves, because AutoSSL or Let's Encrypt validation fails while the record still points somewhere else.
4. Install WordPress, then add a robots.txt file and an XML sitemap for the new host.
5. Check Search Console. A Domain property already covers the subdomain, but a URL-prefix property needs a separate one.

A subdomain setup involves four jobs a subfolder never needs: a DNS record, its own SSL certificate, its own robots.txt and sitemap, and a Search Console check. On a standard control panel the whole process takes about 5 minutes, plus however long the DNS change takes to spread, which is usually just a few minutes with a 300-second TTL.

Pro Tip: If you switch Cloudflare's SSL mode to Full (strict) before the new subdomain has a valid origin certificate, visitors get a 526 error that looks like a server fault. Issue the origin certificate first, then change the mode. And if the fresh blog throws a 500 on first load, the cPanel error log usually names the cause in one line.

How to Move Your Blog From a Subdomain to a Subfolder Without Losing Traffic

Moving a blog into a subfolder is safe when every old URL gets a one-to-one 301 redirect and every internal reference is updated. Skip either step and you'll give away rankings you already earned.

Across the 4,000+ site migrations our team has handled since 2016, the step people most often get wrong is the redirect map. They send every old post to the new blog homepage instead of to its matching URL, and Google tends to treat mass redirects like that as soft 404s.

Here's the checklist to move blog from subdomain to subfolder paths cleanly:

1. Export every URL. Crawl blog.example.com and pull the page list from Search Console, so posts with backlinks but no internal links don't get missed.
2. Choose a physical move or a reverse proxy. A physical move copies WordPress into public_html/blog. A reverse proxy leaves the blog where it is and serves it at /blog through Nginx's proxy module or Cloudflare Workers. Use the proxy route when the blog runs on a platform your main server can't host.
3. Update the WordPress URLs. Take a backup, change the site and home URLs, then run wp search-replace 'https://blog.example.com' 'https://example.com/blog' --all-tables to fix stored links.
4. Add the 301 redirects on the old subdomain. One rule in .htaccess covers every path:

apacheCopy
RewriteEngine On
RewriteCond %{HTTP_HOST} ^blog\.example\.com$ [NC]
RewriteRule ^(.*)$ https://example.com/blog/$1 [R=301,L]

5. Fix canonicals, sitemaps and internal links. Every canonical tag should point at the new path, and the old sitemap should be replaced rather than left live.
6. Keep the redirects for at least 12 months. Google advises holding them for a year or longer so signals fully transfer.

For trailing slashes, query strings and other edge cases, our 301 redirect htaccess examples have copy-paste rules. If you go the proxy route, pass the original Host and X-Forwarded-Proto headers correctly. Mismatched headers cause redirect loops and, now and then, a 400 Bad Request error that only appears on the proxied path.

Moving a WordPress blog from a subdomain to a subfolder requires a one-to-one 301 redirect for every URL, updated canonicals and sitemaps, and redirects kept live for at least 12 months. Some ranking movement for 2 to 6 weeks is typical while Google recrawls, and a drop that lasts longer usually points to broken or chained redirects.

The short version

• Google can rank both structures; the difference is how signals and settings get split.
• Default to a subfolder for blogs, guides and landing pages.
• Save subdomains for separate apps, hosted tools, staging copies and isolated teams.
• If you move, send every URL to its exact new home with a 301.

Your Next Step: Put Your Blog Where It Builds Authority

Now that you know the subdomain vs subdirectory for SEO choice mostly comes down to keeping your signals on one host, the setup is the easy part. You could wire up DNS, certificates and redirects yourself this weekend, or start on a server where both structures are a panel form away. Economy, $1.99/mo: NVMe storage, free SSL, 24/7 help from engineers who handle these moves every day, and a renewal price that matches your sign-up price. One honest caveat: if your project is a custom app that needs root access, a VPS will suit you better. Otherwise, tell Hostaccent what you're building and start on the Economy plan, backed by a 30-day money-back guarantee.

Frequently Asked Questions

Does subdomain vs subdirectory for SEO matter for a small site?

It matters less than content quality, but it still matters. A small site has few backlinks, so splitting them across two hosts hurts more than it would for a large brand. Keeping your blog at example.com/blog lets every link to your homepage support your posts from day one. If your site has fewer than 50 pages and runs on one WordPress install, a subfolder is the simpler and stronger choice.

Should I use a blog subdomain or subfolder?

Use a subfolder for a blog in almost every case. Blog posts usually target the same audience as your main pages, and they convert better when a reader can reach your products without crossing to another host. A subdomain makes sense only if the blog runs on separate software your main server can't host, or if a separate team manages it on its own schedule. Otherwise, example.com/blog is the stronger long-term home.

Does Google treat subdomains as separate websites?

For several systems, yes. Google treats a subdomain as its own site for site names in search results, and each subdomain has its own robots.txt and crawl pattern. Google also says it has no ranking preference between subdomains and subfolders, and a Search Console Domain property can report on all of them together. In practice, a new subdomain starts with fewer inherited signals than a new folder on an established domain.

How long does it take to move a blog from a subdomain to a subfolder?

The technical move usually takes 1 to 3 hours for a blog with a few hundred posts: copying files, updating URLs and adding the 301 rule. Recovery takes longer. Rankings often wobble for 2 to 6 weeks while Google recrawls the old URLs and follows the redirects. Keep those redirects live for at least 12 months, check Search Console's Pages report weekly, and fix any 404s as soon as they appear.

Do subdomains need their own SSL certificate?

Yes. Each subdomain needs a certificate that covers its exact hostname, either its own certificate or a wildcard such as *.example.com. Wildcard certificates from Let's Encrypt require DNS-based validation, which is harder to automate on some setups. On Hostaccent shared hosting, free Let's Encrypt SSL can be issued for each subdomain from the panel once its DNS record points to the server. Certificates renew every 90 days, so confirm auto-renewal is switched on.

Can a subdomain hurt my main domain's rankings?

Not directly. A well-run subdomain won't drag down your main site, and Google doesn't penalise the structure itself. Problems start when a subdomain hosts thin, spammy or third-party content, or when a hacked subdomain serves malware under your brand name, because Google may then question the quality of the whole domain. Keep every subdomain patched and relevant, remove abandoned ones, and noindex staging copies so they never compete with your live pages.