hreflang for Multilingual GEO: How AI Finds the Right Market Version
How hreflang, canonical tags, x-default, and localized sitemaps affect AI visibility across countries and languages.
International SEO already depends on hreflang. Multilingual GEO depends on it too, because AI systems need to know whether /en/pricing/, /de/pricing/, and /fr/pricing/ are separate pages or alternate versions of the same offer.
GEO Scout makes the claim measurable: the same brand can appear in English AI answers and disappear in German or French prompts if localized pages are not crawlable, linked, and attributed correctly.
Basic hreflang Pattern
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing/" />Every localized page should include a self-reference and all alternates. The German page points to German, English, French, and x-default. The English page does the same.
Language vs Region
| Code | Meaning | Use when |
|---|---|---|
en | English, all regions | One global English page. |
en-US | English for the US | US pricing, shipping, compliance, or terminology differs. |
en-GB | English for the UK | UK currency, legal wording, or availability differs. |
de | German, all regions | One German version serves all German-speaking users. |
de-DE | German for Germany | Germany-specific content exists. |
Artificially splitting languages by country without meaningful content differences creates noise. AI systems need clearer entity relationships, not more duplicate URLs.
Canonical Rules
Localized pages should normally canonicalize to themselves:
<link rel="canonical" href="https://example.com/de/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />Do not canonicalize /de/pricing/ to /en/pricing/ unless the German page is not meant to be indexed. That mistake tells crawlers that the German page is a duplicate and can remove it from AI retrieval.
Why x-default Matters
AI crawlers do not always arrive with a clean user locale. x-default tells them which version is the fallback. For global B2B and SaaS companies, the best fallback is usually the full English page, not a thin language selector.
Multilingual GEO Checklist
- Use self-referencing hreflang on every localized URL.
- Keep hreflang links symmetric across all versions.
- Use canonical tags within the same locale.
- Add x-default to a real content page.
- Include hreflang in XML sitemaps for large sites.
- Monitor prompts in every target language in GEO Scout.
Частые вопросы
Do AI crawlers read hreflang?
Should I use en or en-US?
What is x-default for GEO?
Can canonical conflict with hreflang?
Is sitemap hreflang better than head tags?
How do you measure multilingual AI visibility?
Related Articles
Breadcrumbs Schema for AI: How Site Hierarchy Helps Neural Search Cite You
How BreadcrumbList helps AI systems understand site architecture, attribute pages correctly, and cite the right section of your website.
Cloudflare AI Audit and Bot Management: How to Control AI Crawlers
How Cloudflare AI Audit, Bot Management, AI Labyrinth, and pay-per-crawl policies help teams allow, limit, or block AI bots.
E-E-A-T and Author Schema for AI: How Expertise Signals Work in Neural Search
How Person schema, ProfilePage, sameAs, author pages, and external credentials help AI systems trust and cite expert content.