Subdomain vs Subfolder: Making the SEO Decision

A company is about to launch a blog. The engineering team wants blog.example.com so the blog can live on its own stack. The marketing team wants example.com/blog so the main domain "keeps the strength". The same argument returns for the store, the help center and the second language. The subdomain versus subfolder question is usually presented as an SEO decision, yet it is just as much an infrastructure, measurement and operations decision.

This article will not tell you which one is automatically superior, because the evidence we can cite does not support such a verdict. Instead it makes the trade-offs visible: it defines the terms, separates what Google's documents say from what they leave out, walks through a blog, a store, a help center and a language version one by one, and lists the steps for moving from one structure to the other.

Subdomain vs Subfolder: Why the Decision Matters

This is one of the choices that is expensive to reverse. When a URL structure changes you need redirects, new measurement set-ups, updated sitemaps and internal links, and search engines need time to settle on the new layout. During that period traffic can fluctuate. So "leave it as it is for now" is also a choice, with a price that arrives later.

What makes it hard is that no single answer fits everyone. The same structure that works smoothly at one company creates measurement, security and maintenance problems at another. The outcome depends on your team's infrastructure skills, how closely the content relates to the main site, your language and region plans, and what you need to measure.

So begin by asking a better question. Instead of "which is better for SEO", ask whether this section is a natural part of the main site or a separate product that happens to share a brand. Who owns it, how is it published, and which technology runs it? The answers often decide the matter before any SEO argument begins.

Definitions and URL Examples

Let us pin down the terms. A subfolder (also called a subdirectory) is a path under the main domain, like a folder: example.com/blog/. A subdomain is a label added to the left of the main domain: blog.example.com. A third option, a country-code domain such as example.de, is a separate domain and appears here only in the multilingual section.

To a visitor the first two look similar, but technically they sit in different places. A subfolder belongs to the same site and usually runs on the same application, configuration and session cookies. A subdomain can be set up as a separate application, server, host or even a different content management system, and cookies and sessions are not shared automatically by default.

The general rules of URL design, such as readable words, consistent casing and fewer parameters, are covered in URL structure and slug practices, so we do not repeat them. This article asks a different question: which part of the address belongs in the domain and which belongs in the path?

Before writing the decision down, take a snapshot of what you have now. Which sections live at which address, which systems publish them, and which teams manage them? In many companies that list answers half the debate on its own.

What Google Says About Subdomains and Subfolders

Care is needed here. Google's documentation on multi-regional and multilingual sites compares three URL structures in a table: a country-specific domain, subdomains on a generic domain and subdirectories on a generic domain. For subdomains the pros listed are easy set-up, the ability to use different server locations and easy separation of sites, and the con is that users may not recognise the targeting from the URL alone. For subdirectories the pros are easy set-up and low maintenance on the same host, and the cons are a single server location, harder separation of sites and the same recognition issue.

What the document establishes is that each structure carries different operational costs. What it does not say is that one of them ranks higher than the other. Google's URL structure documentation likewise gives a country-specific domain or a country-specific subdirectory as examples of recommended set-ups for multi-regional sites, and offers no ranking verdict between a subdomain and a subfolder.

That is why strong claims deserve caution, such as "Google prefers X" or "a subdomain inherits the main domain's authority". We did not find those statements in these documents. If you read them elsewhere and cannot confirm them in an official source, do not make them the reason for a decision. What actually happens on your own site you can measure with your own data.

The practical conclusion: when choosing a structure for SEO purposes, base the choice on the operational trade-offs these documents list, namely set-up effort, maintenance, separation and clarity of targeting. Treat claims of a ranking advantage as unverified assumptions rather than rules.

Advantages of a Subfolder

For many businesses a subfolder is the default because it simplifies work in a specific direction: one domain, one server or application, one measurement configuration. Each of those makes daily work easier.

• Management under one roof: One certificate, one set of redirect rules, one sitemap approach. A change is made once.
• Simpler measurement: Analytics and search console data sit in one property, and visitor movement between sections is visible without extra effort.
• Link management: Links to your blog land directly in the main domain's profile, so you monitor one profile in one place.
• Internal links and navigation: Menus, breadcrumbs and related-article links can be built in the same system with the same template logic.

How a site's structure reads to people and crawlers is the subject of site architecture and breadcrumbs for SEO. In a subfolder this structure is usually more direct to build, because navigation stays inside a single application.

