Key takeaways
- **Subdomain SEO:** Subdomain SEO depends on whether the subdomain should stand alone or support the main site. The right structure is the one that makes authority, content, and reporting clearer.
For most sites, a subfolder (example.com/blog) outperforms a subdomain (blog.example.com) because it keeps all content under one domain that shares authority. Choose a subfolder unless a hard technical or organizational reason forces a subdomain.
The choice sets how search engines pool the authority your site earns. A subfolder consolidates it; a subdomain can split it. The gap is not universal, but on content that depends on organic search, teams that move a blog from a subdomain into a subfolder often report traffic climbing over the following months. Our website migration service can handle that move.
The core difference
A subdomain sits in front of the root: blog.example.com. Search engines can treat it as a related but separate site. A subfolder sits inside the root path: example.com/blog. It is unambiguously part of the same site.
That distinction drives the SEO gap. Authority signals, internal links, and topical relevance flow more freely inside a single domain than across a subdomain boundary. Google has said it can handle both, and it can. In practice, the subfolder removes the ambiguity rather than asking the crawler to resolve it.
It helps to see where the boundary actually sits. In a URL like example.com/blog, everything to the left of the first single slash is the domain, and /blog is a path inside it. In blog.example.com, the word blog is a label attached in front of the root domain, which makes it a distinct host. Crawlers and ranking systems key a lot of their site-level understanding off the host. Same host means the content is treated as one property by default. Different host means the crawler has to decide whether to treat the two as one site or two, and that decision is not always the one you want.
Comparison table
| Factor | Subfolder (example.com/blog) | Subdomain (blog.example.com) |
|---|---|---|
| Authority sharing | Pools with the main domain | May be evaluated separately |
| Internal linking | Counts as fully internal | Can be treated as cross-site |
| Setup complexity | Higher on some platforms | Easier to host separately |
| Analytics | One property, unified | Often needs separate tracking |
| Separate tech stack | Harder to isolate | Easy to run different software |
| Best for | Content that supports the core site | Distinct apps, stores, or locales |
When a subfolder wins
Pick a subfolder when the content exists to grow the main site's search visibility. A blog, resource library, guides section, or help center belongs in a subfolder because every article reinforces the domain's topical authority and every internal link passes value inside the same site.
If your goal is ranking the parent domain for more terms, the subfolder is the default. It is the reason many companies migrate a blog. subdomain onto a /blog path and watch the parent domain's keyword footprint widen over the following two quarters.
When a subdomain makes sense
Subdomains earn their place when content is genuinely separate:
- A web app or dashboard on app.example.com that runs a different stack from the marketing site
- A store on shop.example.com using a platform that cannot live in a subfolder
- Country or language versions such as fr.example.com when a subfolder structure is impractical
- A support portal on a third-party help-desk tool that only supports a subdomain
In these cases, the technical separation is the point. Forcing a subfolder through reverse proxies adds fragility for little SEO gain when the content is not there to lift the parent domain's rankings.
Reverse proxy: subfolder benefits without moving the stack
You do not always have to migrate the underlying platform to get the subfolder structure. A reverse proxy serves content from a separate system under the main domain's path, so example.com/blog can be powered by a hosted CMS while appearing as a native subfolder.
This is common when a marketing team wants their hosted blog platform to live at /blog instead of a subdomain. It gets the authority-sharing of a subfolder while the blog keeps running on its own software. The tradeoff is configuration complexity: the proxy has to handle paths, caching, and canonical tags correctly, or you trade one problem for another.
How to migrate from subdomain to subfolder
Moving blog.example.com to example.com/blog is a full migration, not a settings change. Treat it with the same care as any domain move:
- Crawl the subdomain and build a complete URL map. See url mapping for the full process.
- Stand up the subfolder structure and confirm every page renders correctly at its new path.
- Set 301 redirects from every subdomain URL to its matching subfolder URL, one to one.
- Update internal links to point at the new subfolder paths directly rather than through the redirect.
- Update the XML sitemap and submit it in Search Console.
- Re-crawl after launch to confirm every redirect returns a single 301 hop.
The redirects are the load-bearing step. Skip them and you strand every ranking the subdomain earned. If you are unsure whether the move is worth the disruption, what is website migration covers when a structural change earns its risk.
What the decision looks like in practice
Most teams do not need a study to make this call. A short set of questions settles it:
- Does this content exist to help the main domain rank? If yes, subfolder.
- Does it run on software that cannot live under the main site's path? If yes, and the content is not there to lift rankings, a subdomain is reasonable.
- Is it a separate product, locale, or app that users understand as its own thing? If yes, a subdomain matches the mental model and the tech.
- Are you moving it purely because a subdomain feels tidier? That is not a reason. Tidiness does not rank.
The most common mistake is defaulting to a subdomain because it is the easier thing to spin up, then discovering a year later that the blog on the subdomain never lifted the main domain the way a /blog path would have. The setup convenience is real, but it is a one-time saving paid for with ongoing authority that stays split.
Migration risks specific to this move
A subdomain-to-subfolder move has a few failure modes worth naming before you start:
- Duplicate content during the transition. If both the old subdomain and the new subfolder serve the same pages at once, set the canonical tags to the subfolder and get the 301s live quickly so search engines do not index two copies.
- Analytics discontinuity. A subdomain often has its own tracking property. Plan the handoff so the new subfolder traffic reports into the main property without a gap that looks like a traffic drop.
- Internal links left pointing at the subdomain. Every internal link to blog.example.com should be rewritten to example.com/blog, so clicks do not route through a redirect.
- Backlinks that never update. External sites will keep linking to the subdomain for years. That is exactly why the 301s have to stay live long-term, not just through launch week.
None of these sink the move on their own, but skipping any of them turns a clean structural upgrade into a slow recovery.
What the choice does not fix
Structure is a multiplier, not a source. A subfolder will not rank thin content, and a subdomain will not sink strong content on its own. If a blog underperforms on a subdomain, moving it to a subfolder helps only when the content is worth ranking in the first place.
Decide structure for the right reason: to remove ambiguity and pool authority where it belongs. Then let the content quality do the ranking.
Related terms
You may see this topic described with related searches like does subdomain affect seo, domain vs subdomain, root domain vs subdomain, seo subdomain vs subdirectory, and subdomain and seo. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.
Related searches such as subdomain for seo, subdomain vs subdirectory, subdomain vs subdirectory seo, subdomain vs subfolder seo which is better, and subfolder vs subdomain are useful when they clarify what the reader needs next. They should support the same plan rather than pulling the page in several directions at once.
Frequently asked questions
Does Google officially prefer subfolders over subdomains?
Google states it treats both fairly and can consolidate signals across subdomains. In observed outcomes, subfolders remove ambiguity and tend to consolidate authority more reliably, which is why many teams see gains after moving content from a subdomain into a subfolder.
Will moving my blog to a subfolder guarantee more traffic?
No. The move helps when the content is worth ranking and the redirects are done correctly. It removes a structural drag on authority sharing, but it does not improve thin or low-demand content. Expect a lift over one to two quarters when the underlying content is strong.
Is a reverse proxy worth the added complexity?
It is worth it when you want subfolder authority but cannot move the platform, such as a hosted blog you want at /blog. The catch is that the proxy must handle paths, caching, and canonicals correctly. Done wrong, it creates duplicate-content and crawling problems.
How risky is a subdomain-to-subfolder migration?
It carries the same risk as any migration: the danger is in the redirects, not the structure. With a complete URL map and one-to-one 301s, the risk is controlled. Skip the mapping step and you can lose the rankings the subdomain built.
Do subdomains and subfolders affect anything besides SEO?
Yes. A subdomain is easier to host on separate infrastructure, run on a different tech stack, and secure or scale independently, which is why apps and stores often live on one. A subfolder ties the content to the main site's hosting and platform. When the deciding factor is engineering separation rather than rankings, a subdomain can be the right call even though it splits authority.
Can I use both a subfolder and a subdomain on the same site?
Yes, and many sites do. Keep marketing content that supports rankings in subfolders, and put genuinely separate systems, such as an app or a store on a different platform, on subdomains. The point is to match the structure to the purpose of each section rather than forcing everything into one pattern.
How do you do internal linking for SEO?
Use internal links to show which section owns the topic. Link from the main domain to the subdomain or subfolder pages that need authority, use descriptive anchor text, and make sure important pages are reachable from hub pages, navigation, and related articles.
What are the 4 types of website structure?
A strong website structure groups related pages clearly, keeps important pages close to the main navigation, and uses internal links to show which pages matter most. For local SEO, the structure should also separate each location and core service cleanly.
How to do internal linking for SEO?
Build links from the pages with authority to the pages that need help ranking. Keep anchor text specific, avoid orphaned pages, and connect each page to the closest parent topic so Google can see how the structure fits together.
What website structure is best for SEO?
A strong website structure groups related pages clearly, keeps important pages close to the main navigation, and uses internal links to show which pages matter most. For local SEO, the structure should also separate each location and core service cleanly.
Which website structure is the best?
Choose the option that fits the goal, budget, risk, and team that will run it. A good choice should make the next step clearer, not add complexity that nobody owns.
Get help deciding and migrating
If you are weighing a subdomain against a subfolder, or planning a move between them, our website migration service team maps the URLs, sets the redirects, and verifies the result so the structure change adds visibility instead of costing it.