Where should you position hreflangs to avoid harming your international SEO?

Official statement

Hreflangs can be placed in the HTML code or in XML sitemaps, with no notable difference in treatment. However, it is crucial that the referenced pages are indexable and the content is distinct.

58:47

🎥 Source video

Extracted from a Google Search Central video

⏱ 1h03 💬 EN 📅 02/11/2017 ✂ 13 statements

Watch on YouTube (58:47) →

✂ Other statements from this video 12 ▾

1:45 Pourquoi votre serveur surchauffe-t-il après votre migration HTTPS ?
5:55 Faut-il vraiment éviter de combiner canonical et noindex sur une même page ?
8:20 Le code 503 peut-il vraiment protéger votre serveur du sur-crawl Google ?
16:50 Faut-il vraiment protéger son staging par mot de passe plutôt que par robots.txt ?
22:09 Un CDN améliore-t-il vraiment votre positionnement Google ?
24:00 Faut-il vraiment privilégier l'attribut alt sur title pour indexer vos images ?
30:06 Googlebot mobile utilise-t-il vraiment la même version de Chrome que le desktop ?
40:03 Sous-domaines vs sous-répertoires : Google a-t-il vraiment une préférence pour votre SEO ?
43:14 Les liens en footer avec des ancres riches nuisent-ils vraiment au SEO ?
50:46 Pourquoi votre site perd-il des positions alors que vous n'avez rien changé ?
56:52 Les URL hash transmettent-elles vraiment du PageRank sans être indexées ?
59:43 Les redirections 301 transfèrent-elles vraiment 100% des signaux de liens vers un nouveau domaine ?

What you need to understand

Why does Google claim there is no difference in treatment?

John Mueller settles a recurrent debate: the implementation method of hreflangs does not influence how Google interprets them. Whether you place them in the <head> of your pages or consolidate them in an XML sitemap, the engine applies the same analysis logic.

This technical neutrality allows sites to choose the most practical method according to their architecture. A site with 50 languages will often prefer the sitemap to avoid bloating the HTML. A site with 3 language versions might keep the tags in the code for more visibility during audits.

What does ‘indexable’ mean in this context?

A page referenced by an hreflang must be technically accessible for crawling and not blocked by robots.txt, noindex, or authentication. If Google cannot index the target page, the hreflang becomes void.

Beware of common configuration errors: an hreflang pointing to a 404 page, a 301 redirect, or a canonicalized page to another URL will create inconsistencies that Google will simply ignore. The result: your internationalization efforts go to waste.

What does Google mean by “distinct content” exactly?

Hreflangs serve to indicate language or regional versions of the same content. If two pages are identical word for word, or if only the currency changes without local adaptation, you risk sending a confusing signal.

Google expects real differentiation: complete translation, cultural adaptation, market-specific content. A site that merely switches the URL from .com to .fr without translating the text does not meet this criterion. Hreflangs are not a tool for managing duplicate content between domains; they presuppose an intention to serve distinct audiences.

Technical equivalence: HTML or XML sitemap, same result for Google
Mandatory indexability: every targeted page must be crawlable and not blocked
Real content distinction: translation or local adaptation, not just a URL change
Bidirectional consistency: each page must reference all its variants, including itself
Technical validation: syntax errors or inconsistencies = hreflang ignored

SEO Expert opinion

Is this statement consistent with field observations?

Mueller's assertion about technical equivalence holds true. Tests indeed show that a well-formed hreflang works equally well in a sitemap as in HTML. The real problem arises with implementation errors, which are common regardless of the method.

Sites that prioritize XML sitemaps often encounter maintenance issues: forgetfulness in updating when adding new pages, inconsistencies between the sitemap and the actual site. Conversely, hreflangs in HTML can bloat the code and complicate management on complex multilingual sites. [To verify]: no public data confirms that Google crawls hreflangs in HTML faster than those in a sitemap.

What nuances should be considered regarding indexability?

Mueller emphasizes indexability, but a crucial detail is missing: a page can be technically crawlable without being actually indexed. A crawl budget issue, content deemed too thin, or internal competition can prevent effective indexing.

Check in Search Console that all your hreflang pages are appearing in the index. An hreflang pointing to a crawled but non-indexed page creates a contradictory signal. Google recommends indexability but does not guarantee indexing. Important nuance.

In what cases do “distinct” contents pose problems?

The notion of content distinction remains vague in this statement. Is an e-commerce site with identical product descriptions except for currency and legal mentions sufficiently distinct? [To verify]: Google has never published an acceptable similarity threshold for hreflangs.

