What x-default is actually for (and the three ways it's misused)

What x-default is actually for (and the three ways it's misused)

Methodology note: across audits we keep seeing x-default deployed as a catch-all bandage rather than as the specific signal it is. Worth disentangling.

The spec is narrow: x-default marks the page served to users whose language/region you haven't explicitly targeted — typically a language selector, a geo-redirecting homepage, or a global default. It is not a fallback for "any locale I forgot to list."

The three misuses we find:

— Pointing x-default at the English page purely because English is the "main" language. If en is already a targeted variant, you've now described the same URL twice with different intents
— Omitting it entirely on a true selector/splash page, leaving Google to guess what to serve unmatched audiences
— Using x-default in place of a missing locale, hoping it absorbs the gap. It doesn't — unmatched users get the default, but matched-but-unlisted users still get mis-served

The fix: reserve x-default for genuinely locale-agnostic entry points. If you have a real language picker, that's the canonical x-default target.

Caveat: x-default is optional. Sites with full per-locale coverage and no global landing page can omit it without harm. The data suggests problems arise from over-using it, not under-using it.