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.
الصيغة
international-url-structure-decision.md
متى تلجأ إليها
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.
ملف المهارة
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.
## ما تحتاجه أولًا
- 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
## الطريقة
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.
## ما الذي تنتجه
A one-page decision naming the chosen pattern per market, the cost of each option rejected, and the trigger that would reopen it.
## أين تخطئ عادةً
- 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
---
من مكتبة مهارات QuQi - https://www.quqi.io/ar/skills/international-url-structure-decision
تنزيل مجاني · بلا حساب وبلا بريد
ما تحتاجه أولًا
-
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
الطريقة
-
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.
ما الذي تنتجه
A one-page decision naming the chosen pattern per market, the cost of each option rejected, and the trigger that would reopen it.
أين تخطئ عادةً
-
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
استخدم هذه المهارة في الذكاء الاصطناعي الخاص بك
الملف الذي تنزّله markdown بسيط، يحمل الاسم والمُشغّل في ترويسته. وحين يكون المساعد قادراً على تحميل المهارات وحده، فهذه الترويسة هي ما يقرؤه ليقرر أن هذه المهارة تنطبق.
كلود كود
احفظه في ~/.claude/skills/international-url-structure-decision/SKILL.md فيحمّله كلود من تلقاء نفسه حين يطابق عملك سطر المُشغّل. وضعه في .claude/skills داخل مشروع إن أردت أن يكون لدى الفريق كله.
كلود
ارفع الملف في قسم المهارات ضمن إعداداتك. وبعدها ينطبق من تلقاء نفسه في أي محادثة يناسبها المُشغّل، دون أن تتذكر وجوده.
شات جي بي تي
لا يوجد صيغة مهارات لتثبيته فيها، فالصق محتوى الملف في تعليمات مشروع أو في GPT مخصص بدلاً من ذلك. عندها ينطبق على كل محادثات ذلك المشروع لا على المحادثة التي لصقته فيها وحدها.
أي مساعد آخر
الصق الـ markdown في المحادثة قبل سؤالك. يعمل مع أي مساعد، لكن عليك لصقه من جديد في كل مرة.
المزيد في SEO الدولي