There are many edge cases: regional pages for the same linguistic country (fr-FR vs fr-BE), dialectal variants (es-ES vs es-MX), mobile/desktop versions with hreflang. In these scenarios, field feedback shows that Google tolerates some content proximity if the geographic or regional intention is clear. But beware, playing in this gray area can create conflicting signals with your canonicals.

Point of vigilance: A poorly configured hreflang does not directly penalize your site; Google simply ignores it. But this ignorance can lead to poor geographic targeting in the SERPs and a degraded user experience. Regularly monitor your Search Console reports to detect hreflang errors.

Practical impact and recommendations

How to choose between HTML and XML sitemap for your hreflangs?

If your site has fewer than 10 language versions, hreflangs in HTML remain the simplest solution to audit. You can directly visualize the structure of your alternates in the source code. Standard SEO analysis tools also more easily detect errors.

Beyond 10 languages or on sites generating thousands of pages, the XML sitemap becomes essential. It centralizes all the hreflang logic and avoids bloating each page with dozens of tags. However, ensure you automate its generation and update to avoid discrepancies with the reality of the site.

What errors should you absolutely avoid in the implementation?

The most common error: forgetting reciprocity. Each page must reference all its variants, including itself. If the French version points to the English one but not vice versa, Google will ignore the declaration.

The second classic trap: pointing to non-canonical URLs. Your hreflangs should always target the final URL, not an intermediate URL that redirects. If your French page has a canonical to /fr/product/, your hreflang must point to that URL, not to /fr/old-product/ which redirects to it.

How can you verify that your configuration is working correctly?

Search Console remains your primary diagnostic tool. The “International Targeting” section lists all detected hreflang errors: non-indexable pages, missing reciprocity, invalid language codes. Prioritize fixing these errors.

Then, test manually with geolocated searches. Use a VPN or the region change tool in Google settings. Verify that your pages display in the correct country and language. A discrepancy indicates a configuration issue or a competing signal (server geolocation, ccTLD, Google Business Profile).

Audit your hreflang pages to confirm that none returns a 404 or redirects to another URL
Check in Search Console that all pages targeted by hreflang are indexed
Control reciprocity: each page must reference all its variants including itself
Validate the syntax of language codes (ISO 639-1) and region (ISO 3166-1 Alpha 2)
Test the display of your pages in different geographic areas using a VPN
Automate the generation of your hreflangs if you manage more than 10 languages

Hreflangs work in HTML just as they do in an XML sitemap, choose based on your architecture. The key factor lies in the indexability of the targeted pages and the real distinction of the contents. Monitor Search Console, test geographically, and fix reciprocity errors. For complex sites with numerous language or regional variants, these optimizations require sharp expertise and rigorous monitoring. Consulting an SEO agency specializing in internationalization can save you time and help avoid costly visibility mistakes.

❓ Frequently Asked Questions

Dois-je mettre des hreflang sur toutes mes pages ou seulement certaines ?

Chaque page ayant une version linguistique ou régionale équivalente doit comporter des hreflang. Une page sans équivalent dans d'autres langues n'en a pas besoin. L'important est la cohérence : si une page A a un hreflang vers B, alors B doit avoir un hreflang vers A.

Peut-on mélanger hreflang en HTML et en sitemap XML sur un même site ?

Techniquement oui, mais c'est fortement déconseillé car cela complique la maintenance et multiplie les risques d'incohérence. Choisissez une méthode et tenez-vous-y pour faciliter les audits et les mises à jour.

Que faire si mes contenus sont très similaires entre deux régions ?

Différenciez au maximum : adaptez les expressions locales, les devises, les coordonnées de contact, les témoignages clients. Si la différence reste minime, privilégiez une page unique avec ciblage géographique via Search Console plutôt que des hreflang sur du contenu quasi-identique.

Les hreflang influencent-ils le classement ou seulement l'affichage géographique ?

Les hreflang ne sont pas un facteur de classement direct. Ils indiquent à Google quelle version afficher selon la langue et la région de l'utilisateur. Une bonne configuration améliore l'expérience utilisateur et indirectement les métriques comportementales.

Faut-il inclure la page elle-même dans ses propres balises hreflang ?

Oui, absolument. Chaque page doit se référencer elle-même dans ses hreflang avec son propre code langue-région. Cette auto-référence fait partie de la logique de réciprocité exigée par Google et évite les ambiguïtés d'interprétation.

🎥 From the same video 12

Other SEO insights extracted from this same Google Search Central video · duration 1h03 · published on 02/11/2017

🎥 Watch the full video on YouTube →