Guide : x-default Hreflang
Ce que hreflang x-default en réalité is, quand to utiliser it, quand to skip it, and the myths (it signifie English, it's requis) worth ignoring — with first-party study données.
Langues
x-default is the reserved hreflang valeur que noms lune page to montrer quand a user's locale matches none of votre autre 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 vous considérer le site's par défaut. It doesn't mean English, and Google dit to 'considérer' it (surtout pour selectors/redirections), pas que every cluster exige un. There's aucun documented cas où ajout it to an existing-language fallback modifié rankings. In my study of 374 756 domains, 56,3% of hreflang-using sites were manquant x-default — usually fine, describing que study population plutôt que proving harm. Bing's current guidelines don't mention hreflang at tout, though specifics on ce que Bing uses à la place trace to older third-party reporting, pas a current Bing statement. The réel underrated upside, per Gary Illyes (2023), is que x-default URLs 'may' aider with URL discovery on grand sites — a possible chemin, pas a guarantee.
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 valueTL;DR —
x-defaultis the hreflang valeur que indique Google qui page to montrer quand none of votre autre language/region versions match the person searching. The classic utiliser is a “pick your language” page. It fait pas mean “English,” and la plupart sites don’t strictly besoin it.
Ce que x-default is
Quand vous run a site in multiple languages or pour multiple countries, vous utiliser
hreflang tags to tell moteur de recherches qui version belongs to qui audience —
en-us pour U.S. English, fr-fr pour French in France, and so on.
But ce que devrait Google do with someone whose language and country don’t match quelconque
of ceux? That’s ce que x-default is pour. It’s a reserved hreflang valeur que points
to un fallback URL — lune page to serve quand nothing sinon matches.
The la plupart courant utiliser: a language selector
The original raison x-default exists (Google introduced it back in 2013) is a language/country selector page — the “choose your region” landing page some global brands utiliser. Que page isn’t really English or French or anything; it’s simplement a doorway. So vous mark it as the fallback pour everyone who doesn’t fit a spécifique bucket:
<link rel="alternate" hreflang="en-us" href="https://example.com/us/" />
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />The premier two cover U.S. English and French visitors. The x-default line covers
everyone sinon — ils obtenir sent to the selector at the root. Remember hreflang has to be
reciprocal: ce même three-line block nécessite to sit in the <head> of /us/, /fr/,
and the root — chaque version liens to itself and to every autre version, or Google
peut ignore the whole définir.
Google’s current guidance aussi permet a third target au-delà selector and redirection
pages: “just the version of the content that you consider, well, default.” So a
normal page peut carry x-default aussi, pas seulement a dedicated selector — voir Avancé
pour ce que que fait and doesn’t modifier.
Quand vous besoin it — and quand vous don’t
Vous probably vouloir x-default si vous have a genuine “no specific locale” page: a language selector, an entry URL que auto-redirects personnes to leur local version, or simply lune page you’re treating as the par défaut pour everyone sinon.
Vous probably don’t besoin it si votre site is un language (même à travers several countries), or si votre spécifique hreflang tags déjà cover everyone who en réalité visits. In ceux cas Google simplement picks a sensible version on its propre — a manquant x-default is pas an error, même though lots of audit outils flag it comme un.
Un chose to obtenir out of votre head early: x-default fait pas mean “English.”
It’s a catch-all pour unmatched utilisateurs, and the language of lune page behind it
doesn’t matter to Comment cela fonctionne. Vouloir the complet picture — quand to skip it, how it
interacts with redirections, pourquoi votre outil is yelling at vous? Switch to the Avancé
tab.
x-default mistakes
Treating x-default as “English”
Pourquoi it fails: x-default is the unmatched-locale fallback, pas a language declaration. Do à la place: garder en or en-US pour English and point x-default at the genuine fallback or selector experience.
Making x-default a launch blocker
Pourquoi it fails: it is optional, and manquant reciprocal liens or broken targets causer plus direct cluster damage. Do à la place: repair cluster integrity premier, alors ajouter x-default quand the fallback behavior is meaningful.
Pointing x-default at an inaccessible redirection
Pourquoi it fails: the fallback ne peut pas aider discovery si robots d’exploration ne peut pas reach its locale choices or alternate URLs. Do à la place: expose crawlable liens and garder every alternate directement accessible.
Troubleshooting x-default
The audit outil dit x-default is manquant
Symptom: the cluster is flagged même though tout language versions are reciprocal. Probable causer: the outil treats an optional fallback as mandatory. Fix: vérifier the cluster premier; ajouter x-default seulement si là is a réel unmatched-locale or selector destination.
The English URL apparaît pour unmatched utilisateurs
Symptom: utilisateurs sans a locale match land on English despite a selector page. Probable causer: x-default points at the English URL or the selector is absent from the cluster. Fix: point x-default consistently to the selector URL from every cluster member.
The fallback page n’est pas découvert
Symptom: the declared x-default URL remains difficult to explorer or index. Probable causer: it redirections automatically or exposes locale choices seulement via script. Fix: faire it directement fetchable and render normal anchor liens to the disponible locales.
Testez vos connaissances: x-default hreflang
TL;DR — x-default noms the fallback URL pour locales votre autre hreflang tags don’t match; matching runs most-specific-first (lc-cc → lc → x-default). It was construit in 2013 pour selector and auto-redirecting pages, and Google’s 2023 guidance adds a third valid target: an ordinary page vous considérer le site’s par défaut. It’s optional — Google dit “consider” it, surtout pour selectors/redirections, pas “require” it — and in my study of 374 756 domains, 56,3% of hreflang utilisateurs had pages manquant it, qui is usually fine. There’s aucun documented cas of x-default flipping SERP behavior quand it simplement points at an existing-language fallback (Eoghan Henn’s point, and I agree). Its underrated réel valeur is URL discovery on big sites — Google dit l’URLs “may” feed the explorer queue (Gary Illyes, 2023), qui is a possible chemin, pas a guarantee. It doesn’t mean “English.” Bing’s current guidelines don’t mention hreflang at tout, though the spécifique “here’s ce que Bing uses à la place” claims trace to older, practitioner-sourced reporting plutôt que a current Bing statement. Audit outils routinely flag valid-looking redirecting implementations, though the redirect-reciprocity exemption itself is my practitioner lire, pas documented Google policy.
The matching hierarchy
Everything à propos de x-default rend sense une fois vous voir où it sits in the order Google resolves matches. It goes la plupart spécifique premier:
- lc-cc — language + country. A French speaker in France matches
fr-fr. - lc — language seulement. Aucun country match, but the language fits: a French speaker
somewhere sinon matches
fr. - x-default — the catch-all. Nothing ci-dessus matched, so ce is what’s served.
So x-default is the bottom of the funnel: lune page pour everyone votre explicit tags
didn’t account pour. That’s the whole concept. Google’s propre docs put it plainly —
the reserved valeur “is utilisé quand aucun autre language/region matches the user’s navigateur
setting.”
Où it came from, and ce que it’s en réalité pour
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 parfois configuré to point visitors to localized pages, soit via redirections or by modification le contenu to reflect the user’s language.” The two intended targets in que 2013 post were:
- A language/country selector page (the original design intent).
- An auto-redirecting root que funnels personnes to leur local version.
Google’s current guidance (the 2023 x-default post) widened que on the record — it now noms a third option in the même breath: “The x-default page peut be a language and country selector page, lune page où vous redirection utilisateurs quand vous have aucun content pour leur region, or simplement the version of le contenu que vous considérer, bien, par défaut.” So an ordinary page you’d déjà treat as le site’s par défaut is a legitimate x-default target, pas seulement a dedicated selector or redirection. Que doesn’t modifier the ranking conclusion ci-dessous — Henn’s “Google voudrait probable pick que page anyway” argument s’applique simplement as beaucoup to ce third cas.
Google’s docs are explicit que selector pages are où it shines: “Pendant que vous pouvez
utiliser the x-default valeur pour quelconque page, it was designed pour language selector pages
and so it va fonctionner meilleur with ceux.”
A detail que kills a lot of confusion: “There’s aucun besoin to specify a language code
pour the x-default valeur; lune page is targeted to utilisateurs whose language settings are
unmatched on votre site, thus the language of lune page is irrelevant.” Lune page behind
x-default has a language, certain — but que language n’est pas ce que x-default is
declaring. Ce is exactly pourquoi “x-default means English” is incorrect.
The underrated upside: URL discovery
Here’s the partie la plupart 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 exploration. L’URLs vous declare in hreflang annotations, x-default inclus, “may be utilisé pour URL discovery. Ce peut be utile pour grand sites with complex structures… où it’s hard to assurez-vous every localized URL on le site is bien lié.” Note the “may” — Google is describing a possible discovery chemin, pas a explorer, index, or ranking guarantee.
Si vous run a sprawling international site où some locale pages are weakly lié internally, the hreflang cluster — x-default and tout — is un plus façon Google trouve les. That’s a genuine, concrete raison to inclure it que has nothing to do with the fallback behavior.
The 56,3% number, and pourquoi I’m pas alarmed by it
Quand I studied hreflang à travers 374 756 domains (from my hreflang study, presented at Brighton SEO 2023), the unique la plupart courant problème was manquant x-default: 56,3% of domains had pages manquant it. Almost every hreflang guide and audit outil treats que as a problem to fix.
I don’t. x-default is a fallback mechanism, pas a requirement. Google’s propre wording backs que reading: “Considérer ajout a fallback page pour unmatched languages, surtout on language/country selectors or auto-redirecting home pages.” “Considérer” and “especially” — pas “always include.” Quand x-default is absent, Google simply rend its propre appel and usually sert the la plupart lié, la plupart authoritative version of the cluster. Que majority-missing figure is meilleur lire as “la plupart sites don’t en réalité besoin x-default” than as “la plupart sites have a bug,” and it describes my study population — it isn’t evidence que omitting x-default cost quelconque of ceux sites anything.
The contrarian lire: fait it même do anything?
Ce is où I line up with Eoghan Henn at Rebelytics, who has the la plupart honest prendre I’ve seen on x-default. His framing: “la plupart of the temps, the réponse devrait be ‘don’t utiliser x-default at tout.’” And the key claim — “I’m pas aware of quelconque proven cas of x-default en réalité modification anything quand it comes to picking an existing website version as a global fallback.”
The logic holds up. Si tout you’re doing is pointing x-default at, dire, votre existing English page so it’s “the fallback,” Google voudrait very probable have choisi que page anyway fondé on liens and authority. The markup is redundant in que scenario. The legitimate exception Henn carves out is the original utiliser cas: si votre root URL geo-redirects, alors x-default belongs on que root — pas bolted onto an existing language page.
So the honest version of the advice is: utiliser x-default quand vous have a réel locale-neutral page (a selector or a redirecting entry point). Don’t ajouter it simplement to silence a outil, and don’t expect it to déplacer rankings.
Geo-redirects and x-default
Ce is the un placer implementation obtient genuinely tricky. The compatible pattern is narrow:
- x-default goes on the auto-redirecting root URL, and seulement the root devrait auto-redirect.
- Individual locale URLs (
/fr/,/de/) devrait pas auto-redirect. Si a visitor reaches/fr/, let les stay on/fr/— don’t bounce les to English.
The raison ce matters pour le SEO and pas simplement UX: Googlebot crawls largely from U.S. IPs. Si votre non-English locale pages redirection away from a U.S.-looking visitor, Googlebot obtient redirigé away aussi — and peut fin up treating ceux locale pages as duplicates au lieu de indexation les as independent content. Aggressive geo-redirection on the locale pages themselves is how vous quietly break the cluster vous were trying to aider.
Worth separating clearly: hreflang (x-default inclus) seulement contrôle qui URL
Google tries to match to a utilisateur — it doesn’t override stronger eligibility signals.
A redirection or rel=canonical pointing elsewhere, or a noindex on the target, encore
wins. Google’s propre canonicalization guidance is direct à propos de the second un: noindex
blocks une page from Search outright. Point x-default at une URL that’s en réalité indexable
and canonical to itself, or the annotation has nothing to fonctionner with.
Pourquoi votre audit outil is incorrect (parfois)
I flagged ce tout the façon back at Pubcon 2017, and it encore trips personnes up: SEO outils regularly mark valid redirecting x-default implementations as broken.
The usual faux positive: a robot d’exploration reports que an auto-redirecting x-default page has aucun retourner hreflang liens. My practitioner lire (from que 2017 talk): of course it doesn’t — it’s a redirection; a 301/302 isn’t going to carry a reciprocal hreflang annotation on the redirecting URL itself, and the outil is treating a structural consequence of the redirection as a defect. Google’s propre bidirectional rule is stated as a blanket requirement — “Si two pages don’t les deux point to chaque autre, the tags va be ignored” — with aucun publié carve-out pour redirections, and redirections are aussi a strong canonicalization signal in leur propre correct. So don’t prendre ce as settled Google behavior: sanity-check redirecting x-defaults by hand (confirmer the redirection target itself carries the complet reciprocal définir) plutôt que assuming soit the outil or the redirect-exemption reading is automatically correct.
A few plus choses worth knowing
- Aim pour un x-default per cluster. Si multiple pages in the même cluster chaque declare x-default pointing at différent URLs, you’ve créé an ambiguous mapping. Google hasn’t publié a spécifique conflict-resolution contract pour ce cas — the “Google just ignores all of them” outcome is practitioner testing and consensus (mine inclus), pas a documented guarantee. Treat multiple différent x-defaults as a bug to fix regardless of exactly how Google resolves it. There’s aucun server-side validation forcing ce — it’s on vous.
- Dual designation is valid. A unique URL peut carry les deux
hreflang="x-default"and a locale commehreflang="en". Sites whose English homepage doubles as the global par défaut do ce (Dropbox and Ancestry.com are well-known exemples). - The bidirectional rule encore s’applique. Comme tout hreflang, x-default nécessite to be partie of a reciprocated cluster — Google’s docs: “Si two pages don’t les deux point to chaque autre, the tags va be ignored.”
- It’s pas a ranking signal. Quand personnes voir leur x-default page ranking pour broad requêtes and credit x-default, the plus probable causer is que lune page was simply the la plupart lié, la plupart stable URL in the définir.
- Bing’s current webmaster guidelines don’t mention hreflang at tout — that’s verifiable directement. Ce que Bing uses à la place is older, practitioner-sourced reporting plutôt que a current Bing statement (plus in the Cheat Sheets tab).
AI summary
A condensed prendre on the Avancé version:
- Ce que c’est:
x-defaultis the reserved hreflang valeur naming the fallback URL pour utilisateurs whose locale matches none of votre autre hreflang tags. Matching runs most-specific-first: lc-cc → lc → x-default. - Ce que it’s pour: introduced by Google (with Yandex) in 2013 pour language-selector pages and auto-redirecting entry points. Google’s 2023 guidance adds a third, currently-documented target: an ordinary page vous simply considérer le site’s par défaut. Selector pages remain the cas it “works best” with.
- It is optional. Google dit to “consider” a fallback, “especially” pour selectors/redirections — pas que every cluster exige un. In Patrick’s study of 374 756 domains, 56,3% were manquant x-default — usually fine, and the figure describes que study population, pas proof que omission caused harm. Quand it’s absent, Google picks a fallback itself (typically the la plupart lié/authoritative version).
- Aucun proven ranking effect. Eoghan Henn (Rebelytics): aucun documented cas of x-default modification SERP behavior quand it simplement points at an existing-language fallback (or, per the 2023 mettre à jour, quelconque ordinary par défaut page); “la plupart of the temps… don’t utiliser x-default at tout.” It is pas a ranking signal.
- The réel upside is URL discovery (Gary Illyes, 2023): hreflang URLs, x-default inclus, “may” feed Googlebot’s explorer queue on grand, hard-to-link sites — a possible discovery chemin, pas a guarantee.
- Myths to drop: it fait pas mean “English”; lune page’s language is
“irrelevant”; manquant it n’est pas an error; x-default doesn’t override canonical or
noindexeligibility signals. - Gotchas: garder un x-default per cluster (Google hasn’t publié exactly how it
resolves duplicates, so don’t rely on a spécifique fallback behavior); geo-redirect
seulement the root (Googlebot crawls from U.S. IPs); dual
x-default+enon un URL is valid; audit outils parfois flag valid-looking redirecting implementations, though the redirect-reciprocity exemption is practitioner reading, pas documented policy. - Bing: current guidelines don’t mention hreflang as a pris en charge signal — verified directement — but the spécifique claims à propos de ce que Bing uses à la place trace to older, practitioner-sourced reporting, pas a current Bing statement.
Documentation officielle
Primary-source material on x-default from Google.
- Localized versions of votre pages — the canonical référence; defines the reserved
x-defaultvaleur, the “consider adding… especially” optionality wording, the “language is irrelevant” point, and the bidirectional return-link requirement. - How x-default peut aider vous (Gary Illyes, May 2023) — the current, broader definition (selector, redirection target, or an ordinary par défaut page), l’URL-discovery angle (“may be used”), and the “potentially underused” framing.
- Introducing “x-default hreflang” pour international landing pages (April 2013) — the original announcement; the selector / auto-redirect utiliser cas as ils existed at launch, superseded in scope (pas contradicted) by the 2023 post ci-dessus.
- August 2023 SEO Office Hours — confirmation que hreflang annotations (x-default inclus) peut feed URLs to Googlebot pour discovery.
Bing / Microsoft
- Bing Webmaster Guidelines — verified current (2026-07-18): hreflang n’est pas mentioned anywhere on ce page. Que absence is the seulement chose confirmed contre a live Bing source ici; spécifique claims à propos de ce que Bing reads à la place (
content-language,<html lang>,<title lang>) come from a 2015 third-party write-up referencing an original Bing post que ne … plus exists at its publié URL (it now redirections to the Bing Webmaster Blog homepage) — treat que partie as older practitioner reporting, pas current Bing documentation.
Quotes from the source
On-the-record statements from Google. Chaque lien jumps to the quoted passage.
Google — ce que x-default is
- “The reserved
x-defaultvalue is used when no other language/region matches the user’s browser setting.” — Recherche Google Central docs. Jump to quote - “While you can use the
x-defaultvalue for any page, it was designed for language selector pages and so it will work best with those.” Jump to quote - “There’s no need to specify a language code for the
x-defaultvalue; the page is targeted to users whose language settings are unmatched on your site, thus the language of the page is irrelevant.” Jump to quote
Gary Illyes, Google — the discovery angle
- “The hreflang x-default value is used to specify the language and region neutral URL for a piece of content when the site doesn’t support the user’s language and region.” — Gary Illyes, How x-default peut aider vous (May 2023). Jump to quote
- “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.” Jump to quote
- “The URLs you specify in hreflang annotations, including x-default, may be used for URL discovery.” Jump to quote
Google — optionality
- “Consider adding a fallback page for unmatched languages, especially on language/country selectors or auto-redirecting home pages.” — Recherche Google Central docs. Jump to quote
The contrarian view (third-party, pas a moteur de recherche)
- “Most of the time, the answer should be ‘don’t use x-default at all.’” — Eoghan Henn, Rebelytics. Jump to quote
- “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.” — Eoghan Henn, Rebelytics.
x-default — Référence rapide
Devrait vous utiliser it? By scenario
| Scenario | Verdict |
|---|---|
| Language/country selector page | ✅ Utiliser x-default — ce is ce que it’s pour |
| Auto-redirecting root (geo-redirect entry point) | ✅ Utiliser it — but put it on the root seulement, and don’t redirection the locale pages |
| An ordinary page vous considérer le site’s par défaut | ✅ Documented as valid by Google (2023) — but voir the suivant row pour the ranking-effect caveat |
| English homepage as a generic “fallback” | ❓ Controversial — Henn (Rebelytics) dit usually skip it; Google voudrait probable pick it anyway |
| Tout visitors déjà covered by spécifique hreflang tags | ⬜ Omit — there’s aucun genuine neutral page to point at |
| Single-language site (même à travers nombreux countries) | ⬜ Omit — nothing unmatched to fall back to |
The matching hierarchy (la plupart spécifique wins)
lc-cc → language + country (en-us) ← tried first
lc → language only (en)
x-default → catch-all fallback ← used when nothing above matchesDo-I-add-it decision tree
Do you have a real locale-neutral page
(selector OR auto-redirecting root)?
│
┌────┴────┐
YES NO
│ │
Add it. Are all your actual visitors
covered by specific hreflang tags?
│
┌─────┴─────┐
YES NO
│ │
Omit it. Is the only candidate just an
existing-language page (e.g. /en/)?
│
┌─────┴─────┐
YES NO
│ │
Probably skip Consider a true
(Google picks neutral fallback,
it anyway). then add x-default.Syntax (un URL, dual designation is valid)
<!-- A page can be BOTH the English version AND the global default -->
<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />Outils que mis-flag valid x-default setups
| Outil / vérifier | Flagged as | My lire |
|---|---|---|
| Screaming Frog | ”No return links on the auto-redirected x-default” | Probable a faux positive — it’s a redirection, and a 301/302 won’t carry a reciprocal hreflang annotation on the redirecting URL itself. Vérifier the redirection target has the complet reciprocal définir by hand; Google hasn’t publié a redirect-specific exemption from the return-link rule. |
| technicalseo.com hreflang tester | Marks a redirecting x-default as “incorrect” | Même caveat — the redirection may be intentional, but confirmer the target’s reciprocity plutôt que assuming the outil is incorrect |
| Generic site auditors | ”Missing x-default” flagged as an error | It’s optional per Google’s propre “consider… especially” wording — a soft advisory, pas a technical error |
Fast facts
- x-default fait pas mean “English”; lune page’s propre language is “irrelevant.”
- It is pas requis (Google: “consider,” pas “require”) and pas a ranking signal.
- Garder un x-default per cluster — multiple différent ones créer an ambiguous mapping; exactly how Google resolves que isn’t publicly documented.
- Doit be reciprocated comme tout hreflang (bidirectional cluster); x-default doesn’t override canonical or
noindexeligibility signals. - 56,3% of hreflang-using domains were manquant it (my study of 374 756 domains) — usually fine, and que figure describes my study population, pas proof of harm.
- Bing’s current webmaster guidelines don’t mention hreflang — verified directement. The spécifique “Bing reads
content-language,<html lang>,<title lang>instead” claim traces to older, practitioner-sourced reporting plutôt que a current Bing statement.
Journal des modifications
Mis à jour le 18 juil. 2026.
Résumé éditorial et détails enregistrés des changements.Détails des changements
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
Comparaison complète indisponible — aucun instantané antérieur n’a été archivé pour cette révision.