GuidesMultilingual SEO
Hreflang across twelve languages: the method that holds up
The four rules
- 1ReciprocityIf A lists B, B lists A.
- 2Self-referenceEach page lists itself.
- 3x-defaultThe version served when no language matches.
- 4Canonical in its own languageNever pointing to another language's version.
In the sitemap
<url>
<loc>https://example.com/en/guide</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/guide"/>
<xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/guide"/>
<xhtml:link rel="alternate" hreflang="es" href="https://example.com/es/guia"/>
<!-- … the nine other languages … -->
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/guide"/>
</url>
The block repeats for each of the twelve URLs, with the same list. A script generates it from the translation table: nobody writes it by hand.
A real example
Small Eden, one of our projects, is published in twelve languages with hreflang tags and a sitemap of nearly 6,000 URLs.
Common mistakes
| Mistake | Consequence |
|---|---|
| Link to a redirected or 404 page | Annotation ignored |
| Made-up code (en-UK instead of en-GB) | Annotation ignored |
| Missing translation listed anyway | Link to a page that doesn’t exist |
| Canonical pointing to the English version | Other languages disappear |
The basics: multilingual SEO. The tool: hreflang tag generator.
Frequently asked questions
- HTML head or sitemap?
- Google accepts both. Beyond a few languages, the sitemap avoids weighing down every page and is generated from one place.
- What if a link isn't reciprocal?
- Google may ignore the annotation: if the English page lists the French one but not the reverse, the pair isn't taken into account.
- Do I need a region, like en-GB?
- Only if the content changes by country (price, currency, delivery). Otherwise the language code alone (en) is enough.
