ccTLD vs Subfolder vs Subdomain for International SEO

The ccTLD vs subfolder vs subdomain question comes up on almost every international project I take on.

And the honest answer is boring: for most businesses, subfolders win.

But "most" isn't "all". Your budget, your teams and how separate each market needs to be all change the answer.

It's also the first thing I settle in any international SEO engagement, because hreflang, content and links all build on it.

Below, you'll see how the three compare on country signal, authority, cost, flexibility and how hard each one is to undo.

ccTLD vs Subfolder vs Subdomain at a Glance

Here's the short version, based on Google's documentation and the international setups I've worked on:

If you only read one row, read "Authority".

For small and mid-sized businesses, that's the factor that decides most outcomes, because links are expensive and slow to earn.

What Each Structure Actually Means

Before you compare them, it helps to be precise about the terms.

ccTLD

A ccTLD is a country-code top-level domain: .de for Germany, .fr for France, .co.uk for the United Kingdom.

Each market you enter gets its own domain, such as brand.de and brand.fr.

Subfolder

A subfolder, also called a subdirectory, puts each market in a folder on one generic domain such as a .com.

So you'd run brand.com/de/, brand.com/fr/ and brand.com/en-gb/.

Subdomain

A subdomain puts each market in front of your main domain: de.brand.com, fr.brand.com.

Technically, a subdomain can live on entirely different servers from the main site.

Note: Whichever structure you choose, it only labels the versions. You still need hreflang to tell Google which pages are equivalents. My guide on what hreflang is explains how that works.

ccTLDs Send the Clearest Country Signal

Google's guide to managing multi-regional sites says ccTLDs give users and search engines a strong signal that a site is intended for a certain country.

That's the big advantage. Nobody wonders who brand.de is for.

Google lists other benefits you get:

• clear geotargeting
• server location becomes irrelevant
• easy separation of sites

There may be a trust angle as well. In some markets, shoppers may prefer a local domain.

That's something you should test with real customer feedback, not assume.

Where ccTLDs Fall Short

The downsides you take on are real, and Google lists most of them:

• Cost. Domains can be expensive or unavailable.
• Infrastructure. More domains to host, secure, renew and monitor.
• Rules. Some ccTLDs have strict registration requirements, such as a local presence.
• One country each. A .de can't target Austria and Switzerland as well.

The cost Google doesn't spell out is the one I see hurt most: authority.

Each new domain starts with no links. Every market you add needs its own link building effort, and its own content, before it can compete.

ccTLD Verdict

Choose ccTLDs when each market runs like a separate business, with local staff, local budget and the patience to build each domain from scratch.

Skip them if one central team will run every market.

Subfolders Keep Everything Under One Roof

Subfolders are the structure I recommend most often.

Google lists their advantages simply: easy to set up, and low maintenance because everything sits on the same host.

The practical upside for you goes further:

• One domain's authority. In my experience, links earned by any market tend to support the others, because they all point at one domain.
• One platform. One CMS, one deployment, one set of templates to fix.
• One set of tools. One Search Console property and one GA4 setup, segmented by folder.

If you're entering your first two or three markets, that's a big head start. A new /de/ folder on an established domain doesn't start from zero.

Where Subfolders Fall Short

Google names two downsides you should weigh: a single server location, and harder separation of sites.

The server point matters less than it sounds.

Google itself says server location isn't a definitive signal, because content delivery networks serve pages from around the world.

Separation is the real cost. Every market shares your templates, plugins and release cycles.

So a change made for one country can break another. I've seen a single template update disturb several markets at once because nobody checked the other folders.

The country signal is also weaker on its own.

A subfolder relies on hreflang and local signals, such as local addresses, phone numbers, currency and links from local sites, to show Google who it's for.

Subfolder Verdict

Choose subfolders if you're entering new markets with one central team, a limited budget, or a domain that already has strong links.

That covers most businesses I speak to.

Subdomains Make Sense When the Tech Stack Decides

Subdomains sit in between. In practice, you'll usually choose one for technical reasons, not SEO ones.

Google lists their pros as easy set-up, different server locations and easy separation of sites.

That makes them useful when:

• your international store runs on a different platform from the main site
• a regional team needs its own hosting or deployment
• a legal or data rule requires separate infrastructure

Where Subdomains Fall Short

Google's main warning: users might not recognise geotargeting from the URL alone.

