# ccTLD

Category: [Technical SEO](https://seo-geo-glossary.com/en/glossary/category/technical-seo/) › [URLs & domains](https://seo-geo-glossary.com/en/glossary/category/technical-seo/urls-domains/)

A **ccTLD** (country code top-level domain) is a top-level domain with two letters that is assigned to a country or territory, such as `.de` for Germany or `.fr` for France. Most ccTLDs follow the ISO 3166-1 alpha-2 country codes. According to reports, two well-known exceptions are `.uk`, which differs from the ISO code GB, and `.eu`, which stands for the European Union.

## ccTLDs and country targeting

Google describes ccTLDs as tied to a specific country and as a strong signal, to users and search engines alike, that a site is meant for that country. For sites on generic TLDs such as `.com`, Google asks for other signals. The International Targeting report in Search Console, which once allowed setting a target country, has been deprecated.

Some country-code endings are used worldwide. Google lists endings such as `.tv`, `.me`, `.co`, `.io` and `.ai` among those it treats as generic, because users and site owners often see them as less country-specific. A site on `.io` therefore does not get a country signal from its ending.

## Trade-offs for international sites

A separate ccTLD per market gives a clear country signal. It also means a separate domain per market to register, host and maintain, and each domain starts with its own links and history. Google lists subdomains and subdirectories on a generic domain as alternatives and advises against URL parameters for country targeting.

Whichever structure is used, language and country versions of a page can be linked with hreflang annotations. Google does not vary the crawler source to look for regional variations of a page, so explicit annotations are needed.

## Example

```
https://www.example.de/   (Germany)
https://www.example.fr/   (France)
https://www.example.at/   (Austria)
```

## Common mistakes

- **Treating every country-code ending as a country signal.** Google treats endings such as `.tv`, `.me`, `.co` and `.io` as generic, because users and site owners often see them as less country-specific.
- **Redirecting automatically by IP address.** Google calls IP location analysis difficult and generally not reliable. Automatic redirects can keep users and search engines from seeing all versions.
- **Translating only boilerplate.** If the bulk content stays in one language, the same content can appear several times in results with different boilerplate languages, according to Google.
- **Declaring the target place with a meta tag.** Google ignores locational meta tags.

## URL structures for country versions compared

| Structure | Example | Target country recognisable? | Pros according to Google | Cons according to Google |
|---|---|---|---|---|
| Country-code domain (ccTLD) | example.de | yes, a strong signal to users and search engines | clear geotargeting, server location irrelevant, easy separation of sites | expensive and sometimes limited availability, more infrastructure, strict ccTLD requirements in some cases, one country only |
| Subdomain on a gTLD | de.example.com | not always clear from the URL alone (is "de" the language or the country?) | easy to set up, allows different server locations, easy separation of sites | users might not recognise the targeting from the URL alone |
| Subdirectory on a gTLD | example.com/de/ | not always clear from the URL alone | easy to set up, low maintenance (same host) | users might not recognise the targeting from the URL alone, single server location, harder to separate sites |
| URL parameters | example.com?loc=de | not always clear from the URL alone | – (not recommended by Google) | URL-based segmentation difficult, users might not recognise the targeting from the URL alone |

Sources: [Google Search Central: Managing multi-regional and multilingual sites (last updated 2025-12-10)](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites); [Search Console Help: International Targeting report (deprecated)](https://support.google.com/webmasters/answer/62399). Last checked: October 8, 2026

*Diagram: Anatomy of a URL.* A URL broken into its parts. RFC 3986 defines scheme, host, path, query and fragment. Only the browser evaluates the fragment after #, it is not sent to the server.

## Related terms

- [Top-level domain (TLD)](https://seo-geo-glossary.com/en/glossary/top-level-domain/index.md)
- [hreflang](https://seo-geo-glossary.com/en/glossary/hreflang/index.md)
- [Geo-targeting](https://seo-geo-glossary.com/en/glossary/geo-targeting/index.md)
- [Subdomain](https://seo-geo-glossary.com/en/glossary/subdomain/index.md)
- [Domain](https://seo-geo-glossary.com/en/glossary/domain/index.md)

## More on the searchVIU blog

- [Migrating from ccTLDs to a gTLD – The WHY, the HOW, and the WTF](https://www.searchviu.com/en/cctlds-to-gtld/)

## Sources

- [Managing multi-regional and multilingual sites – Google Search Central](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
- [The International Targeting report is deprecated – Search Console Help](https://support.google.com/webmasters/answer/1347922)
- [Country code top-level domain – Wikipedia](https://en.wikipedia.org/wiki/Country_code_top-level_domain)
- [RFC 1591: Domain Name System Structure and Delegation – RFC Editor](https://www.rfc-editor.org/rfc/rfc1591)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/cctld/