x-default hreflang: is a missing fallback a problem?

Why this matters

Google recommends considering a fallback for unmatched languages, especially on language or country selectors. It does not require every website to add one. This catalogue entry describes a missing-fallback check; it does not mean we have tested your website. First establish whether the page has equivalent language or regional versions and which experience an unmatched visitor should receive.

How to fix it

Choose a fallback for the specific page cluster, add it alongside the existing hreflang alternatives, and check the delivered annotations on every member. Preserve legitimate regional URLs and their canonical targets. Use the examples below to distinguish a selector from a default content page before editing a template.

When should you add x-default?

For an Australian and a UK version of the same service, ask what a visitor using another language should see. If there is a useful region selector, that can be the fallback. If the international English service page serves everyone else, that page can be both en and x-default. A single-language website without regional alternatives does not need a made-up hreflang cluster. Record the intended journey instead of adding tags solely to clear a warning.

Example: regional pages with a language selector

These are fictional URLs for equivalent service pages. Put this same alternate set in the HTML head of all three pages, including the selector. Each regional page includes its own entry and the return link to the other version. The selector must help visitors reach the equivalent service in their chosen region; an unrelated homepage is not a useful substitute.

<link rel="alternate" hreflang="en-AU" href="https://example.com/au/service" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/service" />
<link rel="alternate" hreflang="x-default" href="https://example.com/select/service" />

Example: one page is both English and the fallback

A separate selector is not mandatory. In this fictional two-page cluster, the international English page serves unmatched visitors as well as English speakers outside Australia. Repeat the complete set on both pages. Two hreflang values may point to the same URL when that URL genuinely serves both roles; x-default is not itself a language code.

<link rel="alternate" hreflang="en-AU" href="https://example.com/au/service" />
<link rel="alternate" hreflang="en" href="https://example.com/en/service" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/service" />

Missing x-default or a broken language cluster?

Check for more consequential configuration mistakes before treating the fallback as the whole diagnosis: a regional page that redirects somewhere unrelated, a missing return link, or a template that gives every service the same generic fallback. Canonical and hreflang solve different problems. Do not change all regional canonicals to the fallback URL. Google asks for a canonical in the same language, or the best substitute if none exists; review the actual duplicate-content setup separately.

Verify the change on the delivered pages

Open each member and inspect the delivered HTML head, not just a template editor. Compare the full alternate sets, including self references and return links, and confirm that each absolute URL reaches the intended content. Walk through the fallback selection as an unmatched visitor. If hreflang is maintained in HTTP headers or a sitemap instead, inspect that implementation consistently. Keep the URL set and test results with the change. Correct annotations do not guarantee which result Google will show or an increase in clicks.

Turn website findings into an action plan

Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.