The connection between ccTLDs and SEO
Country code top-level domain names are the most powerful way to rank a domain or rank a page in a certain country.
There are other ways to do it. For example, I could technically get a page on our website, clickminded.com to rank in Germany—but I would have to put in a lot of effort into this.
In the end, the fastest, most powerful way to do rank a website in a specific country is to get the Country Code Top Level Domain of the country in question and use that.
In general, the “apples to apples” rule applies in internationalization too.
For example, if you have two pages that are exactly the same and one is on a “.com” while the other one is a “.de”, the one that’s on a “.de” domain is generally more inclined to rank better in the German version of Google.
Google assumes that all of the content on a Country Code Top Level Domain is designed for that country—so naturally, it will rank the website in that country.
Keep in mind, though: this is unrelated to language. This is just, plain and simple, country-specific.
Documents on a “.de” domain or on a “.fr” domain, or a “.com.au” domain—they are designed for Germany and France and Australia but they’re not actually language specific.
ccTLDs, targeting global traffic, and what to avoid
If you are targeting global traffic, it’s best to stay away from Country Code Top Level Domains – these are country specifications and they can be a huge headache if you want to attract global traffic on your site.
For example, when I first moved to San Francisco in 2011, people were getting the “.it” version of a website—but that’s a domain indicating Italy.
Some of these people were offering IT services, and other just made up cute and clever start-up names ending in “.it”.
They were all very confused about not ranking in the search results for the United States—but that “.it” ccTLD was basically a massive signal to Google that the content on their websites was designed for Italians.
Therefore, the websites were doing great on Google.it, but not on Google.com.
A lot of people still try to get cute with their domain names—but it can hurt them a lot because they used internationalized domain names even if they don’t want to target those particular countries. So, if you want to take the safe path, wherever you are, use whatever is most popular there. It makes things a lot easier.
If you’re in doubt about your domain name, just do the “mom test”
When you pick your domain name, call your mom and mention it to her one time over the phone.
If your mom is able to go to a browser, input that domain name, and get to your page without clarification from you at all, you’re all set—you’ve got a good domain name. If she can’t do that, you might want to work a bit more on it.
The other version of this test is the crowded bar test.
If you said your domain name one time in a crowded bar to someone, would they be able to remember it and visit next day? If yes, your domain name is good to go. If not, work on it and find something that’s even catchier.
Global Country Code Top Level Domains (GccTLD) are an exception from the general rule. In these cases, Google came out and said: “Okay, yes, ‘.de’ is for Germany and yes, ‘.fr’ is for France, but it looks like most people are buying certain domain extensions and they’re not really targeting those places.”
For example, “.io” is for the Indian Ocean, but every single one is a start-up or an app.
In these situations, Google decided that “.io” will be global. The same goes for “.co” as well (which was originally the Country Code for Colombia).
And there’s a list of other similar generic top-level domains examples as well—you can find them here.
- .ad – Andorra
- .bz – Belize
- .cc – Cocos Islands
- .cd – Democratic Republic of Congo
- .dj – Djibouti
- .fm – Federal States of Micronesia
- .me – Montenegro
- .sc – Seychelles (although it was used for businesses in Scotland and South Carolina!)
- .su – Soviet Union (there’s a different one for Russia, but “.su” was used with its intended purpose only for 15 months before the fall of the Soviet Union)
- .tv – Tuvalu
All of these ccTLDs have now been recognized to be just top-level domain names and they do not carry internationalization power any longer.
There are, however, many others out there that might still be confusing – such as “.is”, which is actually the ccTLD for Iceland, not for Israel as some may believe. Likewise, “.my” is not a cute ending for your domain name, but the ccTLD for Malaysia.
The 3 Questions You Need to Ask Yourself about ccTLDs
Before you invest in Country Code Top Level Domains (or an internationalization strategy), there are a bunch of different questions you should ask yourself:
Do you operate in a certain country and you have no plans on expanding beyond that?
For instance, if you’re a French coffee shop chain, you may have one or two retail locations and you might want to build a couple more—but you will never expand beyond the borders of France.
In this case, getting the “.fr” domain name is totally fine and there are no issues here at all.
Do you operate in multiple countries?
Maybe you’re in the US, in Canada, in the UK, or maybe you’re in France and you also want to expand to Germany. In this case, I would still pick one domain, but use country code sub-folders.
This is what we did at PayPal. Everything happened on the “.com” domain, but the localized versions of the web application were on country code sub-paths.
For example, all of our Mexican content was on “/mx/”, all of our Spanish content was on “/es/”, all of our French content was on “/fr/”, and so on.
Generally, every time you’re adding an incremental domain, things can get tough.
From the technical side to the crawl budgets, Google Search Console, Analytics, and cross-domain tracking, everything can be really overwhelming.
So, if you’re just getting started expanding, picking a global domain and using a country-specific code subpath is a better way to manage internationalization.
Are you everywhere, with multiple offices in different countries? Does your content come in multiple languages? Are you a massive operation?
If that’s the case, you can go ahead and buy Country Code Top Level Domains. In general, I advise against this—think of the fact that even PayPal wasn’t big enough to actually need this.
At Airbnb, there were about 26-27 different ccTLDs—and that involved intricate engineering on the back-end, specifically for making localized copies of each domain.
It was a fantastic ranking signal, we even had all of our content translated by local translators, and it was all great for the search engines.
However, it was expensive and difficult to maintain—so keep this in mind if you’re considering the option.
To summarize, if you will not expand your business into other countries, it’s best to stick with the Country Code Top Level Domain of the country you’re in. Once you start expanding a little bit, build up country-specific sub-folders and you will be fine.
In general, only buy multiple Country Code Top Level Domains if you’re massive operation and you’re willing to invest the time and the financial resources into building and maintaining such an infrastructure.
That’s it – that’s all there really is to Country Code Top Level Domains (or ccTLDs). It’s not a difficult concept to grasp, but knowing the basics around it can really save you a lot of trouble later on!