Your international site structure comes down to three options: a ccTLD (example.in), a subdomain (in.example.com), or a subdirectory (example.com/in/). None of them ranks better by default — Google has said so directly. What they change is how link authority flows, how strong your country signal is, and how much work your team carries to keep it all running.
This guide breaks down the real trade-offs so you can pick a structure that fits your markets, your team, and the authority you already have — instead of copying whatever a competitor happened to choose five years ago.
The three international URL structures at a glance
Every international structure is a variation on where you put the country or language signal in the URL. Here is how they compare on the factors that actually matter.
| Factor | ccTLD (example.in) | Subdomain (in.example.com) | Subdirectory (example.com/in/) |
|---|---|---|---|
| Local trust signal | Strongest | Weak | Weak |
| Geotargeting | Automatic, locked | Manual in Search Console | Manual in Search Console |
| Authority sharing | None — starts at zero | Partial | Full — shares root domain |
| Server/hosting flexibility | High | High | Lower |
| Setup + maintenance cost | High | Medium | Low |
| Best for | Trust-sensitive markets | Distinct regional platforms | Most sites, most of the time |
A useful way to read this table: ccTLDs optimize for local trust, subdirectories optimize for authority efficiency, and subdomains sit uncomfortably between the two. Keep that framing in mind as we go deeper.
Structure is only one piece of a working setup. Before you commit, read the international SEO overview so you understand where structure fits alongside hreflang, targeting, and content.
ccTLDs: local trust vs earning authority from scratch
A country code top-level domain — .in, .de, .co.uk, .fr — is the clearest possible statement that a site belongs to a specific country. Google reads it as an unambiguous geotargeting signal, and users read it as a mark of local legitimacy. In markets where buyers actively distrust foreign domains, that trust converts.
The catch is authority. Search engines evaluate each domain largely on its own backlink profile. A brand-new example.in inherits none of the ranking strength your example.com spent years building. You are effectively launching a fresh site and ranking it one link at a time.
When a ccTLD earns its keep
- Trust-sensitive verticals — finance, healthcare, legal, government services — where a local domain lifts click-through and form completions.
- Priority markets big enough to justify a dedicated content and link-building program per domain.
- Regulatory or payment reasons that require a local legal entity and domain anyway.
If you go this route, budget for real per-market international link building. Ten ccTLDs with thin backlink profiles will underperform one strong subdirectory setup every time. The structure is only as good as the authority you can pour into it.
Subdomains: separation with diluted link equity
A subdomain — in.example.com — gives you a clean technical boundary. You can host it on separate infrastructure, hand it to a different regional team, or run a different CMS behind it without touching the main site. That operational separation is the genuine reason to choose a subdomain.
The SEO story is murkier. Google treats subdomains as part of the same overall site, but the way authority flows between a root domain and its subdomains has historically been less reliable than authority flow inside a single domain. You get some of the brand halo — users recognize example.com in the URL — without the locked geotargeting of a ccTLD or the clean authority consolidation of a subdirectory.
That middle position is why subdomains are often the weakest default for pure international targeting. They make more sense when the regional site is genuinely a different product or platform — a separate marketplace, a localized app portal, a distinct support hub — rather than the same site in another language.
Whichever you choose, your hreflang tags still have to map every language-region pair correctly. Structure never replaces annotation.
Subdirectories: shared authority and simpler management
A subdirectory — example.com/in/ or example.com/de/ — keeps everything under one domain. Every backlink to any page, in any market, strengthens the same domain. That authority consolidation is the single biggest reason subdirectories are the pragmatic default for most international sites.
The management story is just as favorable:
- One SSL certificate, one domain, one analytics property to maintain.
- New markets launch fast — spin up a folder, add content, set targeting, done.
- Wins compound — a link earned for your US content quietly helps your India and Germany folders rank too.
The main constraint is technical flexibility. Everything shares one domain and typically one hosting stack, so a regional team can't easily run separate infrastructure. For the vast majority of businesses, that trade is worth it. If you're standing up several markets on a lean team, subdirectories plus disciplined multiregional website SEO practices will get you further than any other structure.
How each option affects geotargeting and cost
Geotargeting and cost are where the abstract trade-offs become concrete line items.
Geotargeting. A ccTLD is auto-associated with its country and you cannot override it — .in always means India to Google. Subdomains and subdirectories carry no built-in country signal, so you set geotargeting manually in Google Search Console's international targeting settings, or you rely entirely on hreflang and on-page signals. Generic TLDs like .com, .org, and .io are treated as geo-neutral, which is exactly why the manual step matters. Get your geotargeting Google configuration right or the folders sit in limbo.
Cost. Here is a rough picture of what each structure demands over its life.
| Cost area | ccTLD | Subdomain | Subdirectory |
|---|---|---|---|
| Domain registration | Per market, recurring | One domain | One domain |
| Authority building | High — from zero, per domain | Medium | Low — shared |
| Technical maintenance | High | Medium | Low |
| Team/ops overhead | High | Medium | Low |
A five-market ccTLD strategy means five registration renewals, five backlink programs, and five sites to audit. The same five markets as subdirectories share one domain's authority and one audit surface. Run periodic crawls with a tool like DeployFlare's site audit so a structure change doesn't quietly leave orphaned or mis-tagged pages behind.
A decision framework for choosing your structure
Work through these questions in order and the answer usually falls out on its own.
- Does local trust drive conversions in this market? If a local domain measurably lifts click-through or sales — common in finance, healthcare, and some emerging markets — lean toward a ccTLD for that market specifically.
- Do you have a dedicated SEO and content team per market? ccTLDs need per-domain authority building. No dedicated resource? Default to subdirectories.
- Is the regional site a genuinely different product or platform? If it runs on separate infrastructure or a different CMS, a subdomain is defensible. If it's the same site in another language, it usually isn't.
- How many markets, how fast? Many markets on a lean team strongly favor subdirectories — they're the cheapest to launch and the easiest to keep consistent.
- How much authority do you already have? A strong root domain is an asset you shouldn't throw away. Subdirectories keep it; ccTLDs make you rebuild it.
Most sites should start with subdirectories and only graduate to a ccTLD in a specific market once the numbers justify the overhead. A common mature pattern is hybrid: a flagship ccTLD in one or two priority markets, subdirectories for everything else. That works fine as long as your hreflang mapping stays clean across the mixed structure.
Whatever you pick, pair it with market-appropriate translating website SEO and real local keyword work from international keyword research. Structure sets the stage; content and links win the market.
The one-line answer
If you want a default: use subdirectories, set geotargeting in Search Console, get hreflang right, and reserve ccTLDs for markets where local trust is worth the cost of ranking a brand-new domain from scratch. Structure is a signal, not a shortcut — the fundamentals still decide who wins.