Is de.brand.com for German speakers anywhere, or for Germany? The URL doesn't tell your visitors.

The SEO trade-off is authority.

In my experience, search engines often treat a subdomain more like a separate site, so how much strength it shares with your main domain is hard to predict.

You also take on some of the ccTLD overhead without the strong country signal.

Subdomain Verdict

Choose subdomains when a technical constraint rules out subfolders and you can't justify separate country domains.

If neither of those applies, use a subfolder.

What About URL Parameters?

Some sites serve languages with a parameter, such as brand.com/?loc=de.

Google's verdict is blunt: not recommended.

You can't easily segment parameter URLs in reports, and your users can't tell which version they're on. Parameters also tend to break with caching and canonical tags.

If your site works this way today, plan a move to subfolders.

It's one of the few situations where I'd recommend changing structure.

The Factors That Matter More Than Structure

Here's something you'll rarely hear in this debate.

Structure is only one of several signals Google uses to understand who your pages are for. Its documentation also lists:

• hreflang annotations
• local addresses and phone numbers
• local language and currency
• links from local sites
• Business Profile signals

Google also says it works out a page's language from its visible content, not from the URL or the lang attribute.

So a perfect structure with machine-translated copy and home-country prices will still struggle.

What usually wins a market is content built on research in that market's own language. Translated keywords are rarely the ones locals type, which is why I treat each country as its own keyword research project.

Local references matter too.

A business listed in local directories, with a local address, sends signals no URL can. My guide on local citations covers how those work.

Which Should You Choose?

Here's the decision rule I'd give you.

Choose a ccTLD if:

• each country has its own team, budget and marketing plan
• you can afford to build links and content for each domain separately
• a local domain clearly matters to buyers in that market

Choose a subfolder if:

• one central team will run every market
• your main domain already has strong links
• you're entering your first few markets and want results sooner
• you want one platform, one Search Console property and one analytics setup

Choose a subdomain if:

• your international version must run on separate infrastructure or a different platform
• subfolders are technically impossible on your stack
• a ccTLD per market isn't justified

Mix them if: one large market deserves its own domain and everyone else fits under a .com in subfolders.

A Worked Example

Let's make that concrete with a hypothetical business.

Say you run a UK software company on a .co.uk domain with a decent link profile. You want to sell in Ireland and Germany next year, and one marketing team will handle everything.

Here's how I'd think it through:

• Ireland shares your language. You need an en-ie version with euro pricing and Irish contact details, connected to the UK pages with hreflang.
• Germany needs German content researched in German, not translated from your English pages.
• Your team is one group, so three domains would triple the maintenance.

A .co.uk can't hold an Irish or German folder cleanly, because the domain itself says "UK". So the sensible move is a .com with /en-gb/, /en-ie/ and /de/ folders, with the old .co.uk redirected into /en-gb/.

That's a migration, but a one-off one. And afterwards, every link you earn in any market strengthens the same domain.

Now change one detail. Say a German partner will run that market with its own budget and staff. Then a brand.de for Germany, alongside the .com, starts to make sense.

Same business, different answer, because the team changed.

Whatever you pick, connect equivalent pages with hreflang. My free hreflang generator builds the full tag set for any of the three structures.

Changing Structure Later Is a Migration

The worst outcome isn't picking the "wrong" structure. It's switching between them without a plan.

Moving from ccTLDs to subfolders, or the other way round, means redirecting every international URL. Every hreflang annotation changes too.

That's a full site migration, with all the risks that come with one.

So if your current structure works, I usually recommend fixing it in place instead of moving. Broken hreflang and weak localisation are cheaper problems to solve.

If you do need to move, start with a redirect map for each market. Then run the go-live checks in my website migration SEO checklist.

Keep Google's guide to localised versions open during the move. Hreflang URLs must be fully qualified and reciprocal, across every domain you use.

Pick the Structure Your Team Can Actually Run

Every structure can rank. The one that wins is the one your team can maintain without breaking.

So before you decide, answer three questions:

1. Who will run each market: one central team, or local teams?
2. How strong is your current domain, and do you want new markets to share that strength?
3. Does your platform allow subfolders for every market you plan to enter?

If your answers point to one team, a strong domain and a flexible platform, use subfolders.

Crawl, rendering and speed issues in each version sit under technical SEO. And if you'd like help choosing and setting up the structure, hreflang and research per market, here's how my international SEO work runs.