x-default is the reserved hreflang value that marks the fallback URL in a set of language or regional page alternates. In international SEO it tells search engines which version to show when a user’s language and location settings match none of the explicitly listed versions, typically a language selector page or a global English page.
It does not target any language itself. It is a catch-all instruction inside an hreflang cluster, written in the same way as other annotations, for example hreflang="x-default", and it is recognized by Google and Yandex, while support in other engines varies.
How the fallback annotation works
Hreflang annotations form a cluster of alternates: every page version lists itself and all its siblings with a language code, optionally followed by a region code, such as de, de-AT or en-GB. When a search engine serves a result, it compares the user’s interface language and location with these codes and swaps in the best matching URL.
If no code matches, the engine would otherwise pick a version on its own, often the one with the strongest ranking signals. The x-default entry removes that guesswork by naming the page to use for all unmatched users. A French speaker in Japan visiting a site that only has German and English versions for Germany and the United Kingdom would receive the x-default URL.
The value follows the same reciprocity rule as other hreflang annotations: it must appear in the annotation set of every page in the cluster, and the x-default page itself must carry the full set, including a self-referencing entry when it is also a language version.
Where the annotation can be declared
The fallback value can be placed in any of the three supported hreflang methods. Each cluster should use one method consistently, because mixing methods increases the risk of contradictory signals.
| Method | Syntax location | Best suited for |
|---|---|---|
| HTML link elements | Link tags in the page head | Small and medium HTML sites |
| HTTP headers | Link header in the server response | PDFs and other non-HTML files |
| XML sitemap | Alternate entries for each URL | Large sites with many versions |
In the sitemap method, every URL entry lists all alternates, including the x-default line, so a cluster of ten language versions produces ten entries with eleven alternates each. The volume grows quickly, which is why sitemap generation is usually automated from the content management system.
Choosing the right fallback page
The correct target depends on the site’s international URL structure and on what an unmatched visitor needs. There is no universally right choice, but some options are clearly better than others.
| Fallback target | When it fits | Main trade-off |
|---|---|---|
| Language selector page | Many markets with no dominant language | Extra step before content |
| Global English version | English serves most unmatched users | Non-English speakers still miss out |
| Auto-redirecting root URL | Root detects language and redirects | Redirect must not block crawlers |
| Main market version | One market dominates the business | May show local prices or terms abroad |
A language selector page is the textbook use case, because it serves no single audience and lets users choose. A global English page is the most common practical choice on commercial sites. Whatever the target, it must be indexable, return status 200 and not redirect, because a redirecting or blocked fallback is ignored.
Relation to geotargeting and redirects
The fallback value is often confused with other international SEO mechanisms. The comparison below separates what each one controls.
| Mechanism | What it controls | Visible to users |
|---|---|---|
| x-default | Which URL appears in results for unmatched users | Only through the result shown |
| Language-region hreflang | Which URL appears for a matched language or region | Only through the result shown |
| Geo-IP redirect | Where a visitor is sent after clicking | Yes, changes the page loaded |
| Canonical tag | Which duplicate URL is indexed | No |
| Language selector | Manual switching between versions | Yes, an interface element |
Hreflang and the fallback value act only on search results, not on what happens after a click. A Geo-IP redirect works on the visit itself and can override the search engine’s choice. Forced redirects without an option to switch versions are a known problem, because search crawlers mostly request pages from United States IP addresses and may never see the other versions.
Common implementation errors
Most problems with the fallback value are consistency errors that cause the whole cluster to be read incompletely. The table lists the frequent ones.
| Error | Effect | Fix |
|---|---|---|
| Missing on some pages | Fallback not confirmed across the cluster | Add the entry to every version |
| Several fallback URLs | Conflicting instruction, often ignored | Keep exactly one per cluster |
| Fallback URL redirects | Annotation discarded | Point to the final 200 URL |
| Fallback set to noindex | Page cannot be shown | Make the target indexable |
| Mismatch with canonical | Signals contradict each other | Canonical each page to itself |
Search Console no longer offers a dedicated international targeting report, so validation relies on crawling tools such as Screaming Frog and on spot checks of live results from different locations. Regular audits matter, because new page versions are often published without updating the cluster. A useful rule is to treat the hreflang set as generated data, never hand-edited markup, so that every new version enters the cluster, including its fallback entry, at the moment it is published.
Explained without jargon
Imagine a hotel reception with signs in German, English and Spanish. Guests who speak one of those languages go to the matching desk. The x-default is the sign that says everyone else, please come here.
On a multilingual website it tells search engines which page to show when no language version fits the visitor. Without it, the search engine guesses, and the guess is not always helpful. It is a small line of code, but it decides the first impression for every visitor who falls outside the planned markets.
A typical use case
A software company runs its website in German, French and Italian for Switzerland and in English for the United Kingdom. Visitors from Brazil, India and the Nordic countries kept landing on the Swiss German pages, because those had the strongest links, and they left almost immediately.
The team created a neutral global English version at the root path, added it to every page as the x-default URL, and kept the regional annotations unchanged. It also replaced an automatic language redirect with a visible language selector, so crawlers could reach every version.
After the next recrawl, search results in unmatched markets showed the global English pages instead. The Swiss German pages kept their local audience, and the share of immediate exits from foreign visitors dropped clearly, confirming that the fallback page fit those users better.