Hreflang x-default: When to Use It and What Happens Without It
Key Takeaways
x-defaultidentifies a URL candidate for users whose language or region does not match another declared hreflang version- The candidate can be a language-selection page, a neutral landing page, or the content page that the team chooses for unmatched users
x-defaultis optional; omitting it does not invalidate the other hreflang annotations- Declare the same complete, reciprocal cluster on every version, and choose the fallback per logical page rather than assuming one global homepage
Suppose a product page has English, French, and German URLs, but no version specifically declared for the language or region of a particular searcher. A matching x-default annotation gives Google a candidate URL for that unmatched case. Without it, Google can select among the available pages using its own systems; the result is not a promise that one particular language will be chosen.
The hreflang x-default value is therefore a fallback signal for an unmatched language or region, not a declaration that one language is the site's primary language. It can be useful on a language selector, an internationally neutral page, or a suitable version of the same content. The choice belongs to the page cluster being annotated.
Google introduced the value for international pages and documents it in the x-default guidance and the localized versions documentation.
x-default Is a Candidate URL, Not a Default Language
The value x-default does not mean “always show the English page” or “send every other country to the homepage.” It marks the URL your implementation considers suitable when no language or region annotation matches. That URL should make sense for the intent of the specific page.
| Choice | When it fits |
|---|---|
| Language-selection page | Users should choose a locale from visible links. Keep the page useful without requiring an automatic redirect. |
| Neutral landing page | The page explains the offering internationally and lets users continue to a suitable locale. |
| Content page for the same cluster | The team has chosen one localized or language-neutral version as the useful fallback for this exact product, article, or category. |
Different clusters can make different choices. Engineering recommendation: A product page can use its product-level selector, while an article can use a language-neutral article URL. There is no requirement that every cluster share one global x-default target.
Complete HTML Example
This is a complete, runnable HTML document for a product cluster. In this example, the English page is also the chosen x-default candidate. Replace the URLs with the corresponding pages in your own cluster.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Example product</title>
<link rel="canonical" href="https://example.com/en/product">
<link rel="alternate" hreflang="en" href="https://example.com/en/product">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/product">
<link rel="alternate" hreflang="de" href="https://example.com/de/product">
<link rel="alternate" hreflang="x-default" href="https://example.com/en/product">
</head>
<body>
<main>
<h1>Example product</h1>
<p>English is the selected fallback for users without a matching locale.</p>
<p>
<a href="https://example.com/fr/product">Français</a>
</p>
</main>
</body>
</html>Every localized page in this cluster should expose the same four alternate relationships, including its own language code. If the fallback is a selector page instead, point x-default to that page in every entry and describe the choice in your implementation documentation.
Keep the Cluster Complete and Reciprocal
Hreflang is a relationship between equivalent pages. The English, French, and German versions in the example each list all three versions and the same x-default target. A one-way declaration, a missing self-reference, or a URL that represents a different page makes the cluster harder to validate and can prevent Google from using the relationship as intended.
The same rule applies when the annotations live in an XML sitemap. Google supports HTML, HTTP headers, and XML sitemaps as equivalent implementation methods. See the complete XML sitemap example and validation checklist for the sitemap form.
What Happens When x-default Is Omitted?
x-default is optional. Google can still use matching language-region annotations when they exist. For a user with no matching annotation, however, your implementation has not supplied a candidate specifically for that case, so Google decides which available result to show using its own ranking and localization systems.
Adding x-default is useful when the unmatched experience matters: a language selector can give users a clear choice, while a page-level fallback can keep them on the product, article, or category they requested. The value does not guarantee a ranking position, force a redirect, or make a page indexable.
Implementation Checklist
- Choose the candidate URL for each logical page cluster. Use a selector or a suitable content page based on the user's task.
- Use a valid
x-defaultvalue exactly once per cluster and use an absolute, crawlable URL. - Include the self-reference and every alternate language or region on each page, or in each sitemap entry.
- Check bidirectionality and confirm that each URL maps to the corresponding page rather than a generic or unrelated destination.
- Keep canonical, robots, status, and redirect behavior consistent with the page you want Google to evaluate.
- When a URL changes, update every affected cluster reference and any other hreflang implementation the site maintains.
The illustrative MendMySEO demo may show hreflang evidence and guidance, but it is not an every-cluster or production-availability claim. Review the current release status.
Frequently Asked Questions
Can x-default and a language-specific hreflang point to the same URL?
Yes. A page can be both the en version and the x-default candidate when English is the useful fallback for that cluster. The two annotations describe different matching cases even though their URLs are identical.
Should x-default always point to the homepage?
No. Declare it per logical page cluster. A product page can point to its product-level selector or fallback content, and an article can point to its own suitable fallback. Sending every unmatched visitor to a homepage can discard the intent expressed by a specific search.
Can x-default point to a content page instead of a language selector?
Yes. A suitable content page can be the candidate when that is the intended experience for unmatched users. Make the choice at the cluster level and keep the URL equivalent to the product, article, category, or other page being annotated.
Does x-default control which page Google indexes?
No. It supplies a localization candidate for users without another matching annotation. It does not replace indexability controls, guarantee indexing, or force a page to rank. Keep each alternate page independently crawlable and manage indexing with the site's normal technical signals.
Is x-default required for the XML sitemap hreflang method?
No. It is optional in HTML, HTTP headers, and XML sitemaps. If you use it in a sitemap, include the same x-default link in every entry for the cluster, alongside all language alternates and the self-reference.