X-default hreflang: support a selector without forced geo redirects

Use x-default as the hreflang value for the page that serves users whose language or region does not match any other annotated version, typically a selector or global fallback page. Add it alongside your other hreflang annotations, keep the selector crawlable, and avoid automatic redirects that hide alternate URLs from Googlebot.

What does x-default actually do?

x-default is a special hreflang value that marks a fallback page for unmatched languages or regions. Google's documentation recommends considering a fallback page for unmatched languages, especially on language or country selectors or auto-redirecting home pages, and shows the pattern <link rel="alternate" href="https://example.com/" hreflang="x-default" /> (Official source).

It is not a language code. It does not target a country. It tells search engines: if no other hreflang annotation matches the user, this URL is the sensible default. That is why it fits a selector page, where the user chooses their own language or region rather than being pushed to one automatically.

Why forced geo redirects create a problem

Googlebot usually crawls from the USA and sends HTTP requests without setting Accept-Language in the request header. Google also says it does not attempt to vary the location to detect site variations (Official source). If your server redirects every US-looking request to /en-us/, the crawler may never see your other language versions through that path.

A forced redirect also removes user choice. A French speaker in the UK, a German speaker in the US, or a bilingual user in Canada may not want the version your IP database guessed. A selector page lets them decide, and x-default gives search engines a defined fallback when no annotation matches.

How do you implement x-default with a selector?

1. Create a neutral fallback URL, often the root domain or a /global/ page, that presents language and region options.
2. Add hreflang annotations for each language or regional version, including x-default pointing to the selector.
3. Make the annotations reciprocal: every version should reference the others and the x-default page.
4. Keep the selector crawlable. Do not block it in robots.txt or hide it behind JavaScript that Googlebot cannot render.
5. Avoid automatic redirects on the selector itself. If you must redirect, use a temporary redirect only when a user explicitly chooses a locale, not as a default server behavior.

Google supports HTML, HTTP headers, and sitemaps as equivalent methods for indicating alternate pages (Official source). Pick one method and manage it consistently rather than running three implementations that drift apart.

Example: a selector with x-default

Hypothetical example: a retailer sells to the UK, US, and Germany. The root URL https://example.com/ is a selector page with links to /en-gb/, /en-us/, and /de/. Each regional page includes:

<link rel="alternate" href="https://example.com/" hreflang="x-default" />
<link rel="alternate" href="https://example.com/en-gb/" hreflang="en-GB" />
<link rel="alternate" href="https://example.com/en-us/" hreflang="en-US" />
<link rel="alternate" href="https://example.com/de/" hreflang="de" />

The selector page itself carries the same set, with x-default pointing to itself. A user in France who lands on the root sees the selector and can choose. A user whose language matches de may see the German version in search results. No redirect forces a choice.

How do you verify x-default without relying on guesswork?

Use a method you can repeat:

• Inspect the rendered HTML of each version and confirm the full annotation set appears, including x-default.
• Check reciprocity: if /en-gb/ points to /de/, does /de/ point back to /en-gb/?
• Test with a crawler tool that sends no Accept-Language header, or use Google Search Console's URL Inspection to see the crawled page.
• Confirm the selector page returns 200 and is not blocked by robots.txt or a meta noindex.
• Review server logs or a redirect checker for automatic 301 or 302 responses on the selector URL.

If you use a sitemap for hreflang, validate that the sitemap includes x-default entries and that URLs match the canonical versions exactly.

What about language and region targeting beyond hreflang?

Hreflang is not the only signal. Google says it does not use hreflang or the HTML lang attribute to determine the target audience for a page (Official source). Country-code top-level domains, locale-specific subdirectories, and explicit links all contribute. A .de domain or /de/ path can reinforce German targeting, but it does not replace correct annotations.

For ecommerce sites, product pages often need the same treatment as category pages. If you are structuring product information for AI-assisted discovery, the same clarity about locale and fallback helps. See GEO for ecommerce: make products easy to understand for related product-page structure. If you are still setting up store essentials, How do you start an online store without missing the essentials? covers the foundational decisions.

What should you avoid?

• Do not use x-default as a catch-all for every unmatched language if you have a specific page for that language. It is a fallback, not a substitute for proper annotations.
• Do not redirect the selector based on IP. That can hide alternate versions from crawlers and remove user choice.
• Do not mix hreflang methods without a reason. Google treats them as equivalent, and managing three sets increases error risk.
• Do not assume x-default guarantees a specific search result. It helps Google understand your fallback preference; it is not a ranking control.

Follow-up questions

Does x-default replace the need for a language selector?

No. X-default points to the fallback page. The selector is the user-facing mechanism that lets people choose. They work together: the selector gives users control, and x-default tells search engines which page to treat as the default when no annotation matches.

Can I use x-default on every page or only the home page?

You can use it on any page that has alternate versions. The most common use is the home page or a global selector, but product or category pages with multiple locale versions can also include x-default pointing to their own fallback version. The key is consistency and reciprocity across the annotation set.