usdigitalmarketingindex.com SEO
What is the purpose of an x-default hreflang annotation?
Updated November 15, 2026
To name the page that should be offered to searchers whose language and region match none of the versions a site has listed. Google’s documentation defines it in those terms: “The reserved x-default value is used when no other language/region matches the user’s browser setting” (Google’s documentation on localized versions of pages). A site with pages for the UK, the US, and Germany has said nothing about a visitor in Brazil. The x-default annotation fills that gap by designating a fallback. It is an addition to the set of language annotations, not a replacement for any of them, and it does not make a page the main or canonical version of anything.
What x-default denotes
Each ordinary hreflang value says “this URL is for speakers of this language, in this region”. The x-default value says “this URL is for everyone not covered above”.
Points from the documentation:
- It is “recommended for specifying the fallback page for users whose language settings don’t match any of your site’s localized versions”.
- It carries no language: “There’s no need to specify a language code for the x-default value”, because the page is aimed at users whose settings are unmatched, so its language is irrelevant to the annotation.
- It can be used on any page, though “it was designed for language selector pages and so it will work best with those”.
What it does not denote:
| Belief | Correction |
|---|---|
| x-default marks the original or master version | It marks the fallback for unmatched users |
| x-default replaces the <!–INLINECODE0–> or other language entries | It is listed in addition to them |
| x-default is a canonical signal | Canonical tags are separate |
| A set must have one | It is recommended, not required |
| The x-default page must be in English | Its language is not part of the annotation |
When a selector is appropriate
Two kinds of page serve as an x-default target.
| Target | Description | Fits when |
|---|---|---|
| A language or country selector | A page that lists the available versions and lets the visitor choose | The site has several markets and no version is a natural default |
| One of the existing versions | A general page, such as the international English version | One version is suitable for an audience from anywhere |
The documentation mentions x-default in connection with “language/country selectors or auto-redirecting home pages”, advising a fallback page for unmatched languages in those cases.
A selector page should be a real page: it loads at its own URL with a normal response, lists the versions as ordinary links, and does not redirect the visitor away before they can choose. A selector that immediately forwards every visitor based on location gives unmatched users, and crawlers, nothing to land on.
Where one version doubles as the fallback, that URL appears twice in the set: once under its own language value and once under x-default. That is valid.
Example hreflang cluster
A language selector URL alongside localized alternates, for a hypothetical site with three market versions:
<link rel="alternate" hreflang="en-GB" href="https://www.example.com/en-gb/" />
<link rel="alternate" hreflang="en-US" href="https://www.example.com/en-us/" />
<link rel="alternate" hreflang="de-DE" href="https://www.example.com/de-de/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/" />
Here https://www.example.com/ is a selector page offering the three versions. The same four lines appear on all four pages, including the selector itself.
How the set is read:
| Searcher | Version designated |
|---|---|
| English, United Kingdom | /en-gb/ |
| English, United States | /en-us/ |
| German, Germany | /de-de/ |
| Portuguese, Brazil | The selector, through x-default |
| English, Australia | No en-AU entry and no general <!–INLINECODE2–> entry; the set does not designate an English page for this searcher, and the selector is the stated fallback |
The last row shows a design choice. If Australian English speakers should be pointed to an English page, add a general en entry for the chosen English version. The documentation advises such a catch-all where several URLs serve one language in different locales. x-default then covers those whose language is not listed at all.
The alternative arrangement, with a version as the fallback:
<link rel="alternate" hreflang="en-GB" href="https://www.example.com/en-gb/" />
<link rel="alternate" hreflang="en-US" href="https://www.example.com/en-us/" />
<link rel="alternate" hreflang="de-DE" href="https://www.example.com/de-de/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/en-us/" />
For deeper pages, x-default points to the equivalent page in the fallback version, or to the selector if the site uses one for every page. It should not send every unmatched visitor of a product page to the home page.
Validation cautions
| Check | Pass condition |
|---|---|
| Format | The value is exactly <!–INLINECODE4–>, with no language or region attached |
| Target loads | The URL returns 200 and does not redirect |
| Target is indexable | Not <!–INLINECODE5–>, not blocked |
| Part of the set | The x-default line appears on every page in the set, including the target |
| Return links | The x-default target lists all the versions |
| Equivalent page | For inner pages, the target corresponds to the same content |
| Selector behavior | The selector page does not auto-redirect before rendering links |
Cautions about expectations:
- x-default influences which URL is offered to unmatched searchers. It does not raise any page’s ranking.
- It is not a fix for missing versions. A market that matters should have its own annotated page.
- It follows the same rule as all hreflang annotations: pages must point to each other, or the annotations are ignored.
- An x-default pointing at a page that forces visitors elsewhere by location defeats its purpose.
A template setting can add x-default pointing to the home page on every URL. Check inner pages specifically, since that configuration designates the home page as the fallback for every article and product.
The return-link requirement that x-default shares with every other value breaks without any visible error, and how to find those breaks is covered in the guide to how missing reciprocal hreflang references can be detected.
The summary: x-default names the page for everyone the other annotations leave out, it works best with a selector, and it sits beside the language entries without replacing them.
Add your comment to this answer