Hreflang: Why does Google keep insisting when so many sites manage without it?

Official statement

For multilingual sites, use hreflang markup to indicate to Google which pages are relevant for which languages, ensuring that the correct language version is displayed in search results.

61:55

🎥 Source video

Extracted from a Google Search Central video

⏱ 1h09 💬 EN 📅 24/11/2016 ✂ 13 statements

Watch on YouTube (61:55) →

✂ Other statements from this video 12 ▾

2:36 Pourquoi vos rich snippets n'apparaissent-ils pas malgré un balisage schema.org valide ?
5:13 L'automatisation de contenu est-elle autorisée par Google ?
8:19 Pourquoi vos redirections 301 vers la home peuvent-elles être traitées comme des soft 404 ?
10:44 Pourquoi Google insiste-t-il encore sur mobile, HTTPS et AMP alors que ces technologies semblent déjà généralisées ?
14:11 AMP améliore-t-il vraiment le classement Google ou est-ce un mythe SEO ?
15:22 Le mobile-friendly est-il vraiment indispensable pour ranker sur Google ?
36:53 Le Negative SEO est-il vraiment une menace pour votre site ?
39:08 Le fichier Disavow est-il vraiment utile ou Google l'ignore-t-il complètement ?
47:12 Google indexe-t-il vraiment le JavaScript comme il le prétend ?
64:01 Les commentaires spam peuvent-ils ruiner votre classement Google ?
65:26 Pourquoi les traductions automatiques plombent-elles votre SEO ?
69:29 Comment éviter les erreurs SEO techniques qui bloquent l'indexation de votre site ?

What you need to understand

What is hreflang really used for when you scratch the surface?

The hreflang markup allows you to explicitly declare to Google that a page exists in multiple language or geographic versions. You place an attribute in the <head> or in the XML sitemap to say, "this URL is the French version for France, this one is the Spanish version for Spain." Google then uses this — in theory — to display the correct URL in the SERPs based on the user's language and location.

In practice, if a user based in Madrid searches for "buy running shoes," you want them to land on /es/ and not on /fr/. Without hreflang, Google has to guess. With properly implemented hreflang, you give them a clear roadmap. This is especially critical for sites targeting multiple countries sharing the same language (Belgium FR/Switzerland FR, Spain/Mexico, USA/UK).

Does a site without hreflang get penalized?

No. There is no direct penalty. Hreflang is a recommendation signal, not an algorithmic requirement. Google tries to serve the correct version even without this markup, relying on the user's IP address, browser language, page content, and HTML lang tags.

The real risk? Cross-language cannibalization. If your FR and EN pages target the same keywords, Google may choose the wrong version for the wrong audience. The result: high bounce rates, declining conversions, confusion in analytics. Hreflang limits this mess, but does not always resolve it 100%.

What hreflang formats does Google accept and which one should you prioritize?

Three possible methods: HTML tags in the <head>, HTTP header attributes (useful for PDFs), or statements in the XML sitemap. The syntax remains the same: hreflang="fr-FR", hreflang="es-ES", hreflang="x-default" for the fallback page.

For a site with hundreds of multilingual pages, the XML sitemap is more maintainable. For smaller sites or one-off implementations, hardcoded HTML tags work well. The key point: bidirectionality. If the FR page points to ES, the ES page must point to FR. A mistake there and Google ignores the entire cluster.

Hreflang is a signal, not a directive — Google can ignore it if other signals contradict it.
No penalty for absence, but a risk of serving the wrong version to the wrong audience.
Three accepted formats: HTML, HTTP header, XML sitemap — prioritize the sitemap for scalability.
Bidirectionality is mandatory: each variant must point to the others; otherwise, Google ignores the cluster.
Be careful with language-region codes: use fr-FR, en-GB, es-MX, never just fr without specifying if you have multiple countries.

SEO Expert opinion

Is Mueller's statement really in line with what we observe on the ground?

Yes, but with a big caveat. Google has recommended hreflang for over a decade, yet a majority of multilingual sites either lack it or implement it poorly. Why? Because Google has become quite good at guessing the right version without this markup. Sites targeting linguistically distinct markets (FR/EN/DE) often manage without hreflang, especially if the content, lang tags, and subdomains or subdirectories are clear.

The real problem arises for sites targeting multiple countries with the same language: FR-FR vs FR-BE vs FR-CA, or EN-US vs EN-GB vs EN-AU. Without hreflang, Google frequently messes up. You may end up with Canadians seeing prices in euros, or Britons viewing mentions of "free shipping in the US." [To be verified]: Google claims that hreflang "ensures" correct display, but in reality, sometimes Google serves the US version to a UK user even with correct hreflang if other signals (backlinks, engagement) favor the US page.

What are the classic mistakes that kill hreflang effectiveness?

The first pitfall: missing self-referencing. Each page must include a hreflang tag pointing to itself. If the FR page forgets to declare itself hreflang="fr-FR" href="https://site.com/fr/page", Google considers the cluster invalid and ignores it. The result: zero effect.

The second common pitfall: redirect chains or non-canonical URLs. If you point to a URL that redirects with a 301, or to a duplicated non-canonical variant, Google refuses to process the signal. It should point to the final canonical URL, the one that returns a clean 200. The third mistake: using hreflang="fr" when you have multiple French-speaking countries. Google recommends fr-FR, fr-BE, fr-CA to avoid ambiguity. Without regional precision, the signal remains vague.

