Does hreflang really boost rankings, or is it just an SEO myth?

What is hreflang's real function according to Google?

Hreflang is a purely user-oriented signal. It does not contribute to SERP positioning. Its mission: to tell Google which version to show a user based on their language and geographic location, among a set of already ranked pages.

In practical terms, if your page /fr/produit and your page /en/product both rank for an English query, hreflang allows the English version to be favored for a user in the UK and the French version for a French-speaking user. It is a presentation switch, not a ranking lever.

How does it differ from geographic targeting?

John Mueller makes a clear distinction: geographic targeting (via Search Console, ccTLD, or meta tags) gives a slight ranking boost for localized queries. If you target France, Google will slightly favor your site for searches conducted from France or carrying French geographic intentions.

Hreflang, however, has no impact on this boost. It only comes into play after ranking has been established. A site without hreflang can rank perfectly well in multiple countries — it simply risks showing the wrong language version to the user, which degrades the experience and increases the bounce rate.

Why does this confusion persist among practitioners?

Many SEOs associate hreflang with internationalization, and thus assume that it "helps" to rank internationally. This is incorrect. Hreflang does not open new doors: if your English page doesn’t rank in the UK, adding hreflang will not make it appear.

This confusion also comes from the fact that correcting a misconfigured hreflang can sometimes improve measured performance — not due to a ranking effect, but because Google stops showing the wrong version, reducing bounce and improving behavioral signals. This is an indirect effect, not a ranking factor.

• Hreflang is a presentation attribute: it guides the user to the correct language version after ranking.
• Geographic targeting slightly influences ranking for local queries — hreflang does not.
• Fixing hreflang does not boost ranking, but can improve UX and behavioral metrics, which may indirectly stabilize or strengthen existing positions.
• A multilingual site without hreflang can rank, but risks showing the wrong version, degrading user experience.
• Implementing hreflang should be seen as an optimization for UX and qualified traffic, not as a lever for visibility.

Is this statement consistent with field observations?

Yes, and it puts an end to a persistent myth. In practice, we regularly observe well-ranked multilingual sites without functional hreflang. They rank, but Google juggles between versions, sometimes showing the Spanish version to a French user or vice versa.

When hreflang is corrected, the ranking remains stable — what changes is the consistency of the served version. UX KPIs improve (bounce decreases, time on site increases), which may strengthen Google’s trust in the page, but this is not a direct effect of hreflang as a ranking factor.

What nuances should be added to this official position?

Mueller simplifies for clarity, but reality is a bit more complex. Hreflang can indirectly influence ranking through behavioral signals. If Google consistently shows the wrong language version, the bounce rate skyrockets, post-click CTR drops, and these signals may eventually affect positioning. [To be verified]: Google officially denies using bounce rate as a direct factor, but the field correlations are strong.

Another nuance: in highly competitive markets where multiple sites compete for the same query, well-configured hreflang can make the display difference — and thus CTR — that drives the traffic. This is not pure ranking, but the business impact is real.

In what cases does this rule not completely apply?

There are situations where hreflang seems to play a more active role, particularly in the consolidation of signals. If Google hesitates between two versions of a page (e.g., /fr/ and /fr-ca/ for a French Canadian query), hreflang provides a clear instruction, which can prevent signal dilution between two competing URLs.

Likewise, for sites with almost identical translated content, hreflang helps Google not to treat the versions as duplicate content but rather as legitimate variants. Again, this is not direct ranking, but it’s a form of protection against inter-language cannibalization.

What should you do with this information in practice?

The first thing: stop prioritizing hreflang as a visibility lever. If your pages are not ranking in a target country, focus on geographic targeting, the quality of localized content, and local backlinks. Hreflang will come later, once ranking is established.

Next, audit the existing implementation. A misconfigured hreflang can create loops, orphans, or point to non-existent versions. These errors do not harm ranking, but they break the user experience and may send negative indirect signals through behavior.

What errors should be avoided in deploying hreflang?

Classic mistake: deploying hreflang among pages that are not equivalent language variants. If /fr/chaussures-running points to /en/sneakers but the content differs substantially, Google will ignore the signal or worse, treat it as an inconsistency.

Another pitfall: forgetting the x-default tag. It serves as a fallback for users whose language or location does not match any declared variant. Without it, Google chooses randomly, damaging the UX for some traffic.

How to check that the implementation is correct?

Use Search Console, under the International Targeting section, to identify hreflang errors. The most common: non-reciprocal tags (A points to B, but B does not point to A), poorly formatted URLs, or invalid language/region codes (e.g., en-UK instead of en-GB).

Also test manually with a VPN or by changing the browser language: is Google displaying the expected version in the SERPs? If not, it's either a hreflang issue or an insufficient ranking of the target version.

• Ensure that each page with hreflang points to all its language variants, including itself (self-referential tag).
• Always include an x-default tag pointing to a fallback version (often English or the language selection page).
• Use valid ISO 639-1 (language) and ISO 3166-1 Alpha 2 (region) codes: en-GB, fr-FR, es-ES, etc.
• Regularly audit Search Console to detect reciprocity errors or referenced 404 URLs.
• Deploy hreflang only between pages with truly equivalent content — not between different themes.
• Test how variants display in SERPs via VPN or tools like BrightLocal, SEMrush, or Sistrix with geolocation.