hreflang x-default: Choose the Right Fallback URL

Choose the right x-default destination#

Google describes three practical fallback shapes in its x-default guidance:

The selector is usually the clearest choice when the site serves several regions. A default-language page can be reasonable when it is genuinely the fallback experience, but do not point every unrelated page at the homepage just to add an x-default tag.

Add x-default to the same reciprocal set#

Suppose an article has English and Traditional Chinese equivalents, with a language selector for all other visitors. Every localized page should expose the same set:

1
<link rel="alternate" hreflang="en" href="https://example.com/en/posts/widget-guide/" />
2
<link rel="alternate" hreflang="zh-Hant" href="https://example.com/posts/widget-guide/" />
3
<link rel="alternate" hreflang="x-default" href="https://example.com/language/" />

The language pages should list themselves and the other alternate URLs as well. x-default is not a language code, so it does not need a country suffix. Use fully qualified URLs and the exact hostname and trailing-slash convention that the production site serves.

If one side is missing the return set, fix that relationship before deciding whether the fallback is correct. The hreflang no-return-tags guide covers the reciprocal validation failure; x-default adds one member to the set but does not relax the reciprocity requirement.

Do not use x-default to pair independent content#

An English article can discuss the same framework as a Traditional Chinese article without being a translation. Those pages may be valuable internal links, but they do not represent the same primary article for another language audience.

For those pages, keep:

• a self-referencing canonical URL;
• the correct lang value in the document;
• an English or Traditional Chinese title and description written for that page’s query;
• no article-level hreflang or x-default unless an equivalent localized page exists.

The existing guide to independent multilingual content explains this create-versus-pair decision. Adding x-default to an unrelated page set can make a markup audit look complete while making the editorial relationship less accurate.

Verify the deployed HTML#

Inspect the source received by a crawler, not just the template or CMS data:

1
curl -fsSL 'https://example.com/en/posts/widget-guide/' \
2
  | rg 'rel="alternate"|hreflang='
3

4
curl -fsSL 'https://example.com/posts/widget-guide/' \
5
  | rg 'rel="alternate"|hreflang='

For each page in the set, check that:

1. the page lists itself;
2. every equivalent localized page appears with the intended language code;
3. the same x-default URL appears on every member;
4. all href values are absolute and return the intended final URL;
5. the canonical remains self-referencing on each localized page.

If a reverse proxy changes a hostname, strips a trailing slash, or serves a cached head, the rendered HTML is the evidence to use for the next fix. Do not infer success from a source map or a local component alone.

Keep x-default optional#

A multilingual site can have hreflang on only part of its URL set. Add x-default when it describes a real fallback for unmatched languages or regions; omit it when the site has no equivalent alternate set or when the fallback would be arbitrary.

The goal is not to maximize the number of alternate tags. The goal is to help a visitor reach the right version without claiming that independent content is a translation.

Takeaway#

Use hreflang="x-default" as a language-neutral fallback inside a complete reciprocal set. Point it to a selector or a deliberate default page, and keep independently written multilingual articles self-canonical without an artificial alternate relationship.

FAQ#