A subfolder has costs too. Hosting and software are concentrated in one place, so if the blog runs on a different technology, you may need extra infrastructure such as a reverse proxy in front of the main site. Separation becomes harder: a security issue in one section, a mistaken release by one team or a heavy plugin can affect the whole site. Seeing these costs early lets you weigh the advantages realistically.

When a Subdomain Is Justified

A subdomain is not a poor choice. Under the right conditions it is the sensible one, provided the reason is an operational need rather than an SEO myth.

A subdomain makes sense in situations like these:

1. A separate product or platform: The section runs on independent technology managed by a different team, for example a hosted help-center product supplied by a vendor.
2. Security separation: You want to isolate a section that accepts user content, runs third-party code or has different security requirements from the main site's cookies and privileges.
3. Different server location: The section must be hosted in another region. Google's multi-regional document lists this among the pros of subdomains.
4. Ownership and an independent release flow: A separate team publishes on its own schedule and manages its own deployment calendar.

With these reasons in place, no SEO rule forces the section into the main domain. You simply accept the cost knowingly: measurement is configured separately, links are watched separately, and movement between sections and internal linking need extra care.

On the other hand, choosing a subdomain "because it was technically easier" is often a decision people reverse later. Ask who the ease is for: today's developer, or the team that will manage the content for the next two years?

Choosing for a Blog, a Store and a Help Center

The logic differs across these three typical sections, so instead of one rule, run a short assessment for each.

Blog: If the content relates directly to the main site's topic and points readers to product pages, a subfolder usually makes life easier because measurement and internal linking stay in one place. If the blog operates as a separate publication or runs on a different publishing system, a subdomain is also reasonable.

Store: If the store is the core of the main site, a subfolder or the main domain itself is the natural fit. If the store runs on a hosted checkout platform, a subdomain is sometimes a technical requirement. In that case test the measurement set-up and session continuity across domains from the beginning.

Help center: Many support products serve their hosted version on a subdomain. If you want support content to appear in search, what matters is not only the address but also whether the content is crawlable and useful. Evaluate whether moving it onto your own server is possible and what that would cost.

Consider a hypothetical four-person team that sells printed notebooks. Its shop already runs on the main domain, its help articles come from a vendor that serves them on a subdomain, and its writer wants a blog. In this invented example the blog shares the shop's topic and tools, so the team keeps it in a subfolder and leaves the vendor's help center where it is. Your answers may point elsewhere.

For all three, the redirect rules matter as much as the address. Consistency issues such as www versus non-www, HTTPS and trailing slashes apply to every structure; the details are in www vs non-www, HTTPS and trailing slash standardization. When you add a new section, apply that standard to its address as well.

Multilingual and Multi-Regional Sites

For language versions there are usually three options: a country-code domain, a subdomain or a subfolder. Google's document on multi-regional and multilingual sites compares them in a table. A country-code domain gives clear geotargeting and easy separation but is expensive, needs more infrastructure and targets only one country. A subdomain is easy to set up and allows different server locations, but users may not tell whether "de" means a language or a country. A subfolder is easy to set up and cheap to maintain on one host, but it has a single server location and makes separation harder. Read the source yourself: managing multi-regional and multilingual sites (Opens in a new tab).

Whichever structure you choose, language versions have to point at each other. How that mapping is built and checked is described in hreflang audit: language and region tags. The structure decision does not replace hreflang, and hreflang does not make the structure decision for you; the two complement each other.

The link side of a multilingual site is also shaped by structure. You need to track which version receives which links, a topic covered in international and multilingual backlink strategy. Factor that in as you choose: a subfolder gives you one domain profile, while country-code domains each need their own profile to monitor.

When deciding, ask who will manage the language versions and how independently they will operate. For a small team, keeping everything under one structure is usually easier to run. If regional teams have their own infrastructure and legal requirements, a more separate structure can be justified.

Measurement, Backlink and Security Issues With Subdomains

Choosing a subdomain creates extra work in three areas. Knowing them in advance lets you decide with the cost in view.

Measurement: Your analytics tool may need cross-domain tracking for the subdomain, otherwise a visitor moving from the main site to the blog looks like two separate sessions. In search console, check how properties are set up (a domain property or separate properties) and plan how you will combine reports.

Backlinks: You may need to monitor link profiles in two places. How links to a subdomain appear in the overall picture of the main domain depends on the tool you use, and those displays are specific to each tool, not Google values. So instead of declaring that a subdomain passes link strength or does not, track the two sections separately with your own tools and data.

Security: Subdomains can share some cookies and trust relationships with the main site. If you point a subdomain at a third-party service, DNS records must stay current and unused subdomains should be removed. The risk of an abandoned record being claimed by someone else is part of this maintenance discipline.

