What is x-default hreflang?
x-default is the hreflang value for visitors who match none of your language or country versions — what it means and when your site actually needs one.
x-default is a special hreflang value that tells search engines which page to show a visitor whose language or region does not match any of your other versions. It is not a language itself; it is a fallback rule, typically pointing to a global homepage or a page where visitors pick their version manually.
It is one small piece of the multilingual SEO puzzle, easy to skip and easy to get backwards, which is why it earns its own explanation here rather than a passing mention in a longer checklist. It is also the kind of detail our technical SEO service checks by default on any international audit, since it is cheap to fix and easy to miss.
What does x-default actually mean?
It marks one hreflang entry as the catch-all: the version to serve when a visitor's language and location do not match any of the specific versions you have declared. Google's own documentation on international sites lists it as an optional value used exactly for this purpose, alongside the language and language-region codes that cover your named versions [1].
Concretely, if your hreflang set declares en, fr, and de, a visitor browsing in Portuguese matches none of them. Without x-default, there is no explicit instruction for that visitor; with it, you have told search engines exactly where to send someone in that position — usually a genuinely global page, or a page that lets them pick a version themselves rather than guessing on their behalf.
The name itself causes some confusion, because "default" suggests something automatic rather than something you declare on purpose. It is closer to a named parameter than a fallback that happens by accident: you are explicitly telling search engines "if nothing else matched, use this one," the same way a switch statement's default case is written deliberately rather than left to chance.
When do you actually need it?
Whenever your site has more than one version and you want a defined answer for visitors outside your declared set, which in practice is nearly every multilingual or multi-regional site. A company with English, French and German versions selling globally will always have some traffic in other languages, and x-default is what determines what those visitors see instead of an undefined default.
| Target | Fits when | Risk |
|---|---|---|
| A genuine global/international page | You have a real language-neutral landing page | None, if that page actually exists and is maintained |
| A language or country selector page | You want unmatched visitors to choose explicitly | Adds a click before they reach content |
| Your primary language's homepage | That language functions as a true global default | Reads as a false default if it is really just one market's page |
| No x-default set | A small site with only one or two close variants | Unmatched visitors get no explicit fallback instruction |
A site selling only to French and German markets, with no global ambition beyond those two, may reasonably skip x-default — there is no meaningful "everyone else" audience to route. A site with global reach and dozens of markets almost always benefits from declaring one.
How do you implement it correctly?
Add it as one more entry in the same hreflang set you already maintain, using x-default in place of a language code, pointed at your chosen fallback URL. It follows the same rules as every other hreflang value: it needs to appear consistently across every page in the set, and the fallback page itself should link back into the set the same way any other version does.
On a large site, put hreflang — x-default included — in your XML sitemap rather than repeating it in every page's head, since sitemap-based hreflang is easier to validate and maintain at scale [3]. Whichever method you use, the value has to agree everywhere it appears; a fallback declared in the sitemap but contradicted in a page's own tags is the kind of inconsistency that undermines the whole set, not just the one page.
One decision worth making deliberately: do not let x-default default to whichever language happened to launch first by accident. If that language is not actually meant to represent everyone outside your declared markets, a dedicated global page or a selector is the more honest choice, and it matters most on pages where a wrong guess costs something real, such as translated product pages or an international storefront where the wrong currency or unavailable stock actively costs a sale.
What happens if you get it wrong?
Nothing breaks loudly. An unmatched visitor lands on whatever page you pointed x-default at, correct or not, and there is no error message anywhere to flag the mismatch. If that page is not actually a sensible default — an outdated page, a market-specific page mistaken for a global one, or an unedited machine translation rather than a properly reviewed page — an unpredictable slice of your traffic quietly gets a worse experience with nothing in your analytics calling it out by name. The fix is cheap once you know to look for it; the cost of not looking is a steady, invisible leak in exactly the traffic segment you have the least visibility into.
Questions people also ask
Is x-default required on every multilingual site?
No. It is genuinely optional — Google will still work out language and country matches from your other hreflang entries without it. It matters specifically for the visitor who matches none of your listed versions, which is a real but not universal case.
Can x-default point to a redirect?
It can technically resolve to a redirect, but it is cleaner and more reliable to point it at a real page directly — either a genuine global default or a selector page — rather than adding a redirect hop that can complicate crawling.
What's the difference between x-default and a normal hreflang value like en?
A normal hreflang value like en or en-US declares a version for a specific language or region. x-default is not a language at all; it is a catch-all for everyone who does not match any of those specific declarations.
Should x-default point to my English page?
Only if your English page is a genuine, sensible default for an unmatched visitor — for instance if English is your primary global language. If you have a true global landing page or a language selector, that is usually a better target than picking one language and calling it the default for everyone.
Sources
- Tell Google about localized versions of your page — Google Search Central (checked 23 September 2026)
- Managing multi-regional and multilingual sites — Google Search Central (checked 23 September 2026)
- Build and submit a sitemap — Google Search Central (checked 23 September 2026)
Not sure your hreflang set is complete?
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Multilingual SEO: a complete guide for 2026How multilingual SEO works: URL structure, hreflang, translation, keyword research and redirects, with what each decision costs and how to check it is working.
- International Ecommerce SEO: A Practical GuideHow to structure, translate and rank a store across multiple countries without splitting your authority or shipping the wrong currency to the wrong market.
- Translating Product Pages Without Losing SEOMachine translation alone is not enough for product pages that need to rank. Here is what to translate, who should own it, and a workflow that scales.
- Is machine translation OK for SEO?Machine translation is fine for SEO once a person edits it and you publish at a pace an editor can manage; raw output at scale is what Google's policy targets.