SEO & Search
International SEO for Publishers: Why ccTLDs Beat One-Size Domains
A consultant with dozens of publisher SEO projects says generic TLDs only work with strong brand equity, hreflang fails for news, and full localisation via ccTLDs is the only uncompromised strategy.

Publishers chasing international audiences often copy the wrong playbook, according to a consultant who has worked on dozens of international SEO projects for news brands. The popular model — a single generic top-level domain like theguardian.com — only works in narrow circumstances, he argues, and the alternative most publishers choose instead, hreflang tagging, breaks down entirely in a news context.
The analysis, published by Search Engine Journal, sets out what news publishers actually need to do to succeed in search across multiple countries.
Why the generic TLD model rarely transfers
Publishers look at theguardian.com and assume a generic .com domain — or any TLD Google treats as generic — can target almost any country. The author's verdict: this usually works only in specific contexts. The critical ingredient is brand power. The publisher needs strong brand equity, with large volumes of brand searches and direct traffic in every territory the site targets.
There is a second constraint. A single generic domain targeting multiple countries generally works only if the publisher publishes in a single language. The Guardian publishes only in English. It runs territory-specific subfolder homepages, but individual articles are not separated by country and carry a singular canonical URL. Once a publisher wants to publish in multiple languages, the entire premise changes, and one generic TLD is rarely the best strategy.
Multiple languages, one country: viable
One context allows multiple languages on a single domain: when the audience sits in one country but speaks several languages — English and Spanish in the USA, French and Dutch in Belgium, or the many languages of Switzerland. Translated versions can live on one domain because a translation is no longer duplicate content. Google states this explicitly in its localization documentation: "Localized versions of a page are only considered duplicates if the main content of the page remains untranslated."
No special signposting is required. When an English article is translated into Spanish and published on a different URL, Google recognizes the language and ranks it accordingly — hreflang tags are unnecessary. The author still recommends setting the HTML 'lang' attribute correctly; Google doesn't use it, but other search engines do.
Where hreflang fails for news
The theory for same-language, multi-country publishing — say, English for the UK, US and Australia — is to localize content and use hreflang tags to point Google at alternate URLs. In practice, this fails for three reasons. Hreflang tags are hints, not directives, and Google doesn't always obey them. Implementation is messy, and many deployments are invalid or incomplete.
The third problem is specific to news, and the author calls it an "entirely unviable mechanism." It stems from how quickly Google indexes news content and how slowly it reindexes articles already in its index.
Consider the timeline. A UK-targeted article is published in the /uk/ folder and indexed almost immediately — with no hreflang tags, since no translated version exists yet. Shortly after, a US desk publishes its version in the /us/ folder with hreflang tags for both EN-GB and EN-US versions, and updates the British article with the same tags. Google indexes the American article quickly. But now the index holds a conflict: the American article references the British one, while Google's indexed copy of the British article lacks reciprocal tags.
Google will not use this as a trigger for instant recrawling. Reindexing the British article and validating the hreflang implementation can take hours — and in news, a gap of hours is an eternity.
A workaround exists — changing the original article's URL when the American version publishes, forcing Google to treat both as new — but the author does not recommend it. It is not guaranteed, is difficult to implement, risks duplication and redirect problems, and could be seen as an attempt to manipulate rankings. The simpler answer: accept cultural and language variations and don't republish same-language articles for different countries — the Guardian's own approach.
The recommended strategy: country-code TLDs
For multiple languages and multiple countries, subfolders work only for a handful of country-language combinations. Beyond that, complexity compounds: technical challenges, hreflang conflicts, wrong subfolders for specific audiences. Every partial solution "introduces complexity and potential conflicts later down the line."
The one strategy the author endorses without compromise: separate country-code domains for every target country. It carries extra overhead, but delivers the best long-term results, the fewest technical complications, and the closest alignment with local cultural and editorial norms.
International success is about localization, not just translation — behaving like a local, with local language, lingo, cultural references, and domains. "Don't pretend you can target French election voters while sitting in an office in Berlin, or Italian La Liga fans while writing from a sports desk in Chicago," he writes.
Audience preference reinforces the point: people in France want stories on .fr websites; people in Italy prefer sports news from .it websites. Exceptions exist but are rare.
The competitive argument is blunt. Any publisher growing an audience in a specific country competes with websites fully based there — local domains, local brand power, local journalists, local sources. Without matching that locality, the publisher stays at a disadvantage.
"But, you say, this is hard. It's complicated. It's expensive. Yes, it is. That's exactly the point. If you want to succeed internationally, don't half-ass it. Do it properly, or don't do it at all."
Source: Search Engine Journal (https://www.searchenginejournal.com/international-seo-for-publishers-how-to-succeed-across-borders/589631/) / Source: developers.google.com (https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites#generic-domains)
Source: Search Engine Journal; Source: developers.google.com