When does hreflang become superfluous or counterproductive?

If you manage just one country with a single language, hreflang serves absolutely no purpose. No need to declare hreflang="fr-FR" on a 100% French site targeting only France. Another case: sites using country-specific subdomains (fr.site.com, es.site.com) with completely distinct content. Google treats each subdomain as a separate site, so the risk of cross-language cannibalization is already low.

Hreflang becomes counterproductive if improperly implemented. A hreflang cluster with errors (loops, invalid URLs, inconsistencies) can degrade Google’s understanding rather than improve it. Sometimes it's better to have nothing than to have bad markup. Google Search Console flags hreflang errors, but does not fix them: if you leave warnings lingering for months, Google will eventually ignore all the markup.

Practical impact and recommendations

How can you check if your hreflang implementation is really working?

First step: Google Search Console. In the "International Targeting" section, under the "Language" tab. Google lists detected errors: missing tags, non-canonical URLs, incomplete clusters. Be aware that GSC may take several weeks to detect corrections — don't panic if errors persist a few days after a fix.

Second check: crawl with Screaming Frog or Oncrawl. Export all hreflang tags and cross-reference them in a spreadsheet. Ensure that each FR page has its EN, ES, DE equivalent, and that all variants point to each other. Look for inconsistencies: a FR page pointing to EN but not to ES, or an EN page pointing to a URL that returns a 404. An incomplete hreflang cluster = ignored cluster.

What mistakes should you absolutely avoid during deployment?

Never mix multiple methods. If you're using the XML sitemap, do not add HTML tags on top — Google may receive conflicting signals. Choose one method and stick to it. Another pitfall: pointing to URLs with parameters ?lang=fr while the canonical points elsewhere. Hreflang should target the final canonical URL, never a duplicated or parameterized variant.

Avoid deploying hreflang on non-indexable pages (blocked by noindex or robots.txt). Google cannot process a signal for a page it does not index. Finally, if you're managing a large site with thousands of pages, automate the generation of tags via your CMS or sitemap generator — any manual implementation is prone to drift and generate errors.

What concrete steps should you take for a multilingual site starting out?

Before even thinking about hreflang, structure your site properly: subdirectories (/fr/, /en/, /es/) or subdomains (fr.site.com). Avoid cookie or JavaScript solutions that switch language without changing the URL — Google cannot properly index these variations.

Once the structure is in place, generate an XML sitemap with hreflang declarations for all translated pages. Test on a sample of pages before deploying site-wide. Monitor GSC for 4-6 weeks after deployment. If you see errors, fix them quickly — Google can take time to recrawl.

Check in Google Search Console (International Targeting) that your hreflang tags are detected without errors.
Crawl your site with Screaming Frog or Oncrawl to audit the bidirectionality of hreflang clusters.
Ensure that each hreflang URL points to a final canonical URL (200 OK, no redirection).
Use x-default to designate a fallback page (often the EN version or homepage).
Do not mix multiple methods (HTML + sitemap): choose one and stick to it.
Automate tag generation via your CMS or build system to avoid manual drift.

The hreflang markup remains a delicate technical project, especially for sites with dozens of language and regional variants. Between mandatory bidirectionality, precise language-region codes, and the risks of inconsistencies in sitemaps or HTML tags, it’s easy to end up going off the rails. If your site targets multiple countries and you want to avoid serving the wrong version to the wrong audience, implementation must be rigorous. For complex projects or sensitive multilingual architectures, consulting a specialized SEO agency can save you time and avoid costly visibility errors.

❓ Frequently Asked Questions

Hreflang est-il obligatoire pour un site multilingue ?

Non, ce n'est pas obligatoire. Google peut deviner la bonne version sans hreflang, mais le balisage réduit les risques de servir la mauvaise langue à la mauvaise audience, surtout pour des pays partageant la même langue.

Peut-on utiliser hreflang uniquement pour certaines pages d'un site ?

Oui, mais chaque cluster hreflang doit être complet et bidirectionnel. Si une page FR pointe vers EN et ES, les pages EN et ES doivent pointer vers FR. Un cluster incomplet sera ignoré par Google.

Faut-il privilégier le sitemap XML ou les balises HTML pour hreflang ?

Le sitemap XML est plus maintenable pour les gros sites avec des centaines de pages. Les balises HTML en dur fonctionnent bien pour des sites plus petits. Ne mélange jamais les deux méthodes sur les mêmes pages.

Que signifie x-default dans un balisage hreflang ?

x-default désigne la page de fallback pour les utilisateurs dont la langue ou la localisation ne correspond à aucune variante déclarée. Souvent, c'est la version EN ou la homepage principale du site.

Combien de temps Google met-il à prendre en compte les corrections hreflang ?

Google Search Console peut mettre plusieurs semaines à détecter et valider les corrections. Patience : si tu as corrigé les erreurs, surveille la GSC pendant 4-6 semaines avant de conclure à un problème persistant.

🎥 From the same video 12

Other SEO insights extracted from this same Google Search Central video · duration 1h09 · published on 24/11/2016

🎥 Watch the full video on YouTube →