Hreflang: Is it essential to translate all your pages to avoid losing international traffic?

Why does Google still insist on hreflang in 2025?

Because multilinguality remains a technical headache for most international sites. There are plenty of flawed hreflang implementations: tags in HTML and sitemap that contradict each other, quirky language codes (fr-FR instead of fr), redirection loops between versions.

Google reminds us that hreflang primarily guides users to the correct language version in the SERPs. It is not a direct ranking factor, but a signal for indexing and geographic targeting. Without it, Google may display any version of your page to any user.

What does 'acceptable but confusing' mean for the user?

Mueller admits that a partially translated site does not trigger an algorithmic penalty. Technically, you can have 50 pages in French, 30 in English, 10 in Spanish — Google will index what it finds.

The issue is the experience. A user clicking on a result expecting to find content in their language and encountering English will bounce immediately. This bounce sends a negative signal to Google, which will eventually deprioritize that URL in that language market.

Does hreflang automatically fix your targeting errors?

No. Hreflang is a signal among others: ccTLD, server IP, geographic targeting in Search Console, content language, local backlinks. If all these signals contradict each other, Google will decide — and not always in your favor.

A classic example: a .com with hreflang fr-FR hosted in the United States, without French backlinks. Google may decide to ignore your hreflang if the rest of the ecosystem shouts 'American site'. Hreflang helps clarify intent, it does not dictate it.

• Hreflang is a linguistic targeting signal, not a direct ranking factor
• A partially translated site doesn't face a technical penalty, but risks high bounce rates
• Implementation must be consistent: HTML and sitemap should say the same thing
• Google does not guarantee it will follow your hreflang if other geo signals contradict your tags
• Poor UX ultimately impacts ranking through behavioral metrics

Is this statement consistent with what we observe on the ground?

Yes and no. Google says 'acceptable' for partially translated sites, but in practice, sites that mix languages without clear logic often struggle with visibility. Why? Because Google has difficulty understanding the intent behind each orphan page.

I have seen e-commerce sites launch an English version with 20% of the catalog translated. The result: cannibalization between versions, partial duplicate content, and Google indexing the French version for English queries. Hreflang solves nothing if the site's very architecture is shaky.

In what cases does this rule not really apply?

If you are in a very technical niche with little competition, a partially translated site can perform well. Example: specialized B2B documentation where English dominates. Here, having 70% in English and 30% in French poses no issue — users are accustomed to it.

But in more popular sectors where user experience is a differentiation criterion, a partially translated site will underperform compared to fully localized competitors. Google captures UX signals: time on page, bounce rate, clicks returning to SERPs.

What nuances should be added to this statement?

Google talks about 'confusion for the user', but never quantifies the actual impact on ranking or indexing. Does a 50% translated site lose 10% of traffic, 30%, 50%? We don't know. It's typical ambiguity from Google.

Another point: Mueller assumes that untranslated pages remain accessible in all language versions. But many sites automatically redirect based on the browser's language — creating redirection loops or 404 errors for outlier users. Hreflang does not fix this type of design error.

What should you do concretely if your site is partially translated?

First, audit the consistency of your hreflang. Use Search Console, Screaming Frog, or Sitebulb to detect errors: missing tags, incorrect language codes, pages pointing to nonexistent versions. Hreflang errors are among the most common and most penalizing.

Next, segment your content by linguistic priority. Identify the pages generating international traffic and prioritize translating them. A blog with 200 articles does not need to be fully translated — focus on the 20 articles that capture 80% of organic traffic.

How to manage the UX of untranslated pages without losing SEO?

If a page only exists in English, do not hide it from French-speaking users. Display a clear banner at the top of the page: 'This content is only available in English'. This avoids immediate bouncing due to surprise.

On the hreflang side, two schools of thought. Some SEOs completely remove the hreflang tag for untranslated pages, letting Google choose. Others prefer to indicate x-default on the English version. Test both approaches and measure the impact on your impressions by language in Search Console.

What mistakes should you absolutely avoid with hreflang?

Never mix hreflang in HTML and in the sitemap if the two lists do not match 100%. Google will choose one source or the other, and you lose control. Prefer one method and stick to it.

Also avoid incomplete hreflang chains. If your FR page points to EN and ES, then EN must point to FR and ES, and ES must point to FR and EN. A broken chain = Google ignores everything. It's all or nothing.

• Check for consistency between HTML and sitemap for hreflang tags
• Correct language codes (fr-FR → fr if no specific regional targeting)
• Audit automatic redirection loops based on the browser's language
• Identify the 20% of pages generating 80% of international traffic and translate them as a priority
• Test displaying an explanatory banner on untranslated pages to limit bounce rates
• Monitor Search Console by language to detect indexing anomalies