Choosing ccTLD, Subdirectory Or Subdomain
Teams pick this on instinct or by copying a competitor, then discover three years later that eight country domains each have to earn authority on their own while there is budget for one link programme. The obvious argument, that country domains rank better locally, is weaker than it sounds next to the signals you split, but the opposite claim is also overstated: in some markets a national domain measurably affects trust and click behaviour, and legal or procurement rules may decide it for you outright. This applies before the first localised page is built, and again whenever consolidation is proposed.
CATEGORY
International SEO
FORMAT
international-url-structure-decision.md
WHEN TO REACH FOR THIS
Use when a new market launch is being planned, or when you inherit a mix of country domains and folders and someone needs a defensible answer on where localised pages should live.
The skill file
international-url-structure-decision.md
---
name: international-url-structure-decision
description: Use when a new market launch is being planned, or when you inherit a mix of country domains and folders and someone needs a defensible answer on where localised pages should live.
---
# Choosing ccTLD, Subdirectory Or Subdomain
Teams pick this on instinct or by copying a competitor, then discover three years later that eight country domains each have to earn authority on their own while there is budget for one link programme. The obvious argument, that country domains rank better locally, is weaker than it sounds next to the signals you split, but the opposite claim is also overstated: in some markets a national domain measurably affects trust and click behaviour, and legal or procurement rules may decide it for you outright. This applies before the first localised page is built, and again whenever consolidation is proposed.
## What you need first
- The markets you are committing to for the next three years, with the language and the country of each stated separately
- Current domain inventory including any country domains already registered, with the link profile of each
- Whether a local entity, local payment and local support exist per market, or whether everything ships from one place
- The platform and deploy constraints: whether one codebase can serve every locale, and who is able to release to each domain
## Method
1. Write the market list first and split language from country. One Spanish site serving all of Latin America is a different decision from eleven country sites, and teams routinely conflate the two before comparing any options.
2. Score each market on whether a national domain is a real purchase signal there. In parts of Europe and East Asia it visibly affects trust and click-through; in most other markets it does not, and assuming it does everywhere is what produces portfolios nobody can maintain.
3. Count the link acquisition programmes you can actually staff, because each separate domain earns authority on its own. A portfolio of country domains is only defensible if every one of them gets its own effort; otherwise put the markets in subdirectories on one domain.
4. Check legal, registry and procurement constraints before the search argument, because they override it. Several country registries require a local registered entity or address, and some regulated and public sector buyers will not transact on anything else.
5. Treat subdomains as the option that inherits least. They behave closer to separate sites than subdirectories do, and they carry most of the operational overhead of a country domain without the local signal, so pick them only when the platform genuinely cannot serve folders.
6. Price the migration for live markets separately from the greenfield decision. Folding existing country domains into subdirectories is a full migration with a recovery period, so it has to be argued over three years rather than the next quarter.
7. Record the decision with the condition that would reverse it, for example a market passing a revenue threshold that justifies its own domain and its own link budget, so the next reorganisation does not reopen the argument from zero.
## What this produces
A one-page decision naming the chosen pattern per market, the cost of each option rejected, and the trigger that would reopen it.
## Where this goes wrong
- Registering country domains early to protect the brand, then launching them as thin translated copies, which creates weak sites you must later either resource properly or migrate away
- Assuming a subdirectory inherits full authority page by page, when a new locale folder starts from the standing of the domain and each page still has to earn relevance in its own market
- Deciding on ranking theory while ignoring who can deploy to each domain, which is what actually determines whether the country sites stay in sync
- Leaving a legacy country domain live and unmaintained after moving the market into a subdirectory, so the two compete for the same queries
---
From the QuQi skill library - https://www.quqi.io/skills/international-url-structure-decision
Free to download · no account, no email
What you need first
-
The markets you are committing to for the next three years, with the language and the country of each stated separately
-
Current domain inventory including any country domains already registered, with the link profile of each
-
Whether a local entity, local payment and local support exist per market, or whether everything ships from one place
-
The platform and deploy constraints: whether one codebase can serve every locale, and who is able to release to each domain
Method
-
01
Write the market list first and split language from country. One Spanish site serving all of Latin America is a different decision from eleven country sites, and teams routinely conflate the two before comparing any options.
-
02
Score each market on whether a national domain is a real purchase signal there. In parts of Europe and East Asia it visibly affects trust and click-through; in most other markets it does not, and assuming it does everywhere is what produces portfolios nobody can maintain.
-
03
Count the link acquisition programmes you can actually staff, because each separate domain earns authority on its own. A portfolio of country domains is only defensible if every one of them gets its own effort; otherwise put the markets in subdirectories on one domain.
-
04
Check legal, registry and procurement constraints before the search argument, because they override it. Several country registries require a local registered entity or address, and some regulated and public sector buyers will not transact on anything else.
-
05
Treat subdomains as the option that inherits least. They behave closer to separate sites than subdirectories do, and they carry most of the operational overhead of a country domain without the local signal, so pick them only when the platform genuinely cannot serve folders.
-
06
Price the migration for live markets separately from the greenfield decision. Folding existing country domains into subdirectories is a full migration with a recovery period, so it has to be argued over three years rather than the next quarter.
-
07
Record the decision with the condition that would reverse it, for example a market passing a revenue threshold that justifies its own domain and its own link budget, so the next reorganisation does not reopen the argument from zero.
What this produces
A one-page decision naming the chosen pattern per market, the cost of each option rejected, and the trigger that would reopen it.
Where this goes wrong
-
Registering country domains early to protect the brand, then launching them as thin translated copies, which creates weak sites you must later either resource properly or migrate away
-
Assuming a subdirectory inherits full authority page by page, when a new locale folder starts from the standing of the domain and each page still has to earn relevance in its own market
-
Deciding on ranking theory while ignoring who can deploy to each domain, which is what actually determines whether the country sites stay in sync
-
Leaving a legacy country domain live and unmaintained after moving the market into a subdirectory, so the two compete for the same queries
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Claude Code
Save it as ~/.claude/skills/international-url-structure-decision/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude
Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT
There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else
Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.
Questions about this skill
When is this the right method rather than copying whichever competitor looks successful?
Use it before the first localised page exists, and again whenever consolidation is proposed. Copying a competitor imports their legal entity structure, their link budget and their staffing without anyone checking you have those. The argument is genuinely contested: a national domain measurably affects trust and click behaviour in some markets, and does nothing in most.
What do I need in hand before starting?
The markets committed to for three years with language and country stated separately, the domain inventory with each link profile, whether a local entity, payment and support exist per market, and who can deploy to each domain. Skip the entity and deploy questions and you produce a ruling that registry rules or your release process overturns later.
What do I end up with, and which part of it gets used?
A one-page ruling naming the chosen pattern per market, the cost of each option rejected, and the trigger that would reopen it. The trigger is the part that survives contact with the next reorganisation. Without a stated condition, such as a market passing a revenue threshold that justifies its own domain and link budget, the argument restarts from zero.
What ruins this most often?
Registering country domains defensively and launching them as thin translated copies. You then own several weak sites, each needing its own link programme, and the only way out is a full migration with a recovery period. The related trap is leaving a legacy country domain live after moving that market into a subdirectory, so both compete for the same queries.
More in International SEO