x-default Hreflang

What hreflang x-default actually is, when to use it, when to skip it, and the myths (it means English, it's required) worth ignoring — with first-party study data.

First published: Jun 25, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #3 in Hreflang#13 in International SEO#311 on the site
AIAuthored byAI v2

x-default is the reserved hreflang value that names the page to show when a user's locale matches none of your other hreflang tags. Its original job (2013) was language-selector and auto-redirecting pages; Google's 2023 guidance adds a third valid target — an ordinary page you consider the site's default. It doesn't mean English, and Google says to 'consider' it (especially for selectors/redirects), not that every cluster requires one. There's no documented case where adding it to an existing-language fallback changed rankings. In my study of 374,756 domains, 56.3% of hreflang-using sites were missing x-default — usually fine, describing that study population rather than proving harm. Bing's current guidelines don't mention hreflang at all, though specifics on what Bing uses instead trace to older third-party reporting, not a current Bing statement. The real underrated upside, per Gary Illyes (2023), is that x-default URLs 'may' help with URL discovery on large sites — a possible path, not a guarantee.

TL;DR — x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\" names the fallback URL for locales your other hreflang tagsHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. don’t match; matching runs most-specific-first (lc-cc → lc → x-default). It was built in 2013 for selector and auto-redirecting pages, and Google’s 2023 guidance adds a third valid target: an ordinary page you consider the site’s default. It’s optional — Google says “consider” it, especially for selectors/redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., not “require” it — and in my study of 374,756 domains, 56.3% of hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. users had pages missing it, which is usually fine. There’s no documented case of x-default flipping SERP behavior when it just points at an existing-language fallback (Eoghan Henn’s point, and I agree). Its underrated real value is URL discoveryURL discovery is how search engines find URLs to crawl — by pull (following links and reading sitemaps) and by push (you notify them via IndexNow, the Indexing API, or WebSub). It's the find step that comes before a page is ever fetched. on big sites — Google says the URLs “may” feed the crawl queue (Gary Illyes, 2023), which is a possible path, not a guarantee. It doesn’t mean “English.” Bing’s current guidelines don’t mention hreflang at all, though the specific “here’s what Bing uses instead” claims trace to older, practitioner-sourced reporting rather than a current Bing statement. Audit tools routinely flag valid-looking redirecting implementations, though the redirect-reciprocity exemption itself is my practitioner read, not documented Google policy.

The matching hierarchy

Everything about x-default makes sense once you see where it sits in the order Google resolves matches. It goes most specific first:

  1. lc-cc — language + country. A French speaker in France matches fr-fr.
  2. lc — language only. No country match, but the language fits: a French speaker somewhere else matches fr.
  3. x-default — the catch-all. Nothing above matched, so this is what’s served.

So x-default is the bottom of the funnel: the page for everyone your explicit tags didn’t account for. That’s the whole concept. Google’s own docs put it plainly — the reserved value “is used when no other language/region matches the user’s browser setting.”

Evidence for this claim Google defines x-default as the fallback value for users whose language or region does not match another hreflang annotation. Scope: Google Search x-default matching behavior; x-default does not declare English or any other language. Confidence: high · Verified: Google: x-default value

Where it came from, and what it’s actually for

Google (with Yandex) shipped x-default in April 2013. The original announcement frames the problem plainly: “The home pages of multinational and multilingual websites are sometimes configured to point visitors to localized pages, either via redirects or by changing the content to reflect the user’s language.” The two intended targets in that 2013 post were:

  • A language/country selector page (the original design intent).
  • An auto-redirecting root that funnels people to their local version.
Evidence for this claim Google documents x-default for locale-selector and redirecting fallback pages and says it can also help URL discovery. Scope: Google Search x-default use cases; the annotation remains part of a reciprocal hreflang set. Confidence: high · Verified: Google: How x-default can help

Google’s current guidance (the 2023 x-default post) widened that on the record — it now names a third option in the same breath: “The x-default page can be a language and country selector page, the page where you redirect users when you have no content for their region, or just the version of the content that you consider, well, default.” So an ordinary page you’d already treat as the site’s default is a legitimate x-default target, not only a dedicated selector or redirect. That doesn’t change the ranking conclusion below — Henn’s “Google would likely pick that page anyway” argument applies just as much to this third case.

Google’s docs are explicit that selector pages are where it shines: “While you can use the x-default value for any page, it was designed for language selector pages and so it will work best with those.”

A detail that kills a lot of confusion: “There’s no need to specify a language code for the x-default value; the page is targeted to users whose language settings are unmatched on your site, thus the language of the page is irrelevant.” The page behind x-default has a language, sure — but that language is not what x-default is declaring. This is exactly why “x-default means English” is wrong.

The underrated upside: URL discovery

Here’s the part most guides skip. In May 2023, Gary Illyes wrote a whole post to argue x-default is “potentially underused by sites that already use hreflang” — and his angle wasn’t rankings, it was crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor.. The URLs you declare in hreflang annotations, x-default included, “may be used for URL discoveryURL discovery is how search engines find URLs to crawl — by pull (following links and reading sitemaps) and by push (you notify them via IndexNow, the Indexing API, or WebSub). It's the find step that comes before a page is ever fetched.. This can be helpful for large sites with complex structures… where it’s hard to make sure every localized URL on the site is well linked.” Note the “may” — Google is describing a possible discovery path, not a crawl, indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or ranking guarantee.

If you run a sprawling international site where some locale pages are weakly linked internally, the hreflang cluster — x-default and all — is one more way Google finds them. That’s a genuine, concrete reason to include it that has nothing to do with the fallback behavior.

The 56.3% number, and why I’m not alarmed by it

When I studied hreflang across 374,756 domains (from my hreflang study, presented at Brighton SEO 2023), the single most common issue was missing x-default: 56.3% of domains had pages missing it. Almost every hreflang guide and audit tool treats that as a problem to fix.

I don’t. x-default is a fallback mechanism, not a requirement. Google’s own wording backs that reading: “Consider adding a fallback page for unmatched languages, especially on language/country selectors or auto-redirecting home pages.” “Consider” and “especially” — not “always include.” When x-default is absent, Google simply makes its own call and usually serves the most linked, most authoritative version of the cluster. That majority-missing figure is better read as “most sites don’t actually need x-default” than as “most sites have a bug,” and it describes my study population — it isn’t evidence that omitting x-default cost any of those sites anything.

The contrarian read: does it even do anything?

This is where I line up with Eoghan Henn at Rebelytics, who has the most honest take I’ve seen on x-default. His framing: “most of the time, the answer should be ‘don’t use x-default at all.’” And the key claim — “I’m not aware of any proven cases of x-default actually changing anything when it comes to picking an existing website version as a global fallback.”

The logic holds up. If all you’re doing is pointing x-default at, say, your existing English page so it’s “the fallback,” Google would very likely have chosen that page anyway based on links and authority. The markup is redundant in that scenario. The legitimate exception Henn carves out is the original use case: if your root URL geo-redirectsA geo-redirect automatically sends a visitor to a location- or language-specific URL based on IP or browser signals — a UX/serving mechanism that's separate from, and can actively undermine, hreflang., then x-default belongs on that root — not bolted onto an existing language page.

So the honest version of the advice is: use x-default when you have a real locale-neutral page (a selector or a redirecting entry point). Don’t add it just to silence a tool, and don’t expect it to move rankings.

TIP Generate x-default only after choosing a real fallback

The generator can include x-default and produce the annotation formats. It cannot prove that a fallback is useful, model every geo-redirect, or turn an optional value into a requirement.

If the cluster has a genuine selector or unmatched-locale entry point, add that URL in my Hreflang Generator and export the complete set together. Hreflang Generator Free

  1. Choose the fallback from user experience and routing behavior, not an audit warning.
  2. Include it with the language/region alternates on the relevant cluster members.
  3. Manually verify redirecting entry points and live return relationships after deployment.

Geo-redirects and x-default

This is the one place implementation gets genuinely tricky. The compatible pattern is narrow:

  • x-default goes on the auto-redirecting root URL, and only the root should auto-redirect.
  • Individual locale URLs (/fr/, /de/) should not auto-redirect. If a visitor reaches /fr/, let them stay on /fr/ — don’t bounce them to English.

The reason this matters for SEO and not just UX: GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. crawls largely from U.S. IPs. If your non-English locale pages redirect away from a U.S.-looking visitor, GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. gets redirected away too — and can end up treating those locale pages as duplicates instead of indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. them as independent content. Aggressive geoGenerative Engine Optimization (GEO) is the practice of optimizing content and brand presence so AI-powered search engines and assistants — Google AI Overviews, ChatGPT, Perplexity — cite, recommend, or mention you when generating answers. Google's position is that it's still SEO.-redirection on the locale pages themselves is how you quietly break the cluster you were trying to help.

Worth separating clearly: hreflang (x-default included) only controls which URL Google tries to match to a user — it doesn’t override stronger eligibility signals. A redirect or rel=canonical pointing elsewhere, or a noindex on the target, still wins. Google’s own canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. guidance is direct about the second one: noindex blocks a page from Search outright. Point x-default at a URL that’s actually indexable and canonical to itself, or the annotation has nothing to work with.

Why your audit tool is wrong (sometimes)

I flagged this all the way back at Pubcon 2017, and it still trips people up: SEO tools regularly mark valid redirecting x-default implementations as broken.

The usual false positive: a crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. reports that an auto-redirecting x-default page has no return hreflang links. My practitioner read (from that 2017 talk): of course it doesn’t — it’s a redirect; a 301/302 isn’t going to carry a reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. annotation on the redirecting URL itself, and the tool is treating a structural consequence of the redirect as a defect. Google’s own bidirectional rule is stated as a blanket requirement — “If two pages don’t both point to each other, the tags will be ignored” — with no published carve-out for redirects, and redirects are also a strong canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. signal in their own right. So don’t take this as settled Google behavior: sanity-check redirecting x-defaults by hand (confirm the redirect target itself carries the full reciprocal set) rather than assuming either the tool or the redirect-exemption reading is automatically right.

A few more things worth knowing

  • Aim for one x-default per cluster. If multiple pages in the same cluster each declare x-default pointing at different URLs, you’ve created an ambiguous mapping. Google hasn’t published a specific conflict-resolution contract for this case — the “Google just ignores all of them” outcome is practitioner testing and consensus (mine included), not a documented guarantee. Treat multiple different x-defaults as a bug to fix regardless of exactly how Google resolves it. There’s no server-side validation forcing this — it’s on you.
  • Dual designation is valid. A single URL can carry both hreflang="x-default" and a locale like hreflang="en". Sites whose English homepage doubles as the global default do this (Dropbox and Ancestry.com are well-known examples).
  • The bidirectional rule still applies. Like all hreflang, x-default needs to be part of a reciprocated cluster — Google’s docs: “If two pages don’t both point to each other, the tags will be ignored.”
  • It’s not a ranking signal. When people see their x-default page ranking for broad queries and credit x-default, the more likely cause is that the page was simply the most linked, most stable URL in the set.
  • Bing’s current webmaster guidelines don’t mention hreflang at all — that’s verifiable directly. What Bing uses instead is older, practitioner-sourced reporting rather than a current Bing statement (more in the Cheat Sheets tab).

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.