The x-default hreflang value tells search engines and AI systems which page to serve when a visitor's language or region doesn't match any of your specific localized versions. It is a fallback, not a language — and getting it wrong is one of the most common reasons international sites show the wrong version in search results and AI answers. If you run more than one language or country version of a page, you almost certainly need an x-default, and it needs to point at your language selector or your most universal version.
What x-default actually does
A standard hreflang set maps each URL to a language-region pair: en-us, en-gb, de-de, and so on. But real traffic never fits neatly into your list. A user in Japan browsing in French, or a search engine evaluating a query from a country you don't target, has no matching entry. Without a fallback, the engine guesses — often serving a version that feels foreign to the reader and confuses AI models trying to attribute the right page to a query.
The x-default entry closes that gap. It says: "if nothing else matches, send them here." Google explicitly recommends it for pages that aren't targeted to any single language, such as a country or language picker page. It is not itself a language — you do not use it to mean "English" or "our main market." Treating x-default as a synonym for your primary locale is the mistake that quietly breaks the whole cluster.
How to implement it correctly
Add x-default alongside your other hreflang annotations, and make it reciprocal like the rest. Every page in the group must reference every other page, including the x-default, and the x-default target must reference back. In HTML head form it looks like this: a set of link rel="alternate" hreflang="…" tags where one carries hreflang="x-default". You can also deliver hreflang in the XML sitemap or via HTTP headers for non-HTML files — pick one method and use it consistently, because mixing signals across methods is a frequent source of errors.
- Point it at a neutral destination. A language-selector landing page or a global homepage is ideal. If you have no selector, choose your most widely understood version.
- Keep return links complete. A missing back-reference invalidates the annotation. Every URL lists all alternates plus x-default.
- Use absolute URLs. Relative paths are not valid in hreflang.
- Match canonicals. Each localized page should self-canonicalize, not canonicalize to another language. Conflicting canonical and hreflang signals cancel each other out.
Why AI answer engines care about your fallback
Answer engines like ChatGPT, Perplexity, and Google's AI Overviews assemble responses from the page that best fits the user's context, including language. When your hreflang cluster is clean, these systems can confidently associate one canonical page per locale and cite the right one. When it is broken — missing x-default, non-reciprocal links, or an x-default that wrongly points at a single-language page — the engine cannot tell which version is authoritative, and it may cite the wrong language, split your authority across near-duplicate pages, or skip you entirely in favor of a clearer competitor. A correct fallback is part of how you present one coherent entity to machines. For the broader mechanics, see our guide to hreflang and multilingual SEO and the language-specific tactics in multilingual AEO for non-English AI citations.
Common x-default mistakes to audit
Run through this checklist on any international template. First, confirm an x-default exists at all — many sites annotate every locale but forget the fallback. Second, confirm it does not point at, say, your en-us page while also being listed as en-us; the x-default should be an additional annotation, typically on your selector or global page, not a relabel of an existing locale. Third, verify reciprocity across the entire group with a crawler, since one broken return link can invalidate the cluster. Fourth, make sure the x-default target isn't accidentally noindexed or canonicalized elsewhere — a fallback that search engines can't index defeats the purpose. Finally, watch for conflicting duplicate-content signals; if two localized URLs look nearly identical to a crawler, your canonical strategy needs to reinforce, not fight, your hreflang.
Getting the fallback right is a small tag with an outsized effect on how correctly search and AI serve your international audience. To check whether crawlers and AI systems can read your current hreflang and canonical setup cleanly, run your pages through the CheckMy.site scanner and fix what it flags before it costs you citations.