The hreflang x-default value
x-default is a special hreflang value that names the page to serve when no other language or region annotation matches the user. It is the fallback in an hreflang set — often a language selector, a global homepage, or a generic version. This page covers when x-default is appropriate, how it interacts with the rest of the cluster, and the return-tag and self-reference rules that keep it valid.
What this means
hreflang annotations tell search engines which URL to show for a given language and optional region. x-default is the catch-all entry: it specifies the page to use when none of the other language/region values applies to the user.
Google documents x-default as the value for the page that targets no specific language or that is the default selector. Bing does not use hreflang the same way, so x-default is primarily a Google signal.
When to use x-default
Use x-default when you have a page that does not target a particular locale. Common cases include a language-picker landing page, a generic global homepage, or an English page that serves as the default for unlisted languages.
x-default is optional, but it is recommended when your audience includes locales you do not explicitly target. Without it, Google will pick the best match it can from the listed annotations, which may be less appropriate for an unmatched user.
- Value is literally x-default in the hreflang attribute
- Points to the fallback page for unmatched languages/regions
- Often a language selector or a generic/global version
- Optional, but recommended for broad international coverage
Implementation and return-tag rules
x-default participates in the same reciprocity rules as every other hreflang value. Each URL in the cluster must list every alternate, including x-default, and every alternate must point back (the return-tag rule). A page should also self-reference its own hreflang.
You can declare hreflang in HTML link elements, HTTP headers, or an XML sitemap — but use only one method per cluster, and keep absolute URLs. A broken return tag from or to the x-default page invalidates that pairing, which Search Console reports as an hreflang error.
How it appears in analytics and logs
An hreflang set that lists x-default tells Google which URL to prefer for users who do not match any targeted language or region. A missing or wrong x-default does not break crawling; it can lead to a less-ideal localized URL being shown to unmatched users in search.
Diagnostic use case
Choose the correct fallback page for international audiences whose language or region is not explicitly targeted, and validate that x-default is part of a fully reciprocal hreflang cluster.
What WebmasterID can help detect
WebmasterID records which crawler fetched which localized URL and the response it got, helping you confirm that all variants in an hreflang cluster — including the x-default target — are actually reachable and return 200, rather than redirecting or erroring during crawl.
Common mistakes
- Treating x-default as required when it is optional — though recommended for unmatched locales.
- Pointing x-default at a localized page instead of a neutral fallback or selector.
- Forgetting that x-default must be reciprocated by every other URL in the cluster.
- Mixing hreflang declaration methods (HTML + sitemap) for the same cluster.
Privacy and accuracy notes
hreflang and x-default operate on language and region annotations, not on individual user identity. WebmasterID does not geolocate or profile visitors for this purpose; any region context is a coarse edge estimate, never an exact location.
Frequently asked questions
- Is x-default mandatory?
- No. x-default is optional. Google recommends it when your hreflang set does not cover every language or region your audience uses, so unmatched users get a sensible fallback page.
- What page should x-default point to?
- A page that targets no specific locale — typically a language selector, a global homepage, or a generic default version. Avoid pointing it at a region-specific localized URL.
Related pages
- Hreflang return-tag errors
The hreflang return-tag rule requires that every URL in a language cluster references every other URL, and that each referenced URL points back. A missing back-reference is a no-return-tag error, which invalidates that pairing and is reported in Search Console. This page explains reciprocity, self-referencing, single-method consistency, and how to find and fix return-tag problems.
- Diagnosing hreflang errors
hreflang annotations tell search engines which language and regional URL to show to which users. They are easy to get subtly wrong: return tags that are not reciprocal, invalid language or region codes, hreflang pointing at non-canonical or redirecting URLs, or a missing self-reference. These errors cause search engines to ignore the cluster, so the wrong-language page can surface for users.
- Canonical tag best practices
The rel=canonical annotation tells search engines which URL is the preferred version of duplicate or near-duplicate content, consolidating signals onto one URL. It is a strong hint, not a directive — Google may choose a different canonical if other signals disagree. This page covers correct implementation: self-referencing canonicals, absolute URLs, consistency with sitemaps and internal links, and the mistakes that send conflicting signals.
- Web crawler reference
Identify which search and AI crawlers fetch your localized URLs.
Sources and verification notes
- Google Search Central — Localized versions of your pagesDocuments x-default and hreflang reciprocity rules.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.