ccTLD vs Subfolder vs Subdomain for SEO
Three ways to structure a site across countries, what each one costs to run, and how Google actually treats them — with a decision process, not just a table.
A ccTLD (example.fr) starts a country's SEO from zero on its own domain; a subfolder (example.com/fr/) or a subdomain (fr.example.com) both keep it under your main domain, with a subfolder sharing more of that domain's authority than a subdomain does. Most sites should default to a subfolder unless a specific business reason argues otherwise.
That default is part of the wider multilingual SEO picture; this post is the full comparison behind that one-line recommendation, because the reasons to deviate from it are real and worth understanding before you commit to a structure.
On this page
What's actually different between the three?
All three point a URL at content for a specific country or language. The difference is what they share with your main domain, and how much of that sharing has to be built by hand.
| Structure | Example | Shares authority with main domain? | Setup effort |
|---|---|---|---|
| ccTLD | example.fr | No — starts as a separate domain | High: new domain, hosting, often a local entity |
| Subdomain | fr.example.com | Partially — closer to a separate property than shared | Moderate: DNS and hosting configuration |
| Subfolder | example.com/fr/ | Fully — same domain, same signals | Low: routing within existing hosting |
A ccTLD is registered and hosted as its own domain, which means it carries none of your main domain's backlinks, age or ranking history on day one. A subfolder is a path on the domain you already have, so it inherits everything that domain has already earned. A subdomain sits in between on paper, but in practice search engines have historically treated it closer to a separate property than a true subfolder, even though DNS-wise it is simpler to set up than a new domain entirely.
Think about it from a crawler's point of view rather than a URL's. A crawler discovers a subfolder the same way it discovers any other path on a domain it already knows and trusts — by following an internal link. A ccTLD has to be discovered as an entirely new domain, usually starting from an external link or a manually submitted sitemap, because nothing on your existing site points a crawler there automatically unless you build that bridge yourself. That discovery gap is a real, if often overlooked, part of why new ccTLDs tend to take longer to index than a new subfolder on an established domain — plan for it in your launch timeline rather than treating slow early indexing as a sign something is broken.
Which structure actually ranks best?
For most businesses, the subfolder. Google's own guidance on managing multi-regional and multilingual sites describes ccTLDs and country-specific hosting as location signals it uses to understand which market a page targets — not as a mechanism that improves how well that page ranks once targeting is clear [1]. A ccTLD tells a search engine "this page is for France" more explicitly than a subfolder does, but it does not make the content on that page better, and content quality is still doing most of the ranking work.
What the subfolder buys you instead is compounding. Every link earned by your main domain, every year it has existed, every piece of trust it has built — a new subfolder inherits all of it immediately. A new ccTLD inherits none of it and has to earn its own signals from a standing start, market by market, which is a slower and more expensive path to the same ranking outcome in most cases.
How much does each option actually cost to run?
More than the domain registration fee, in every case except the subfolder. A ccTLD often requires proof of local presence to register at all, ongoing renewal in a separate registrar, its own SSL and hosting configuration, and — in many countries — a locally registered business entity before you can even claim the domain.
ccTLD: domain, hosting, sometimes an entity
Registration and renewal fees vary widely by country; several require a local address or company registration before you can even buy the domain.
Subdomain: DNS and, often, separate hosting
Cheaper than a new domain, but frequently still means a second hosting environment or CDN configuration to manage alongside your main site.
Subfolder: routing within your existing setup
The lowest ongoing cost of the three — it is a path and a routing rule on infrastructure you are already paying for.
The ongoing cost matters as much as the setup cost. A ccTLD is a second domain to renew, secure and monitor indefinitely, for as long as that market stays live — a maintenance line that a subfolder simply does not create.
Does a subdomain count as a separate site to Google?
Functionally, closer to yes than to no. Even though a subdomain sits under your root domain in the URL, search engines have long treated subdomains as distinct enough that ranking signals do not transfer between them as completely as they do within a subfolder structure [1]. That makes a subdomain a strange middle option: it costs less to set up than a ccTLD, but it does not deliver the full authority-sharing benefit that makes a subfolder the default recommendation in the first place.
Where a subdomain does make practical sense is when a country or language version genuinely needs separate hosting infrastructure — different servers for latency reasons, a different CMS entirely, or a security or compliance boundary that a shared codebase cannot satisfy. In those cases the hosting requirement is the real driver, and the SEO trade-off is a cost you accept rather than a benefit you are chasing.
This is also the structure many companies reach for after an acquisition, when a newly bought regional business already runs on its own platform and migrating it onto the parent site's codebase is a multi-quarter engineering project rather than a routing decision. A subdomain lets that acquired site keep its own technology stack while still living under the parent domain, which is a pragmatic reason to accept the weaker authority-sharing — just be clear with stakeholders that the SEO cost is real, not a rounding error, and budget content and link-building for that subdomain as if it were closer to a new site than an extension of an established one.
When does a ccTLD actually make sense?
When the reason for it has nothing to do with SEO. A registered local business entity that regulation requires for that market. A domain extension that carries genuine trust with local buyers beyond what a subfolder can signal — a bank or a government-adjacent service is a plausible case. Hosting requirements a shared domain cannot meet, such as data residency law in a specific country.
A large enterprise entering a market with strict local regulation, or a brand that wants to present as fully domestic in a country where that matters commercially, are the clearest real cases. A small or mid-size business expanding into two or three new languages almost never has one of these reasons, which is why the subfolder remains the right default outside genuinely large or regulated operations.
There is also a competitive version of this question worth asking honestly: do your actual competitors in that market run on ccTLDs, and does that visibly correlate with anything beyond brand preference? A quick manual check of the top results for your core terms in that country tells you more about local buyer expectations than any general rule does, and it costs nothing but twenty minutes and a VPN.
Can you mix structures across markets?
Yes, and many sites do. A common pattern is subfolders for most new markets, with a single ccTLD reserved for one country where a local entity or hosting requirement is unavoidable — a company selling everywhere through example.com/xx/ subfolders except in a market where financial regulation requires locally hosted infrastructure under a local domain. This choice is not something you have to resolve identically for every country; the decision belongs to each market individually.
That said, mixing structures adds real operational complexity: two hosting environments, two sets of SSL and DNS to maintain, and a hreflang set that has to correctly link URLs across genuinely different domains rather than just different paths. Make the exception only where the underlying reason is strong enough to justify that ongoing cost.
How does this interact with markets outside Google?
If a market you are entering runs primarily on a search engine other than Google, the URL-structure calculus can shift. SEO for Baidu, Naver and Yandex covers three engines with their own hosting and domain preferences, some of which favor a local ccTLD and local hosting more strongly than Google's own guidance does for its index. Treat that as a market-specific exception to check before defaulting to a subfolder everywhere.
How do you actually decide, in practice?
Start from the subfolder as the default and require a specific, named reason to deviate from it for any given market — not a general sense that a ccTLD "feels more local." Write that reason down per market before building anything, because it is the test you will need again the next time someone asks why one country looks structurally different from the rest of the site.
Default to a subfolder for every new market
Start here unless a specific reason below applies. It is the cheapest option and the one that shares the most authority.
Check for a hard hosting or legal requirement
Data residency law, required local business registration, or infrastructure a shared domain genuinely cannot provide.
Check for a real trust or brand reason
A market where a local domain extension measurably changes buyer trust — not a guess, ideally something you can test.
Document the exception, market by market
If a ccTLD or subdomain is justified, write down why, so the decision can be revisited later against the reason that was actually given.
If you are choosing between platforms or an agency to execute whichever structure you land on, the best international SEO agencies reviews four options directly, and a WordPress site specifically weighing plugin-driven multilingual setups should read Weglot versus WPML before committing to either the structure or the tool that will maintain it.
Questions people also ask
Which structure is best for SEO: ccTLD, subfolder, or subdomain?
A subfolder in most cases, because it keeps every backlink and ranking signal pointed at one domain. A ccTLD or subdomain only earns its extra cost when the business reason for it — local hosting, a local entity, a distinct brand — outweighs starting that market's SEO from zero.
Does Google treat a subdomain as a separate site?
Largely yes, for ranking purposes. A subdomain is close enough to a separate property that it does not inherit the main domain's authority the way a subfolder does, even though it is easier to set up than a full ccTLD.
Is a ccTLD ever worth the cost just for SEO?
Rarely for SEO alone. A ccTLD is worth it when a market needs local hosting for speed, a registered local entity for trust or regulation, or a genuinely distinct brand — SEO benefits are a side effect of those decisions, not the reason to make them.
Can I switch from one structure to another later?
Yes, but it is a migration, with all the risk that implies: redirects, a temporary ranking dip, and rebuilt internal links. Choosing carefully the first time is cheaper than migrating a working structure later.
Do I have to use the same structure for every country?
No. Many sites mix structures — subfolders for most markets, a ccTLD for one country with a distinct legal or hosting need. The mix should follow the business reason for each market, not a rule that every market must match.
Sources
- Managing multi-regional and multilingual sites — Google Search Central (checked 23 September 2026)
- International and multilingual sites — Google Search Central (checked 23 September 2026)
- Tell Google about localized versions of your page — Google Search Central (checked 23 September 2026)
Get your URL structure reviewed before you build on it
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Multilingual SEO: a complete guide for 2026How multilingual SEO works: URL structure, hreflang, translation, keyword research and redirects, with what each decision costs and how to check it is working.
- Best International SEO Agencies (2026)Four agencies — a global network, a UK specialist, and two localization firms — reviewed on their own published pages, plus where we fit, bias disclosed.
- SEO for Baidu, Naver and YandexBaidu, Naver and Yandex rank pages differently from Google — mainland hosting, ecosystem content and behavior signals matter. What each one actually requires.
- Weglot vs WPML: which is better for SEO?Weglot is a translation proxy that works with any site; WPML is a WordPress plugin storing each language as native content. How they compare on cost and SEO.