By Hridoy Ahmed | Last updated: November 2026 | 12 min read
Short answer: For most sites, a subfolder such as
example.com/blogis the simpler choice. It keeps everything in one site, one set of settings and one internal link structure. Google says it works with both. Choose a subdomain only when the section is truly separate: a different platform, team, audience or risk level. Pick the setup you can keep for years, because switching later costs real work.
In this guide
- The difference in one table
- What Google says, and what nobody can prove
- Where the real differences show up
- The 6-question test
- Common use cases
- The WordPress angle
- When and how to switch
- Mistakes to avoid
- FAQ
The difference in one table
| Subfolder | Subdomain | Separate domain | |
|---|---|---|---|
| Example | example.com/blog/ | blog.example.com | exampleblog.com |
| Part of the same host? | Yes | No, a different host | No |
| Own robots.txt file? | Shares the main one | Yes, its own | Yes, its own |
| Typical reason | Content that belongs with the main site | A different platform, team or purpose | A different brand |
A subdomain is a prefix before your main domain name. A subfolder is a path after it. To visitors, both can look natural. To servers, crawlers and tools, they behave in different ways.
What Google says, and what nobody can prove
Google’s John Mueller said in a 2017 Search Central video that Google Web Search is fine with using either subdomains or subdirectories. He added that you should verify subdomains separately in Search Console, and that you should pick a setup that suits your plans for the longer term. I have not seen Google publish anything since that reverses this advice.
Many SEO writers still claim that subfolders rank better. Some report traffic gains after moving a blog from a subdomain to a subfolder. These stories are not controlled tests. Other changes often happen at the same time, such as new redirects, better internal links and updated content. So I treat the idea that “subfolders pass more authority” as unproven. It is a risk to plan for, not a law.
That leaves a more useful question: which setup is easier to run well for your site?
Where the real differences show up
| Area | Subfolder | Subdomain |
|---|---|---|
| Search Console | One property covers it | Needs its own verification, or a Domain property that includes all subdomains |
| robots.txt and sitemaps | One file and one sitemap set for the host | Each subdomain needs its own robots.txt and sitemap |
| Internal linking | Normal internal links inside one site | Links between hosts are harder to plan and measure |
| Analytics | Simple | Needs careful tracking setup across hosts |
| Platform and hosting | Same CMS and server, or a proxy setup | Can run on a different CMS, host or team |
| Security and risk | A problem on one area is a problem on the site | Easier to isolate risky or experimental areas |
| Cost to change later | High | High |
Notice the last row. Neither choice is free to reverse. That is why the decision matters more than the label.
The 6-question test
Instead of asking which is “better”, answer these six questions about the section you plan to build.
- Is it part of the same business and audience as the main site? If yes, lean to a subfolder.
- Must it run on a different platform or server? If yes, a subdomain is much easier. A proxy can place a separate platform under a path, but it adds complexity.
- Will a different team run it on its own release schedule? If yes, a subdomain gives them freedom.
- Should it rank for the same topics as your main pages? If yes, keeping it in a subfolder lets you link the content together as one topic cluster.
- Is it high-risk? Examples are user-generated content, a login area or an app. If yes, a subdomain can isolate it.
- Can you keep this setup for the next several years? If you are unsure, pick the one that is cheapest to maintain.
Here is how I read the answers.
| Your answers | Lean toward |
|---|---|
| Yes to 1 and 4, no to 2, 3 and 5 | Subfolder |
| Yes to 2, 3 or 5, no to 4 | Subdomain |
| Mixed answers | Subfolder, unless a technical limit forces a subdomain |
If the answers are mixed and you want a second opinion on your own structure, my technical SEO service includes a site structure review.
Common use cases
| Section | Usually better | Why |
|---|---|---|
| Blog or articles | Subfolder | Content supports your main pages and shares internal links |
| Landing pages | Subfolder | Same brand, same audience |
| Help center or docs | Either | Subfolder if search traffic matters. Subdomain if the platform requires it. |
| Web app or customer dashboard | Subdomain | Separate system, login required, little search value |
| Online store on a separate platform | It depends | If the store is the business, keep it with the main site when you can |
| Languages | Subfolders or separate country domains | Clear structure. Use hreflang. See the hreflang guide. |
| Staging or testing | Subdomain, kept private | Easy to separate. See WordPress staging sites. |
| Community forum | Either | Choose by moderation load and platform |
The WordPress angle
A normal WordPress site. Your blog and pages already live in one install. Use a subfolder structure and keep URLs short and readable. My guide on SEO-friendly URL structure covers the details.
WordPress Multisite. When you set up a network, WordPress asks whether sites should use subdomains or subdirectories. This is hard to change later, so decide first. Each site in the network behaves like a separate site for settings, sitemaps and plugins.
Blog on WordPress, main site elsewhere. This is the most common reason for a subdomain. Your store or landing pages run on another platform, and WordPress runs the blog on blog.example.com. It works. You can also place WordPress under a path with a reverse proxy at the server or CDN level. That keeps one hostname, but it needs careful setup for caching, cookies, canonical tags and redirects. Do it only if someone can maintain it.
Whatever you choose, link the sections to each other on purpose. My guide on internal linking for topic clusters shows how.
When and how to switch
Do not switch because an article told you to. Switch when the current setup causes a real problem you can name: the content belongs with the main site, the split makes reporting and linking painful, or the platform no longer fits. Be honest with yourself about the result. A switch can bring gains, but nobody can promise it, and rankings often move for a while.
If you move a section from a subdomain to a subfolder, use this plan:
- Crawl the old section. Save every URL, title and traffic figure.
- Build the new section. Keep the content the same at first. Change one thing at a time.
- Map old URLs to new URLs one by one. Use 301 redirects. Do not send everything to the homepage.
- Update internal links, canonicals, sitemaps and hreflang to the new URLs.
- Check robots.txt and noindex rules on the new location, so you do not block the move by mistake.
- Test the redirects. Use my guide on checking redirects to find chains and loops.
- Watch Search Console. Compare clicks and indexed pages for the old and new sections for several weeks.
- Keep the redirects. Google’s site move guidance says to keep them for at least a year.
A move like this follows the same logic as a site migration. See how to migrate WordPress without losing SEO, and how to change your domain name for the Search Console steps. If you want help with the move itself, see my WordPress migration service.
Moving a section from a subfolder to a subdomain is rarely worth it, because you give up the simplicity of one site.
Mistakes to avoid
- Choosing a subdomain because the platform default did. Check whether the platform can use a path instead.
- Splitting one topic across hosts. A guide on the main site and its follow-up on a subdomain are harder to link as a cluster.
- Forgetting the second robots.txt. A subdomain has its own file, and a mistake there affects only that host.
- Not verifying the subdomain. Without it you cannot see its search data. A Domain property covers all subdomains.
- Creating many thin subdomains at scale. For example one per city with the same text. That looks like spam, no matter the structure.
- Leaving a staging subdomain public. Protect it and keep it out of the index.
- Moving back and forth. Each move is a mini migration. Decide once.
FAQ
Does Google treat a subdomain as a separate site?
Search Console treats it as a separate host that you verify and track on its own. Google says it handles both setups fine for web search. How much a subdomain shares with the main site is not fully public.
Will moving my blog to a subfolder raise my traffic?
It might, but nobody can promise it. Reported gains are not controlled tests, and moves can cause temporary losses. Do it for a clear structural reason.
Which is better for a new site?
Usually a subfolder, because it is simple and keeps all content in one place. Choose a subdomain only for a separate platform, team or risk area.
Can I use both on the same site?
Yes. Many sites keep content in subfolders and put an app or help center on a subdomain. Keep each section’s purpose clear.
Not sure how your site should be structured? I review your URLs, platforms and goals, then recommend a setup and a safe migration path if you need one. See my SEO and technical SEO service.
About the author: Hridoy Ahmed is an SEO specialist and WordPress security expert based in Dhaka, Bangladesh. He has 8+ years of experience and works with clients worldwide.
