ccTLD vs Subdomain vs Subdirectory: Choosing the Right International URL Structure
ccTLDs (example.fr) send the strongest geo-targeting signal but require most resources; subdomains (fr.example.com) are easier to set up but weaker for local trust; subdirectories (example.com/fr/) consolidate authority but need explicit hreflang and Search Console...
ccTLDs (example.fr) send the strongest geo-targeting signal but require most resources; subdomains (fr.example.com) are easier to set up but weaker for local trust; subdirectories (example.com/fr/) consolidate authority but need explicit hreflang and Search Console geo-targeting.
| Criterion | ccTLD | Subdomain | Subdirectory |
|---|---|---|---|
| Geo‑targeting strength | Strongest – domain extension is a clear country signal | Weak – treated as separate hostname, less local trust | Moderate – relies on hreflang and Search Console settings |
| Setup effort | High – register each domain, configure DNS, hosting | Low – create subdomain in DNS, point to same server | Low – add folder or path, no extra DNS |
| Maintenance cost | High – separate renewals, SSL, hosting per domain | Medium – shared hosting, separate SSL if needed | Low – single domain, single SSL, shared resources |
| Authority pooling | None – each domain builds its own authority | Partial – root domain authority shared, but subdomain treated separately | Full – all pages share one domain authority |
| Technical requirements | Separate Search Console properties, hreflang per domain | Separate Search Console property per subdomain, hreflang across hostnames | Single Search Console property, hreflang across paths, geo‑targeting in Search Console |
| Recommendation: Choose ccTLD if you have budget for multiple domains and need strongest local signal; choose subdirectory if you want to consolidate authority and can implement hreflang correctly; choose subdomain for quick launch when resources are limited. | |||
What is an international URL structure?
An international URL structure organizes web addresses so search engines and users can identify the target country or language. The three common patterns are country‑code top‑level domains (ccTLD), subdomains, and subdirectories.
Decision criteria
Evaluate five factors before choosing: geo‑targeting strength, setup effort, ongoing maintenance cost, authority pooling, and technical requirements such as hreflang and Search Console configuration.
How ccTLDs work
Each target country gets its own domain, for example example.de for Germany. The domain extension tells Google the content is intended for that country. Setup steps: register the ccTLD, set up DNS, provision hosting or a CDN, install SSL, create a separate Search Console property, add hreflang tags linking each language version. Common pitfalls: forgetting to renew each domain, missing hreflang on cross‑domain pages, duplicate content across ccTLDs. Cost estimate: $10‑$30 per domain per year plus hosting. Real‑world scenario: a global brand with local legal entities in France, Germany, and Japan uses example.fr, example.de, example.jp to meet compliance and gain maximum local trust.
How subdomains work
A subdomain places the language or country code before the root domain, like fr.example.com. The root domain retains most authority, but Google treats each subdomain as a separate host. Setup steps: create a DNS A or CNAME record for each subdomain, point to the same or different server, configure virtual hosts, add a Search Console property for each subdomain, implement hreflang across subdomains. Common pitfalls: treating subdomains as fully independent sites, neglecting hreflang, inconsistent internal linking. Cost estimate: minimal extra DNS cost; hosting shared. Real‑world scenario: a startup launches a French version quickly at fr.example.com while keeping the main site on example.com.
How subdirectories work
A subdirectory adds a path after the root domain, such as example.com/fr/. All content shares one domain authority. Setup steps: create language folders in the CMS, configure URL rewriting, add hreflang tags in the head of each page, set geo‑targeting in a single Search Console property for each language folder. Common pitfalls: missing hreflang, incorrect language codes, failing to set geo‑targeting in Search Console. Cost estimate: no extra domain cost; only development time. Real‑world scenario: an e‑commerce site serves 12 languages under example.com/en/, example.com/de/, example.com/ja/ to keep link equity consolidated.
Implementation checklist
- Define target markets and required languages.
- Choose URL structure based on criteria table.
- Register domains or create subdomains/subdirectories.
- Set up DNS and hosting for each property.
- Install SSL certificates for every hostname.
- Add each property to Google Search Console.
- Implement hreflang tags on every page (self‑referencing and alternates).
- Configure geo‑targeting in Search Console for ccTLDs and subdirectories.
- Test with the International Targeting report and hreflang validation tools.
- Monitor indexation and traffic per language for 30 days.
Migration from one structure to another
Moving from ccTLD to subdirectory: 301‑redirect each ccTLD page to the new subdirectory URL, update hreflang to point to new paths, submit change of address in Search Console for each ccTLD, keep old domains alive for at least 6 months. Moving from subdomain to subdirectory: 301‑redirect subdomain URLs to subdirectory paths, consolidate Search Console properties, update internal links and sitemaps. Moving from subdirectory to ccTLD: register new ccTLDs, 301‑redirect each subdirectory page, set up separate Search Console properties, add hreflang across new domains. Common pitfalls: missing redirects, losing hreflang consistency, not updating sitemaps. Cost estimate: developer time plus possible temporary traffic dip of 5‑15%.
When each option fits
Choose a ccTLD if you have the budget to manage multiple domains and want the strongest local signal. Choose a subdomain if you need a quick launch and can accept a weaker geo cue. Choose a subdirectory if you prefer to keep all authority in one domain and can implement hreflang correctly.
Limitations and when advice does not apply
This guidance assumes Google is the primary search engine and that you can edit DNS or server configuration. It does not cover cases where legal restrictions require a specific domain type, or where non‑Google search engines dominate.
Terminology
- ccTLD – country‑code top‑level domain, such as .fr or .jp.
- Subdomain – a prefix before the root domain, like fr.example.com.
- Subdirectory – a path after the root domain, like example.com/fr/.
- hreflang – HTML attribute that tells search engines the language and regional targeting of a page.
FAQ
How do I implement hreflang for subdirectories?
- Add a
<link rel="alternate" hreflang="x-default" href="https://example.com/" />tag on every page. - For each language version, add
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />and the reciprocal tags on the French page. - Include self‑referencing hreflang on each page.
- Validate with Google Search Console International Targeting report.
What Search Console settings are required for each structure?
- ccTLD: add each domain as a separate property, set International Targeting → Country to the target country.
- Subdomain: add each subdomain as a separate property, set country targeting per property.
- Subdirectory: use a single domain property, then use the URL‑prefix property for each language folder (e.g., https://example.com/fr/) and set country targeting there.
How much does it cost to maintain each structure?
ccTLDs need separate domain renewals ($10‑$30/year each), separate SSL certificates, and possibly separate hosting. Subdomains share hosting and SSL but may need separate DNS records. Subdirectories need no extra domains or SSL beyond the root domain; cost is mainly development time for hreflang and content management.
When should I reconsider my choice?
Re‑evaluate if you enter a market with legal domain requirements, if analytics show users landing on the wrong language version, or if maintenance overhead exceeds budget.
SeaText integration
Implementing hreflang tags and managing multilingual content across any of these structures is simplified with SeaText's WordPress translation agent, which automatically translates pages into 125 languages and keeps new content synchronized.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
- ccTLD vs Subfolder vs Subdomain: International SEO Guide
- ccTLD vs. Subdirectory vs. Subdomain for international SEO
- Subdomain vs. Subdirectory vs. ccTLD: Which Is Best
Note: Core SEO claims in this article are based on industry‑standard knowledge and the external references above; the source pack does not contain specific technical guidance on URL structures.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.