Your Translated Pages Are Outranking the Original Language: International SEO’s Strangest Paradox

When a translated page outranks the original-language version, hreflang is the obvious suspect. Start somewhere else. Google describes hreflang as a way to help Google Search point users to the most appropriate version of a page by language or region. It is about which version a user is shown, not about making one version stronger than another. So the first move is to find out which of two situations you are in: cross-market cannibalization, where the wrong version shows in a market, or in-market superiority, where the localized page is simply better in its own market and correctly winning there. They point to different fixes, and “fix hreflang” addresses only the first.

Where is the gap occurring?

Before touching anything, locate where the ranking difference happens. That one fact decides the diagnosis.

Cross-market cannibalization looks like this: your German page appears for English-language searches in an English-speaking market, or your Spanish page surfaces for users who should see the English original. The wrong audience is shown the wrong version. That is a real problem, and it can trace back to how the versions are annotated.

In-market superiority looks different: your German page wins in Germany, for German searches, shown to German users. That isn’t a bug. The localized page is performing better in its own market, which is what a localized page is for. Forcing the English original to outrank it there would be optimizing against your own users.

So the question is geographic and linguistic: in which market, for searches in which language, is the “wrong” page winning? If the answer is “in its own market, in its own language,” stop looking for a technical fault and ask why the original is comparatively weak.

When hreflang is the wrong place to look

Google’s guide to localized versions says the annotations help Google understand that pages are localized variations of the same content, so it can point users to the most appropriate one. If the annotations were broken, the symptom to expect is the wrong version shown to users, not a difference in strength between versions in their own markets.

Follow that through. A gap that shows up inside a market points to differences between the pages, such as content, links or page experience, not to annotations. You can audit every return tag on the site and the gap won’t close, because what separates the two pages is that one is stronger. A sprint spent on hreflang when the issue is in-market superiority is a sprint spent on the wrong layer.

What in-market superiority looks like

When the localized page is legitimately winning in its market, look at these differences:

• Localization versus word-swapping. A page translated word for word keeps the source market’s keyword choices. A localized page targets how the local audience searches: a British reader may search “trainers” rather than “sneakers.” If the translation was localized and the original was never written for that market’s vocabulary, the translation can win on relevance.
• Local links. Google’s guide to managing multi-regional sites lists links from other local sites among the signals for a page’s intended audience. A market-specific page with local press, local directories and links from sites in that country can carry signals the original, linked from another market, doesn’t.
• Page experience. Google’s page experience documentation says Core Web Vitals are used by its ranking systems, and that its core ranking systems generally evaluate content page by page. Compare the two versions’ field data: LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less at the 75th percentile, per web.dev’s Web Vitals overview. If one version passes and the other doesn’t, that is a difference to fix, not a guaranteed explanation.
• Competition by market. The same query can be harder in one market than another. A translated page can rank well in a thinner market while the original fights a crowded one, and that is a fact about the results page before it is a verdict on either page.

One more check: duplicated text. Google’s localized-versions guide says localized versions of a page are only considered duplicates if the main content remains untranslated. If a translation-memory workflow left whole sections in the source language, or reused identical untranslated blocks across pages, fix those sections. Fully translated versions aren’t duplicates of each other.

When to suspect a serving fault

If the symptom is cross-market (the wrong version shown), look at the annotation errors that can cause it: missing return links, pages that don’t list themselves, wrong language or region codes, a missing or misused x-default, and hreflang that conflicts with canonical tags or sitemap entries. The localized-versions guide sets the rules: each language version must list itself and all other versions, and if two pages don’t both point to each other, the tags are ignored.

Don’t look for Search Console’s International Targeting report; it has been deprecated, though Google says it continues to support and use hreflang tags. Check with a site crawler and your server logs instead, and cross-check against your sitemaps: a crawl follows internal links, so localized pages that nothing links to can be missing from it.

A note on architecture: Google’s multi-regional guide compares country domains, subdomains and subdirectories on setup, maintenance and how clearly they signal a target country. A translated page winning isn’t evidence that your URL structure is wrong.

Aim for the best page in each market

The goal is the best performance in each market, not the original language ranking first everywhere. If the translation wins in its own market, that is success; leave it. If the original is outperformed in its own market, raise the original: localize its vocabulary, strengthen its content, earn links in its market and fix its Core Web Vitals. Think of it as the weaker version climbing rather than the stronger version being held back. The paradox dissolves once “the original should always win” stops being the objective.

Frequently asked questions

My translated page ranks above the original in the original’s own market. Is that an hreflang problem?

Check the other causes first. Hreflang helps Google show the right version to the right user; a difference in strength within one market points to factors such as content, links or page experience. Compare the two pages on localization, links and Core Web Vitals before touching the annotations.

Should I noindex the translated page so the original wins?

No. If the translated page serves its market better, suppressing it harms the users it serves. Improve the weaker version instead of removing the one that works.