Hreflang and multilingual AI visibility
Why hreflang is essential for multilingual AI strategy
When your website offers content in multiple languages, a fundamental problem arises: how do AI models know which language version to cite? Without clear directions, an English-language AI model might cite your Dutch page for an English question, or worse, consider two language versions as competing pages. Hreflang tags solve this problem by explicitly indicating which pages are translations of the same content.
This problem touches on multiple aspects of AI optimization we have discussed before. The relationship between language versions is comparable to the canonical URL question: if AI models do not understand which page is the 'original' in which language, it can lead to fragmentation of your authority signals. Combined with correct Schema.org markup, hreflang forms the backbone of every multilingual AI strategy.
Google fully supports hreflang. Other AI crawlers such as GPTBot and ClaudeBot do not always explicitly process hreflang, but they indirectly benefit from the clear language structure that hreflang enforces on your website.
Implementing hreflang tags correctly
Hreflang tags tell search engines and crawlers that a page is available in multiple languages or for multiple regions. There are three ways to implement hreflang: via HTML link elements in the head, via HTTP headers, or via the XML sitemap.
Method 1: HTML link elements
<head>\n <!-- Hreflang tags for a NL/EN website -->\n <link rel="alternate" hreflang="nl" href="https://aeo-expert.nl/blog/hreflang-gids" />\n <link rel="alternate" hreflang="en" href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n <link rel="alternate" hreflang="x-default" href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n\n <!-- Canonical URL (always the current language version) -->\n <link rel="canonical" href="https://aeo-expert.nl/blog/hreflang-gids" />\n</head>Each hreflang element contains two attributes: hreflang (the language code) and href (the full URL of that language version). The x-default value indicates which version should be shown when none of the specified languages matches the user's preference. This is typically the English or primary language version.
Method 2: Hreflang in the XML sitemap
For larger websites with many language versions, implementation via the XML sitemap is more efficient. This keeps your HTML head clean and centralizes all language information in one place.
<?xml version="1.0" encoding="UTF-8"?>\n<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"\n xmlns:xhtml="http://www.w3.org/1999/xhtml">\n <url>\n <loc>https://aeo-expert.nl/blog/hreflang-gids</loc>\n <xhtml:link rel="alternate" hreflang="nl"\n href="https://aeo-expert.nl/blog/hreflang-gids" />\n <xhtml:link rel="alternate" hreflang="en"\n href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n <xhtml:link rel="alternate" hreflang="x-default"\n href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n </url>\n <url>\n <loc>https://aeo-expert.nl/en/blog/hreflang-guide</loc>\n <xhtml:link rel="alternate" hreflang="nl"\n href="https://aeo-expert.nl/blog/hreflang-gids" />\n <xhtml:link rel="alternate" hreflang="en"\n href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n <xhtml:link rel="alternate" hreflang="x-default"\n href="https://aeo-expert.nl/en/blog/hreflang-guide" />\n </url>\n</urlset>Dive deeper: Canonical URLs and duplicate prevention | Schema.org markup for AI | What is AEO?
The golden rules of hreflang
Hreflang implementation is notorious for its complexity and the volume of mistakes made. Follow these rules to avoid problems.
- Bidirectional references are mandatory. If page A references page B as the English version, page B must also reference page A as the Dutch version. One-way references are ignored.
- Every page must reference itself. The Dutch page therefore has an hreflang="nl" link to itself, alongside the reference to the English version.
- Use correct language and region codes. Language codes follow ISO 639-1 (nl, en, de, fr). Region codes follow ISO 3166-1 Alpha 2 (nl-BE, en-US, de-AT). Invalid codes are ignored.
- Canonical URL and hreflang must be consistent. A page's canonical must always point to its own URL, not to a translation. Hreflang and canonical work independently of each other.
- Use x-default for the fallback version. This prevents users with an unsupported language preference from seeing no version at all.
Hreflang and AI models: the practical impact
Although not all AI crawlers explicitly process hreflang in the same way as Google, there are multiple indirect benefits.
- Language recognition: hreflang tags confirm the language of a page, which helps AI models select the correct version for an answer in a specific language.
- Duplicate prevention: by implementing hreflang correctly, you prevent AI models from treating your Dutch and English versions as competing pages.
- Authority consolidation: hreflang tells AI models that two pages represent the same authority in different languages, making your combined authority stronger.
- User experience: when an AI model cites a source, it can select the correct language version based on the language of the question.
Schema.org inLanguage as a complement to hreflang
In addition to hreflang tags, it is recommended to explicitly indicate the language of your content in your Schema.org markup. The inLanguage property tells AI models directly in which language the content is written.
<script type="application/ld+json">\n{\n "@context": "https://schema.org",\n "@type": "Article",\n "headline": "Hreflang and multilingual AI visibility",\n "inLanguage": "en",\n "author": {\n "@type": "Organization",\n "name": "AEO Expert"\n },\n "datePublished": "2026-04-24",\n "availableLanguage": [\n {\n "@type": "Language",\n "name": "Dutch",\n "alternateName": "nl"\n },\n {\n "@type": "Language",\n "name": "English",\n "alternateName": "en"\n }\n ]\n}\n</script>By adding inLanguage to your Schema.org, you give AI models an extra strong signal about the language of your content. This is particularly valuable for models that do not fully parse the HTML head but do process JSON-LD.
URL structure for multilingual sites
The way you structure your URLs for different languages affects how crawlers understand your site. There are three common approaches.
- Subdirectory per language (recommended): example.com/en/blog/article. Easy to manage, consolidates domain authority and is the clearest for crawlers.
- Subdomain per language: en.example.com/blog/article. More technical complexity and split domain authority. Not recommended for most sites.
- Separate domain per language: example.com for English, example.nl for Dutch. Maximum separation but also maximum authority dilution. Only sensible for very large international brands.
For most multilingual websites, the subdirectory approach offers the best compromise between simplicity, SEO benefit and AI visibility. AI crawlers can infer the language structure from URL patterns, and you retain all domain authority on a single domain.
Multilingualism is not an obstacle to AI visibility. With correct hreflang implementation and Schema.org inLanguage, you turn each language version into an asset rather than a competitor.
Common hreflang mistakes
- Missing return references: page A references page B, but page B does not reference back. Both references are then ignored.
- Invalid language codes: "dutch" instead of "nl", or "en-UK" instead of "en-GB". Only ISO standard codes are accepted.
- Hreflang pointing to a page with a different canonical: if the hreflang URL redirects to a different page, the hreflang is ignored.
- Not specifying x-default: users with an unsupported language preference then receive no fallback version.
- Confusing hreflang and canonical: hreflang references language versions, canonical references the preferred URL. They have different functions and must each be correct independently.
Key takeaways
- Hreflang tags are essential for multilingual websites to help AI models select and cite the correct language version.
- Implement hreflang bidirectionally: every page must reference all language versions, including itself.
- Combine hreflang with Schema.org inLanguage for a doubly strong language signal to AI models.
- Use the subdirectory structure (example.com/en/) for the best compromise between manageability and AI visibility.
- Prevent duplicate confusion by implementing hreflang, canonical and Schema.org consistently and correctly across all language versions.
Frequently asked questions
Should my hreflang tags be in the HTML head or in the sitemap?
Both methods are valid and supported by Google and AI crawlers. For small sites with few language versions, HTML link elements are simplest. For large sites with dozens of language combinations, the sitemap method is more efficient and organized. Never use both methods simultaneously for the same page, as that can lead to conflicts.
Do AI models like ChatGPT process hreflang tags?
AI models do not always process hreflang in the same way as Google, but they benefit from it indirectly. Hreflang enforces a clear language structure on your website that makes it easier for any crawler type to identify the correct language version. Additionally, AI models use the lang attribute on the HTML element and Schema.org inLanguage as supplementary language signals.
What if I have a page that is not translated?
If a page is only available in one language, you do not need hreflang tags. Hreflang is only useful when there are actually multiple language versions of the same content. It is better to have no hreflang than an incorrect implementation with missing pages.
How do I handle regional variants of the same language?
Use the extended hreflang notation with region codes. For example: hreflang="nl-NL" for Netherlands Dutch, hreflang="nl-BE" for Belgian Dutch, and hreflang="nl" as the general Dutch fallback. This is especially relevant for languages with significant regional differences, such as English (en-US, en-GB) or Spanish (es-ES, es-MX).
Does hreflang affect the AI score of my website?
Hreflang has no direct impact on scoring systems of individual AI models. However, it does increase the chance that the correct language version of your content is cited, leading to a better user experience and higher relevance. Indirectly, this strengthens your authority signals, because consistent, correctly structured multilingual content appears more professional to both humans and machines.
Hreflang is the translator between your website and the world. Without hreflang, you might be speaking the right language, but nobody understands which language you are speaking.
How does your website score on AI readiness?
Get your AEO score within 30 seconds and discover what you can improve.
