When to Use X-Default in a Language or Region Setup

If your site has separate URLs for different languages or regions, hreflang annotations tell Google which pages are alternate versions. The value x-default identifies the fallback URL for visitors whose language or region does not match any listed version.

Use x-default when you have a useful destination for those visitors, such as a language or country selector. The annotation describes how URLs relate. It does not detect a visitor’s location or send them to another page. Google recommends considering a fallback, especially for selector pages, but does not promise a ranking or traffic increase from adding the annotation.

When an x-default fallback helps

Add x-default when a page has language or regional alternatives and some visitors will not match any of them. For example, a site with US English, UK English, and German pages could point unmatched visitors to a selector that lets them choose the version they need.

Choose a fallback that helps visitors continue toward the page they wanted. A selector for a product page should offer a way to reach the same product in another region, rather than sending every visitor to an unrelated site homepage. Google describes x-default as particularly suited to language selectors, while allowing other useful fallback pages.

You can use different fallbacks across the site. A selector might suit a page with several regional product versions, while a particular translated page might be the best available destination for another page set. In its 2022 SEO Office Hours guidance, Google says to choose the destination that helps visitors, not based on the order in which translations were produced.

If you have no meaningful fallback, leave x-default out. It does not create missing translations, map regional content, or make inaccessible pages available.

What x-default tells Google

A hreflang annotation links a page to alternate versions for different languages or regions. The language or region labels identify specific versions, such as en-US for US English or de for German. x-default identifies the fallback URL for visitors who do not match a listed alternative.

For example, a page with US English, UK English, and German versions could include this annotation for a selector:

This example shows the relationship for one page set. Each participating page should list the same alternatives, including itself, so Google can confirm the relationships. Google may ignore annotations that do not link back consistently. Its localized page documentation covers the required structure and supported ways to provide the annotations.

x-default does not mean “English,” “the main language,” or “the company’s home country.” If a general English page is itself a language alternative, label it en. Use x-default for the fallback destination outside the listed language or region choices. A site can use both, such as a general English page for English-speaking visitors and a selector for visitors who do not match a listed version.

The annotation also does not carry out language detection or redirect visitors. If your site redirects people based on a browser setting or location, that behavior comes from your site’s code or server configuration. Google’s original announcement of x-default describes the annotation as a signal about which URL to consider when no other version is a better match.

How to check an x-default setup

Check the entire set of related pages, rather than looking only at the fallback tag. Start by confirming that each URL represents a real language or regional version of the same page. Then verify that the fallback points to a live page that gives unmatched visitors a useful next step.

Next, inspect the annotations delivered on each page. Google supports HTML, HTTP headers, and XML sitemaps; choose a method you can keep consistent. For HTML, check the rendered page’s <head>. For a PDF or other non-HTML file, an HTTP header can carry the relationship. Google’s documentation says that providing annotations in several methods at once adds maintenance work without a search benefit.

Check that each annotation uses a complete URL and a valid language or language-region code. Google expects the language before the region, when you include one. A country code by itself is not a language-region label, and Google ignores certain reserved region codes, including UK.

Also check the canonical URL for each version. A canonical URL tells Google which URL to treat as the preferred version when pages are duplicates or similar. hreflang tells Google which pages are language or regional alternatives. These signals have different jobs. Google advises that a localized page’s canonical point to a page in the same language, or the closest suitable alternative when no same-language page exists. See Google’s guidance on canonical URLs before changing canonicals across language versions.

Finally, confirm that Google can reach the pages and that visitors can switch versions. A redirect based on browser language or location can interfere if it prevents users or crawlers from accessing the other URLs. Google’s multilingual and multi-regional site guidance recommends separate URLs and warns about relying on automatic redirects or content that changes according to browser settings.

Use Search Console’s URL Inspection to examine how Google sees an individual URL and investigate indexing. Search performance data shows what happened to impressions and clicks, but it does not establish that x-default caused a change.

Common failures and what the evidence supports

The most common problems involve the surrounding page relationships: a missing return link, a stale or redirected URL, a fallback that does not help visitors, or a canonical that points to a different language. These issues make the annotation inconsistent or conflict with the intended URL relationships. Check the live pages and their actual HTML, headers, or sitemap entries rather than assuming the CMS generated the intended set.

A correct annotation still does not guarantee that Google will crawl, index, or show the fallback URL. It communicates localization information; it does not replace crawl access, indexability, or useful page content. Google’s current documentation recommends considering a fallback, but the reviewed official guidance provides no measured ranking lift or traffic increase attributable to x-default. Treat it as a way to clarify page relationships and provide a relevant destination, not as a ranking fix.

The evidence here is Google’s implementation guidance, so it supports claims about Google’s documented handling. Do not assume that other search engines follow the same rules without checking their current documentation.

For AI search, Google says its AI features have no additional technical requirements or special markup beyond the fundamentals for Google Search. Pages must be indexed and eligible to appear with a snippet, and eligibility does not guarantee inclusion. Google’s AI search guidance does not identify x-default as an AI visibility advantage. Its role remains the same: describing localized alternatives and a fallback.

Key Takeaways

• Use x-default for a real fallback: Point unmatched visitors to a useful selector or other destination for that page set.
• Keep its meaning distinct: Use language or region labels for specific versions; use x-default for the fallback.
• Check every related URL: Confirm that pages list themselves and each other, the fallback works, and the annotations use valid URLs and codes.
• Treat it as localization guidance: It does not redirect visitors, guarantee indexing, or promise a ranking or AI-search gain.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com