Hreflang x-default: When and How to Use It
What the x-default hreflang value does, when to use it, and how to implement it correctly. The fallback for users whose language isn't targeted.
x-default is a special hreflang value that designates a fallback page -- the version Google should show when none of your other language or region tags match the user's context.
It's one of those things that's simple in concept but easy to misuse. Here's exactly what it does, when you need it, and how to implement it.
What x-default means
Every hreflang set maps specific languages and regions to specific URLs. But what happens when a user's language isn't in your set? If you only target en, fr, and de, what does a Japanese user get?
Without x-default, Google makes its best guess from your existing variants. With x-default, you're explicitly telling Google: "if no other tag matches, send them here."
The tag looks like this:
<link rel="alternate" hreflang="x-default" href="https://example.com/" />
x-default isn't a language code -- it's a signal that this URL is the catch-all.
The two main use cases
1. A language selector or homepage
If you have a page where users choose their language, x-default is a natural fit. Instead of dumping unmatched users on an English page, you send them to a page where they can pick their own path.
<link rel="alternate" hreflang="en" href="https://example.com/en/" />
<link rel="alternate" hreflang="es" href="https://example.com/es/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />
Here, https://example.com/ is the language selection page. A Korean user goes there, not to /en/.
2. Your default language as the fallback
More commonly, x-default points to your default language version. If your site is primarily English and you have regional variants for specific markets, your English page serves as the global default:
<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="de" href="https://example.com/de/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/" />
A user in Australia gets the x-default English page since there's no en-au variant.
Generate hreflang with x-default automatically
Build complete hreflang sets with correct x-default handling for every page variant.
Is x-default required?
No. It's recommended, but Google won't penalise you for omitting it.
If you omit x-default and a user's language isn't in your hreflang set, Google will serve whichever of your variants it thinks is most appropriate. That's not ideal -- you're giving up control you could have.
Add it if you have an obvious fallback
If your site has a primary language or a language selector page, add x-default. It costs nothing and gives you explicit control over where unmatched users land.
Where x-default fits in the tag set
x-default lives alongside your other hreflang tags -- it doesn't replace them. Every page in the set still needs the full group of language/region tags plus the self-referencing tag:
<!-- On your English page -->
<link rel="canonical" href="https://example.com/en/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/" />
<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/en/" />
In this case, x-default and hreflang="en" point to the same URL. That's fine -- they serve different purposes. en targets English speakers; x-default handles everyone else.
What x-default is not
x-default does not mean "English" or "global." It means "fallback." The URL it points to can be in any language. You could point x-default to your Spanish homepage if Spanish is your primary audience. The value is the explicit fallback designation, not an implied language.
It also doesn't exempt the page it points to from needing its own complete hreflang set. If x-default points to https://example.com/, that page still needs all the hreflang tags the rest of the set has.
Audit warnings for missing x-default
Some SEO tools will flag "missing x-default" as a warning. This is a recommendation, not an error. Your hreflang implementation isn't broken without it -- you're just leaving Google to make a choice you could make yourself.
If you're seeing this warning in an audit and you don't have an obvious fallback page, either:
- Point
x-defaultto your primary language version, or - Accept the warning as a low-priority item
Don't add x-default pointing to a random page just to clear the audit warning.
Related Articles
Part of Boring Tools -- boring tools for boring jobs.
Generate perfect hreflang tags
Create and validate hreflang markup for your multilingual site. Free.