Missing X-Default Hreflang: How to Fix It

The x-default row tells Google which URL to serve when a searcher's language or country matches none of the versions you explicitly target. This check fires when your hreflang cluster is otherwise fine but has no x-default at all, leaving everyone outside your named locales to Google's guesswork.

What this check flags and the stakes

Without an x-default, a Portuguese speaker in a market you never listed, or anyone whose Accept-Language does not map to your set, gets whichever version Google decides looks closest, which is frequently the wrong one. The gap is startlingly common; our breakdown of why most hreflang setups silently break cites Patrick Stox's large-scale Ahrefs study on exactly how many live sites omit it. This check makes sure yours is not one of them.

What the fix looks like

The x-default is a single extra row appended to the same block every page already carries. It usually points at your language selector, your global homepage, or your most universal version (often English). Here it is added to a four-language set:

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

The x-default row carries no language or country attribute of its own; the value is x-default. Like every other row, it appears identically on every page in the cluster.

x-default in each delivery method

Hreflang can be delivered three ways, and the x-default row must live in the same method as the rest of your cluster. The exact syntax differs per method:

Pick one method and keep the whole cluster, x-default included, in it. Splitting a cluster across methods is a classic source of silent breakage.

Where to point x-default

The target choice is not arbitrary. This table maps common setups to the right destination.

How to detect it

1. Screaming Frog, Hreflang tab. Crawl with Configuration > Spider > Crawl > Hreflang enabled, then check the Missing X-Default filter. Frog lists every clustered URL whose set lacks the x-default row.
2. View source. Search the head of any localized page for x-default. If it is absent while other hreflang rows are present, this is your flag.
3. Validator. An hreflang validator reports a present, valid cluster with a missing x-default as a distinct, lower-severity notice, separate from hard errors.
4. Search Console, indirectly. Google removed the old International Targeting report, so there is no dedicated hreflang view anymore. Instead, open Performance > Search results, add a Country filter for a market you do not explicitly target, and check which URLs earn the impressions there. If the wrong-language version keeps surfacing for unlisted countries, a missing x-default is the usual cause.

How to fix it

1. Decide the target using the table above. Selector first, dominant version second.
2. Add the single row to your canonical hreflang block so it prints on every page, not just the homepage.
3. Confirm the target resolves 200 and does not itself geo-redirect the unmatched visitor straight back into the maze.
4. Keep it consistent across HTML, header, or sitemap; do not add x-default in one delivery method while the rest of the cluster lives in another.
5. Recrawl and validate that the row now appears everywhere.

Absent and broken are two different tickets. Once the row exists, make sure it is pointed correctly, which is the job of x-default missing or misconfigured. For the concept in isolation, the x-default definition is a quick reference, and the implementation guide shows how it fits the whole cluster.

FAQ

Is x-default required for hreflang to work?

No, a cluster without it is still valid. But it is strongly recommended, because it is the only signal covering searchers outside your named locales, and that audience is usually larger than teams assume.

Can x-default point to a page that also has its own language tag?

Yes. It is normal for x-default and, say, the en row to point at the same English URL. The English page gets both a language-specific tag and the fallback role.

Do I need x-default on every page or just the homepage?

Every page in the cluster. The block is identical across the group, so the x-default row rides along on each URL, not only the root.

Should x-default point to a language selector or a real page?

A genuine selector is ideal because it hands the choice to the user. If you have none, a stable dominant-language page is the pragmatic fallback. Avoid anything that auto-redirects by geography.

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

No. One cluster gets exactly one x-default URL, repeated identically across every page's block. Two different x-default targets inside the same cluster contradict each other, and Google will simply pick one or ignore the signal.

What happens if I just never add it?

Google serves unlisted-locale searchers its best guess from your existing rows, which is frequently the wrong language and drives the exact mismatched-result problem hreflang exists to solve.

Does x-default replace the need for language-specific tags?

No. It sits alongside them as a catch-all. You still need a real hreflang row for every language and region you target; x-default only handles the searchers who match none of those rows. Dropping the language rows in favor of x-default alone would strip Google of the precise routing it needs for your named markets.