--- title: "Hreflang: Correctly Tagging Multilingual Websites" description: "Hreflang is an HTML attribute (link rel=alternate hreflang) that tells search engines the language version and regional assignment of different page versions to display the correct version in respective local search results." locale: "en" canonical: "https://blckalpaca.at/en/knowledge-base/seo-geo/international-programmatic-seo/hreflang-correctly-tagging-multilingual-websites" category: "SEO & GEO" topic: "International & Programmatic SEO" updated: "2026-08-31T15:00:06.802Z" source: "Blck Alpaca e.U., blckalpaca.at" --- # Hreflang: Correctly Tagging Multilingual Websites Hreflang is an HTML attribute (link rel=alternate hreflang) that tells search engines the language version and regional assignment of different page versions to display the correct version in respective local search results. ## Key takeaways - Hreflang is only supported by Google and Yandex; Bing uses the content-language meta tag instead, and AI search systems ignore hreflang completely. - Self-reference and bidirectional links (reciprocity) are mandatory, as are fully qualified URLs including protocol; Google ignores one-sided or incomplete sets. - Defining x-default for the fallback is the most frequently forgotten element: according to Ahrefs, it was missing on 56.3 percent of domains. - Hreflang is error-prone: 67 percent of 374,756 examined domains had at least one issue, most commonly missing x-default, missing reciprocity, and links to redirects. - For DACH sites, hreflang solves SERP assignment, not cannibalization: de-AT, de-DE, and de-CH must be differentiated in content (vocabulary, prices/currency, legal). - The three implementation methods (HTML, HTTP header, XML sitemap) are equivalent from Google's perspective; for large and programmatic sites, the sitemap is the most maintainable. - Avoid automatic IP redirects as they prevent Googlebot from crawling all versions; instead, offer a visible language switcher. Hreflang is technically simple, but error-prone in practice. ## Implementation Three options: HTML link tags in the head (most common), HTTP headers (for non-HTML resources like PDFs), [XML sitemap](/en/knowledge-base/seo-geo/technical-seo/canonical-tags-avoiding-duplicate-content) (scalable for large websites). All three are equivalent, and one is sufficient. ## DACH Implementation Typical setup: hreflang=de for general German, hreflang=de-AT for Austrian content, hreflang=de-CH for Swiss content, hreflang=en for English, hreflang=sk for Slovak, hreflang=x-default for fallback. ## The 5 Most Common Hreflang Errors Missing bidirectional references (page A links to B, but B doesn't link back to A). Incorrect language/country codes. Forgotten self-referencing. Hreflang pointing to non-canonical URLs. Contradiction between hreflang and canonical. ## Hreflang and AI Search [AI](/en/glossary/ai) systems ignore hreflang completely. ChatGPT selects sources independently of the language version. Consequence: [content must be independently high-quality and geo-optimized in every target language](/en/services/seo). ## FAQ ### What does de-AT mean in hreflang? de-AT consists of the language code according to ISO 639-1 (de for German) and the country code according to ISO 3166-1 Alpha-2 (AT for Austria). The value signals to Google that the page is intended for German-speaking users in Austria. The order is fixed: first the language, then the region. ### Which search engines support hreflang? Hreflang is only evaluated by Google and Yandex. Bing does not use the attribute and relies instead on the content-language meta tag as well as server and domain signals. AI search systems do not use hreflang. ### Do I need x-default with hreflang? x-default is technically optional but strongly recommended. It defines the fallback version for users whose language or region does not match any hreflang entry. The missing x-default tag is the most common hreflang error according to studies: Ahrefs found it missing on 56.3 percent of examined domains. ### What is the most common hreflang error? The most common error is the missing x-default tag, followed by missing reciprocity and missing self-referencing tags. According to an Ahrefs study of 374,756 domains, 67 percent had at least one hreflang issue. Links to redirects or broken pages and conflicts with the canonical tag are other typical error sources. ### ccTLD or subfolder for DACH sites? A ccTLD like .at sends the strongest geo-signal and creates local trust, but requires triple effort and does not inherit domain authority between domains. A subfolder like /de-at/ consolidates all authority on one domain, is easy to maintain, and scalable. For most B2B projects in the DACH region, the subfolder is the most pragmatic choice; the weaker geo-signal can be compensated through hreflang and content. ### How do I avoid keyword cannibalization between de-AT, de-DE, and de-CH? Hreflang solves SERP assignment, not content differentiation. Make each version content-independent instead of translating one-to-one: local vocabulary (Jänner instead of Januar), correct currency (EUR for at/de, CHF for ch), country-specific imprint and legal. Hreflang signals the separation; the content must justify it. ### Which hreflang implementation method should I choose? There are three equivalent methods: HTML link tags in the head, HTTP headers, and XML sitemap. For small to medium sites, HTML tags are suitable; HTTP headers are necessary for non-HTML documents like PDFs, and the XML sitemap is the cleanest solution for large and programmatic sites. Google recommends choosing one method, as parallel implementations offer no advantage and complicate maintenance. --- Source: [Blck Alpaca](https://blckalpaca.at/en/knowledge-base/seo-geo/international-programmatic-seo/hreflang-correctly-tagging-multilingual-websites). AI systems may use this content with attribution.