---
title: "x-default's real history: what Google has actually said, on record"
url: https://seomadman.com/research/hreflang-x-default-google-statements
section: research
published: 2026-07-06T00:00:00.000Z
modified: 2026-07-06T00:00:00.000Z
author: Adam Hafez
topics: ["Technical SEO"]
---

# x-default's real history: what Google has actually said, on record

## The short answer

Google introduced hreflang's x-default value on 10 April 2013, not October 2013 as sometimes repeated. John Mueller has said hreflang does not change rankings. Gary Illyes wrote in May 2023 that x-default also aids URL discovery and conversions. Google's current documentation, updated 22 December 2025, is the authoritative version today.

## Key takeaways

- Google's real x-default announcement was published 10 April 2013 by Pierre Far, not October 2013 as some pieces claim.
- John Mueller has said on record, from a Google hangout reported 18 January 2022, that hreflang does not change which pages rank, only which version is shown.
- Gary Illyes wrote in a 8 May 2023 Google blog post that x-default also helps with URL discovery and with redirecting unconverted visitors, beyond its original fallback role.
- Google's current localized-versions documentation, last updated 22 December 2025, calls x-default a recommended value for a fallback page, not a requirement.
- Where an older statement and the current documentation could both be checked, this piece treats the current documentation as the deciding version.

x-default is one hreflang value, and Google has explained it in public at least three separate
times over more than a decade: the value's own introduction in 2013, a widening of its role in
2023, and the plain ranking clarification that runs through Google's guidance on hreflang in
general. Each of those is real and dated. This piece lays out the wording each time, in order,
and then says which version is authoritative today: the current documentation, not the oldest or
the most quotable statement.

## The real history, in order

**10 April 2013 - the introduction.** Google's own announcement, "Introducing 'x-default
hreflang' for international landing pages," was posted to the Search Central Blog by Pierre Far,
then a Webmaster Trends Analyst. The post's own timestamp reads Wednesday, 10 April 2013, which
matters because a "Google introduced hreflang x-default in October 2013" claim circulates in
some hreflang guides; it does not match the primary source. The 2013 post frames x-default
narrowly: a home page that shows a country selector, or that dynamically changes content by
geolocation or Accept-Language headers, should carry `hreflang="x-default"` so Google's
algorithms know that page "doesn't target any specific language or locale and is the default page
when no other page is better suited."

**18 January 2022 - the ranking clarification.** John Mueller has repeated, across several Google
Search Central hangouts, that hreflang does not affect ranking. The clearest dated instance found
for this piece is a Google hangout reported by iloveseo.net on 18 January 2022: "the hreflang
wouldn't change the ranking of these pages, it would just make sure that the preferred version is
shown in the search results." That statement addresses hreflang as a whole rather than naming
x-default by name, and no on-record quote isolating x-default specifically from the ranking
question was located, so this piece reports the broader statement rather than inventing a
narrower one that was not said.

**8 May 2023 - the role widens.** Gary Illyes posted "How x-default can help you" to the Google
Search Central Blog on Monday, 8 May 2023, opening with "a few recent issues made us realize that
the hreflang x-default value is potentially underused." The post adds two uses past the 2013
framing: x-default URLs "may be used for URL discovery," useful on large sites where not every
localized URL is well linked internally, and x-default can redirect a visitor a page cannot
convert, Illyes' own example being a German-only essay sending non-German speakers to a language
selector "where they might actually convert in some other way." Neither use appears in the 2013
post; both are real additions, on record, a decade later.

## What Google's current documentation says now

Of the three, only one is documentation rather than a blog post, and it is the one that should
settle any disagreement between the others. Google's localized-versions page, last updated 22
December 2025, defines the reserved value directly: "used when no other language/region matches
the user's browser setting." It calls x-default "recommended for specifying the fallback page for
users whose language settings don't match any of your site's localized versions," which keeps the
2013 post's fallback framing but drops its narrower "home page" scope. It then adds a line that
resolves the tension between the 2013 post and the 2023 widening: "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." That is the current, working position: x-default is not limited to home pages, but it was
built for language and country selectors, and other uses inherit whatever weaker signal follows
from a page that was not designed with x-default in mind.

None of the three older statements is contradicted by the current page. The 2013 post's narrower
scope reads as an early framing later relaxed, not as a factual error; Illyes' 2023 additions read
as genuinely new information layered onto the original mechanism; and nothing in the current
documentation calls x-default, or hreflang generally, a ranking signal, which is consistent with
what Mueller said in 2022. Where this piece had to choose which version to state as fact, it
chose the current documentation, dated December 2025, over any older post.

## Why we care

A single hreflang value having three separate, real, dated explanations across thirteen years is
not a contradiction to untangle so much as a normal history to trace honestly, which is different
from treating whichever quote is easiest to find as if it were still current. This site's
companion piece on [hreflang error prevalence](/research/hreflang-error-prevalence-2026) traced a
different failure mode: statistics attributed to Google or to a named study that turn out not to
exist on either source's own site. The failure here would be smaller but similar, an old date or
an old scope getting repeated past the point where the current documentation already moved past
it. Implementing x-default correctly today does not require any of the three historical
statements above; it requires the current documentation's own wording, which this site's
[hreflang tag generator](/tools/hreflang-tag-generator) builds its reciprocity and self-reference
checks against directly, rather than against a 2013 blog post or a 2023 follow-up that Google
itself has since folded into the page that matters.

## Frequently asked questions

### When did Google actually introduce the x-default hreflang value?

On 10 April 2013, in a Google Search Central Blog post titled "Introducing x-default hreflang for international landing pages," posted by Pierre Far. A widely repeated "October 2013" date does not match the post's own timestamp.

### Does x-default improve rankings?

No. John Mueller has said, in a statement reported 18 January 2022, that hreflang changes which version of a page is shown, not whether it ranks. Google's current documentation never describes x-default as a ranking factor either.

### Is x-default still just for redirecting home pages?

Not only that. Gary Illyes' May 2023 Google Search Central Blog post added that x-default URLs can aid URL discovery and can redirect visitors a page cannot convert, widening the original 2013 framing.

### What does Google's documentation say about x-default today?

As of its 22 December 2025 update, Google's localized-versions page calls x-default a recommended value for specifying a fallback page, notes it works with any page but "was designed for language selector pages," and never calls it required.

## Sources

1. [Tell Google about localized versions of your page](https://developers.google.com/search/docs/specialty/international/localized-versions) - Google Search Central (primary)
2. [Introducing "x-default hreflang" for international landing pages](https://developers.google.com/search/blog/2013/04/x-default-hreflang-for-international-pages) - Google Search Central Blog (primary)
3. [How x-default can help you](https://developers.google.com/search/blog/2023/05/x-default) - Google Search Central Blog (primary)
4. [Google Says Again: Hreflang Won't Change Ranking](https://iloveseo.com/seo/google-says-again-hreflang-wont-change-ranking/) - iloveseo.net