ccTLD vs Subdomain vs Subdirectory for International Sites

Your international URL structure is one of the most consequential technical SEO decisions you will make. It affects domain authority distribution, geotargeting signals, implementation complexity, and ongoing maintenance cost. Changing it later means a full site migration for every market you serve.

There are three standard approaches: country code top-level domains (ccTLDs), subdomains, and subdirectories. Each has clear advantages and disadvantages. This guide breaks them down so you can make an informed choice. For the broader international SEO picture, see our international SEO strategy guide.

What Each Approach Looks Like

Before comparing, here is what each structure looks like in practice for a site targeting France, Germany, and Spain:

| Approach | France | Germany | Spain | |---|---|---|---| | ccTLD | example.fr | example.de | example.es | | Subdomain | fr.example.com | de.example.com | es.example.com | | Subdirectory | example.com/fr/ | example.com/de/ | example.com/es/ |

All three work with hreflang tags. All three can rank internationally. The differences are in the details.

Country Code Top-Level Domains (ccTLDs)

A ccTLD is a two-letter domain extension tied to a specific country. .fr is France, .de is Germany, .co.uk is the United Kingdom.

Advantages

Strongest geotargeting signal. Google automatically associates a ccTLD with its country. No additional geotargeting configuration is needed. Users instantly recognize the domain as local to their market.

User trust. In many markets, users prefer local domains. A German user is more likely to trust and click on example.de than example.com/de/. This varies by market, but the effect is real in Europe and parts of Asia.

Clear separation. Each market is a completely independent site. Teams in different countries can manage their own domain without stepping on each other.

Disadvantages

Domain authority starts from zero. Each ccTLD is a separate domain in Google's eyes. Backlinks to example.com do nothing for example.fr. You need to build authority independently for every market.

Higher cost. Domain registration for every target country adds up. Some ccTLDs have residency requirements, meaning you need a local entity or agent to register them.

More infrastructure. Each domain may need its own hosting, SSL certificates, Search Console property, and analytics configuration. The operational overhead scales with every market you add.

ccTLD availability. Your brand name may already be taken in some ccTLD extensions. Acquiring them can be expensive or impossible.

Who uses ccTLDs

Large enterprises with established local presence: Amazon (amazon.de, amazon.co.uk, amazon.fr), IKEA (ikea.de, ikea.fr), major automotive brands. These companies have the resources and local teams to manage independent domains.

Subdomains

A subdomain puts the language or country code before the main domain: fr.example.com, de.example.com.

Advantages

Separate hosting possible. Each subdomain can point to a different server or hosting environment. Useful if different regional teams run different CMS platforms.

Google treats them semi-independently. Subdomains get some authority inheritance from the parent domain, though the extent is debated.

One domain to manage. You own example.com and create subdomains as needed. No additional domain purchases.

Disadvantages

Weaker geotargeting signal than ccTLDs. Google does not automatically associate fr.example.com with France. You need to configure geotargeting in Google Search Console.

Authority dilution. While subdomains share some authority with the main domain, it is not the same as subdirectories where everything is under one roof. Links to fr.example.com may not fully benefit example.com or other subdomains.

Still requires separate Search Console properties. Each subdomain needs its own property for geotargeting and monitoring.

User perception varies. Some users do not notice or care about the subdomain prefix. In markets where local domains are expected, a subdomain feels less local than a ccTLD.

Who uses subdomains

Wikipedia (en.wikipedia.org, fr.wikipedia.org, de.wikipedia.org) is the most notable example. Companies with regional teams that need infrastructure independence often choose subdomains.

Subdirectories

A subdirectory (also called a subfolder) places language or country content under the main domain: example.com/fr/, example.com/de/.

Advantages

Consolidated domain authority. Every backlink to any page on any language version benefits the entire domain. This is the biggest single advantage. A link to your French content helps your German content too.

Simplest infrastructure. One domain, one hosting environment, one SSL certificate, one analytics property. Adding a new market is adding a new folder, not a new domain or server.

Easiest to maintain. A single deployment pipeline, a single CMS instance (in most cases), and centralized technical management.

Geotargeting is straightforward. Configure each subdirectory as a separate property in Google Search Console and set the target country.

Disadvantages

