ccTLD SEO

I would start with one ccTLD as a test, not a portfolio. Pick your highest-priority market and launch a single country domain. For example, I once targeted France with a .fr domain. I spent the first three months building local links from French business directories, a few guest posts on .fr blogs, and getting listed on PagesJaunes. After six months, the site ranked on page one for its core terms, but it took longer than a subdirectory on my established .com would have. The traffic was 30% higher than the .com/fr/ equivalent, but the effort was triple. My rule now: if you cannot articulate why a user needs to see .fr in the URL, use a subdirectory. ccTLDs are for trust and regulation, not for ranking alone.

Set up hreflang from day one. Even with a ccTLD, you need hreflang tags to tell Google which language or region each page targets. I learned that the hard way when my .fr site started appearing in Swiss search results because Google saw French content but no hreflang. Build local links and content specifically for that market. Do not try to globalise your .com link profile. A .de site needs links from .de domains, from German newspapers, from local chambers of commerce. That takes time. Budget for it.

I would also argue that for many businesses, a single gTLD with subdirectories is easier to scale. If you are not selling something that requires local payment methods or legal pages in a specific jurisdiction, you do not need a ccTLD. My decision rule is: if the market has a strong preference for local domains (like Germany, Japan, China), use ccTLD. Otherwise, go with subdirectories and [hreflang](/multilingual-seo/). That saves you the hassle of managing multiple [international SEO](/international-seo/) campaigns and separate Search Console dashboards.

Here is a worked example with numbers. I tracked the .fr site: initial Domain Authority 0, after six months DA 22, traffic 1,200 organic visits per month. The .com/fr/ site reached the same traffic in three months with an inherited DA of 45. So the ccTLD cost me three months of growth. However, the .fr site had a 2% higher conversion rate because users trusted the country domain. For an ecommerce store with high average order value, that lag might be worth it. But for a content site, it was a net loss.

Authority does not transfer. If your .com has strong links, your new .de starts at zero. You will need to build authority from scratch. Some people argue that cross-domain rel=canonical or hreflang can share signals, but Google's John Mueller has said that does not consolidate authority across ccTLDs. So each ccTLD is its own site. That means link-building and content operations are duplicated across markets. I have a client who runs .fr, .de, .it, and .es. They spend £4,000 per month on [link building](/international-link-building/) per domain. That is £16,000 per month total. With a subdirectory structure, they would spend £4,000 per month for all markets combined. ccTLDs multiply cost significantly.

ccTLDs do not fix language issues. A .mx domain does not tell Google you are targeting Spanish speakers in Mexico—you still need hreflang. I once saw a .be website (Belgium) with Dutch and French content but no hreflang. Google showed the Dutch page to French-speaking users in Belgium. Hreflang fixed it, but it required [localization SEO](/localization-seo/) expertise that the client did not budget for.

Maintenance multiplies. Each ccTLD needs its own Search Console property, its own analytics view, its own content calendar. If you have five ccTLDs, you have five separate sites to manage. That is more server configurations, more SSL certificates, more redirect rules. Edge case: some ccTLDs have registration restrictions. For example, .it requires an Italian VAT number, .us requires a US presence. Check before you commit. I nearly registered .in for India but learned it requires an Indian entity for commercial use. Always read the registry requirements for each extension.

Counter-argument: some say ccTLDs improve click-through rates because users trust the country domain more than a generic .com. That is a UX benefit, not a ranking benefit, and it comes at the cost of link equity and scalability. If click-through matters more than organic reach (for example, a brand that relies on direct traffic), then ccTLDs might still win. But for most SEO-driven projects, the trade-off is not worth it.

I assumed ccTLDs were always better for local rankings. They are not—Google has said subdirectories can work just as well with proper hreflang. I used to think seeing a .de domain gave me an automatic ranking boost in Germany. It does not. The country signal helps, but not as much as strong content and links. I launched multiple ccTLDs at once without enough content or links. In 2018, I registered .fr, .de, .it, .es all at the same time for a client. Each site had ten thin pages. None of them ranked for six months. I wasted £5,000 on registration and hosting before we consolidated to a [single gTLD with subdirectories](/global-seo-strategy/). That worked within two months.

I thought a ccTLD alone handled language targeting. It does not. I had a .ch site with German and French content. Google indexed the French version as the primary for German-speaking users because I did not add hreflang. I lost traffic until I fixed it. Another mistake: I ignored the fact that ccTLDs are treated as separate entities by Google. I expected link equity from my .com to pass to my .de through cross-linking. It did not. I needed proper [SEO translations](/seo-translations/) and local content, not just a redirect of link signals.

I also underestimated the cost of maintaining separate link-building strategies. Now I always calculate the total cost of running multiple ccTLDs before recommending that path. If your total budget for international SEO is under £10,000 per year, do not use ccTLDs. Use subdirectories and invest that money in content and hreflang implementation instead.

What I would do differently today: pick one market, prove the model with a ccTLD only if absolutely necessary, and scale only after nine months of consistent performance data. And never launch more than two ccTLDs in the same quarter.