What does hreflang x-default do?
x-default identifies the fallback page for users whose language or region does not match the other listed versions. A missing fallback is a configuration question, not proof of a ranking penalty. Start with the actual language journeys your site offers.
Choose the fallback experience
The fallback can be a language selector or an appropriate default version. Ask what an unmatched visitor should see for this specific content. A useful starting point is the intended customer journey: record the available versions, their audiences and the page that helps everyone else proceed. Do not point every service or product cluster at a generic homepage merely because it is easy to copy.
Add it to the existing language cluster
Use fully qualified alternate URLs. Each participating version should list itself and the other versions, with reciprocal annotations. Add x-default alongside those annotations rather than replacing them. The example is a small illustrative cluster: substitute the equivalent live URLs for the page being configured. You can implement hreflang through HTML, HTTP headers or a sitemap; choose a method you can maintain consistently.
<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/choose-region/service" />Check canonical and hreflang separately
Canonical identifies the preferred URL for a page; hreflang describes its language or region alternatives. Save the current canonical and alternate values before making a change. Then verify that the intended regional pages remain accessible and are not accidentally redirected or canonicalised to an unrelated page. Adding a fallback cannot compensate for a broken page or an inconsistent locale relationship.
Verify every member, not just one page
Build a small checklist from the actual cluster. Visit each listed URL, record its final address and response, and read the delivered alternate links. Test the selector or fallback as a visitor who does not use either named region. The handover should include the complete URL set and what happened on each journey, so a developer can reproduce a mismatch.
- Collect all URLs from the cluster and check that each has its intended live content.
- Compare the alternate sets and confirm reciprocal links.
- Check the fully qualified URLs for typos and unexpected redirects.
- Open the fallback and test the language or region selection path.
- Retest after the next template or routing change.
Does every website need x-default?
A single-language site without alternate regional versions does not need to invent a language cluster to clear a scanner warning. Where a real cluster exists, a fallback can help Google understand the intended unmatched-language page. This is a targeting and discovery aid, not a promise of more traffic. Record the configuration decision and compare real search landing pages over time instead of treating the absence of a tag as a diagnosis on its own.
Frequently asked questions
Is x-default a language code?
No. It is the fallback value for users not matched by the other language or region annotations.
Can the fallback be a language selector?
Yes. That is a common use. Check that it actually helps an unmatched visitor choose the correct version.
Will adding x-default guarantee better rankings?
No. Verify the cluster and the user journey, then measure search performance separately.
See where your website stands
Start with a public-signal screening report in about 60 seconds. No signup or card. Quick Scan samples the website; it does not test every topic in this guide.
Run a free scan