These three points are not obstacles; they are a maintenance checklist. If the team can keep it up, a subdomain causes no trouble. If it cannot, a simpler structure is the wise option.

Moving From One Structure to the Other

Moving an existing subdomain into a subfolder, or the reverse, is a site move and calls for the same discipline. Google's guidance on site moves with URL changes lists the main steps: server-side permanent (301) redirects from old URLs to new ones, mapping every old URL to its new address, updating canonical tags, hreflang annotations and internal links, creating a sitemap of the new URLs, verifying both old and new properties in search console, and monitoring the process. It also suggests timing the move for a lower-traffic period, moving all URLs at once on small to medium sites, and changing only one thing at a time. See the source: site move with URL changes (Opens in a new tab).

How to protect link value during a move is the topic of preserving backlink value during site migration. After the move, the most common technical problem is redirect chains and loops, and finding and fixing them is explained in redirect chains and loops: how to fix.

We cannot give a number for the ranking effect of a move; fluctuation after the move is normal and its length varies by site. What matters is complete redirects and regular monitoring. Before deciding to migrate, ask whether the problem with the current structure is large enough to be worth solving. A move undertaken for a minor annoyance may not justify months of volatility.

Questions to Ask at the Moment of Decision

Answer the following in writing before you enter the meeting. The answers will often settle the matter themselves.

• Is this section a natural extension of the main site, or an independent product?
• Which technology and which team run it? Could it run on the same infrastructure as the main site?
• Is there a security or data-separation reason?
• Can we collect measurement in a single property, or do we need cross-domain tracking?
• How often, and with which tool, will we monitor the link profile?
• What is our language and region plan? Which versions will be added in the next two years?
• If we have to change the structure later, can we afford the cost?

If your answers conflict, with some pointing to a subdomain and others to a subfolder, give the weight to operational need. An SEO rationale alone is not strong enough to force one structure; you can see that from the documents above and from your own data.

Record the outcome as a decision log: date, reasoning, accepted costs and a review date. Someone reopening the question in two years should be able to see which assumptions the choice rested on.

Example Template: Subdomain and Subfolder Decision Matrix

The matrix below summarises tendencies for typical sections. The judgments are a general guide, so adapt them to your own conditions. Read the columns as starting assumptions, not verdicts.

Rename the rows to match your own sections and assign an owner to each. If both structures look equal on a row, choosing the one with the lower maintenance load is a reasonable tie-breaker.

Frequently Asked Questions

Is a subdomain or a subfolder better for SEO?

Google's documents do not rule in favour of either one for rankings. The multi-regional guide lists different set-up, maintenance and separation costs for each. Decide on your operational conditions: team, technology, measurement needs and language plan.

Should I keep my blog on a subdomain or in a subfolder?

If the blog covers the main site's topic and can share its infrastructure, a subfolder keeps measurement and internal links simple. If it runs on a separate publishing system or with a separate team, a subdomain is reasonable. Record the accepted costs either way.

Does a subdomain share the main domain's authority?

We could not confirm that in Google's documents, so we do not state it as fact. Tools may show subdomain links differently, and those displays are specific to the tool, not Google values. Track both sections separately with your own data.

Which structure suits a multilingual site?

Google's multi-regional guide compares country-code domains, subdomains and subfolders. A subfolder is often chosen for a small team and low maintenance, while a subdomain can be justified by a different server location or an independent team. Verify the hreflang mapping in every case.

Is moving from a subdomain to a subfolder risky?

Every move is a site move and fluctuation may follow. Risk grows when redirects are incomplete or monitoring is skipped. Follow Google's steps on permanent redirects, mapping and monitoring, and expect no promised ranking outcome.

What data should I look at before deciding?

Start with operational facts: who runs the section, its technology, security needs, measurement set-up and language plan. Then check traffic, crawl and conversion behaviour in your search console and analytics. Read several indicators together instead of relying on one metric.

Conclusion and Next Step

The decision point is this: is there a concrete operational reason to separate the section from the main site? If there is, a subdomain can be chosen knowingly, with its costs accepted. If not, a subfolder is usually the lower-maintenance path for most businesses. An SEO argument alone does not settle it.

Once you have decided and want to look at execution, the how it works page at Akua Adforce shows the order flow: selection, cart, payment, seller approval, delivery notice and the dispute path. For a lasting choice such as site structure, answer the questions above in writing first and, if possible, test the idea on one small section.