x-default

x-default is a reserved hreflang value that marks the page users should get when none of your declared language versions matches their language or location. Leave it out and Google picks the fallback for unmatched visitors itself — often not the page you would have chosen.

What x-default actually does

Every hreflang annotation says "this URL is for this audience": fr for French speakers, en-GB for English speakers in the UK. x-default answers the question the others can't: what about everyone else? A Japanese searcher on a site with English, French, and German versions matches none of the declared codes — x-default tells Google which URL to show that person.

Two classic candidates for the x-default URL:

• A language selector page — a neutral gateway where the visitor picks a country or language (this is the use case Google introduced x-default for).
• Your primary-language version — most commonly the global English page, doing double duty as both en and x-default.

Both are valid. Pointing x-default at the same URL as one of your language annotations is completely fine and extremely common.

A real hreflang block with x-default

Head-tag implementation for a three-language site where global English is the fallback:

<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Note the shape: x-default is one more annotation inside the same cluster, present on every page of the cluster, pointing at one agreed fallback URL. It follows the same reciprocity rules as everything else in hreflang.

Roles inside an hreflang cluster

Matching goes from most specific to least: exact language-region first, then bare language, then x-default catches the rest.

Signal, not directive

Worth repeating because it changes how you debug: hreflang — x-default included — is a clustering signal, not a command. It helps Google group your language versions and pick the right one to surface; Google can and does override it when other signals disagree. That also means implementation discipline matters more than tag volume: pick ONE method (head tags, HTTP headers, or XML sitemap) and never run two in parallel — mixed methods produce conflicting clusters. And despite being both free and useful, x-default is the most skipped annotation in the spec — the majority of hreflang sites ship without it, per the Ahrefs data discussed in the hreflang implementation errors guide. The dedicated check page on missing x-default hreflang covers detection and impact.

How to check it

1. Crawl the site in Screaming Frog, open the Hreflang tab, and filter "Missing X-Default" — you'll see instantly whether the annotation exists and whether it's on every page of each cluster or only some.
2. Spot-check one URL per template: curl -s https://example.com/fr/ | grep x-default. If nothing comes back and your implementation is supposed to be head tags, that template is shipping incomplete clusters.
3. If hreflang lives in your XML sitemap, fetch it and confirm every <xhtml:link> group includes an hreflang="x-default" entry.
4. Load the x-default target URL itself and confirm it's a 200, indexable, and not auto-redirecting by IP — a fallback page nobody can reach isn't a fallback.
5. Run a few URLs through the hreflang validator to confirm reciprocity across the whole cluster.

Common mistakes

• Omitting it entirely. The most common state of x-default is absent. Fix: add one line per cluster; it's the cheapest annotation in international SEO.
• x-default on some pages but not others. The homepage cluster has it, product templates don't. Inconsistent clusters are harder for Google to trust. Fix: generate hreflang from one template or feed, never per-page by hand.
• Pointing x-default at an IP-redirecting URL. If the fallback page 302s visitors by geolocation, Googlebot (crawling mostly from the US) never sees the selector. Fix: suggest with a banner, don't force-redirect.
• Different x-default targets on different pages. Page A says the fallback is /, page B says it's /en/. Fix: one fallback URL per cluster, agreed once, emitted everywhere. The x-default misconfiguration check catches this pattern.
• Treating x-default as region-specific. Writing x-default-us or scoping it per market. There is exactly one x-default value and it takes no region. Fix: hreflang="x-default", nothing else.

FAQ

Is x-default required?

No — hreflang works without it. But without it you've left the "no match" case to Google's judgment. Given that it costs one line, "optional" shouldn't be read as "skippable."

Can x-default point to the same URL as my en annotation?

Yes. That's the most common setup: the global English page serves as both the English version and the universal fallback. Two annotations, same href, no conflict.

Can I have more than one x-default in a cluster?

No. One fallback per cluster. Multiple x-default entries pointing at different URLs is a misconfiguration that undermines the whole cluster's credibility.

Does x-default have to be a language selector page?

No. Google's original announcement used a selector page as the example, but any sensible fallback works — most sites point it at their primary language version.

Does x-default help rankings?

Not directly. Like all hreflang, it's about serving the right URL to the right user — fewer wrong-language landings, fewer pogo-sticks, correct per-market indexation. The wins are in matching, not ranking boosts.