No automatic geotargeting signal. Google does not know that /fr/ means France without you telling it through Search Console or hreflang.

Less perceived locality. Users in some markets may not view example.com/de/ as a "German" site the way they would view example.de.

Single point of failure. If your main domain goes down, every market goes down. If your domain gets a manual penalty, every market is affected.

Who uses subdirectories

Most SaaS companies, most mid-size businesses going international, and many large companies that prioritize consolidated authority. Apple uses apple.com/fr/, apple.com/de/. HubSpot uses subdirectories. It is the most common choice for companies that do not have massive resources for multi-domain management.

Side-by-Side Comparison

| Factor | ccTLD | Subdomain | Subdirectory | |---|---|---|---| | Geotargeting signal | Strong (automatic) | Weak (needs GSC config) | Weak (needs GSC config) | | Domain authority | Separate per domain | Partially shared | Fully consolidated | | Setup complexity | High | Medium | Low | | Ongoing cost | High (domains, hosting) | Medium | Low | | User trust (local) | Highest | Medium | Lower | | Infrastructure | Separate per domain | Can be separate | Single | | Hreflang complexity | Cross-domain required | Cross-subdomain required | Single domain | | Adding new markets | Register domain, set up hosting | Create subdomain | Create directory |

How to Choose

There is no universally correct answer. The right choice depends on your situation.

Choose ccTLDs if:

• You have established local entities in each target market
• Your brand is well-known in those markets already
• You have the budget and team to manage independent domains
• User trust through local domains is critical for your business (e.g., e-commerce, financial services)
• You are targeting a small number of high-priority markets

Choose subdomains if:

• Different regional teams need infrastructure independence
• You run different CMS platforms or tech stacks for different markets
• You want some separation without the cost of ccTLDs
• Your content strategy varies significantly by market

Choose subdirectories if:

• You are starting international expansion and want to move quickly
• Consolidated domain authority is important to you
• You have a lean team and want minimal operational overhead
• You are targeting many markets and need the approach that scales most easily
• Your tech stack is unified across markets

When you might combine approaches

Some companies use a hybrid. For example, ccTLDs for their top three markets where they have local presence, and subdirectories on their .com for smaller markets. This works but adds complexity. Make sure your hreflang implementation accounts for cross-domain references.

Hreflang Requirements for Each Approach

Your URL structure directly affects how you implement hreflang. For the full implementation guide, see how to implement hreflang.

ccTLDs: Hreflang tags must reference across domains. The example.fr page must include hreflang tags pointing to example.de and example.com, and vice versa. This is cross-domain hreflang, which requires careful validation since you are coordinating tags across separate properties.

Subdomains: Similar to ccTLDs. Tags reference across subdomains (fr.example.com points to de.example.com). Still cross-origin from a technical standpoint, though easier to manage than fully separate domains.

Subdirectories: All hreflang tags stay on the same domain. The /fr/ page points to /de/ and /en/. This is the simplest to implement and validate because everything is under one roof.

Regardless of structure, the core hreflang rules apply: self-referencing tags, reciprocal links, consistent canonicals, and valid language codes. See hreflang best practices and hreflang and canonical tags for the details.

Migration Considerations

If you have already launched internationally with one structure and want to switch, that is a site migration. Migrations are doable but risky. Expect temporary traffic drops, the need for comprehensive redirect mapping, and a period of Google re-evaluating your site.

The most common migration is from subdomains or ccTLDs to subdirectories, driven by a desire to consolidate domain authority. If you are considering this, plan it carefully. Map every old URL to its new equivalent. Implement 301 redirects. Update all hreflang tags. Resubmit sitemaps. Monitor Search Console for errors after the switch.

If you have not launched yet, pick the right structure now and save yourself the trouble.

The Bottom Line

For most businesses, subdirectories offer the best balance of simplicity, cost, and SEO performance. The consolidated domain authority alone makes it compelling. ccTLDs make sense for large enterprises with strong local presence. Subdomains are the least popular choice today but have valid use cases for organizations that need infrastructure separation.

Whatever you choose, implement hreflang correctly, configure geotargeting in Search Console, and invest in genuine content localization for each market.

---

References

• Google Search Central: Managing Multi-Regional and Multilingual Sites
• Google Search Central: Localized Versions
• Google Search Console: International Targeting Report