Do you need hreflang x-default?
Rubric check: missing hreflang x-default (check id hreflang_no_xdefault)
It's optional, but useful. hreflang="x-default" names the page to show visitors whose language or region isn't in your hreflang set, such as a language chooser or your main version. Without it, search engines pick a fallback for you.
Why it matters for SEO
Google supports x-default and recommends it for language chooser pages and sites that redirect by location. Leaving it out isn't an error, which is why Rubric counts it as minor.
Without x-default, a searcher in a country you don't target may land on whichever version Google guesses, which isn't always the one you'd choose.
Does this matter for ChatGPT and AI Overviews?
There's no public evidence that ChatGPT or AI Overviews read hreflang. They pick pages from search indexes, which do use it to choose the right language version.
A clear fallback helps the index serve the right page to everyone else. Rubric counts this as a minor check.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: x-default is optional, but it tells search engines which version to show everyone else.
It is judged on every page Rubric scores. It is only judged on sites with more than one language.
Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 16 of 71 sites where Rubric could judge it (23%). That is 16 of 69 judged sites in Rubric's 313-site test set and 0 of 2 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 12 of its findings by hand and 2 were wrong (17%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Holdout test 5 (sites the check had never seen): 0 of 3 findings judged wrong.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- WPML adds x-default automatically; check WPML > Languages for the x-default option.
- Polylang and TranslatePress add hreflang tags; check their settings for an x-default option, or which language they treat as the default.
- View the page source and search for
x-defaultto confirm.
Shopify
Shopify Markets adds hreflang tags, including x-default, for your published languages and markets automatically. If Rubric reports it missing, check your theme's theme.liquid for custom hreflang tags that replace Shopify's, or ask your translation app's developer.
Webflow
With Webflow Localization, Webflow adds hreflang tags for each locale, including x-default, which normally points at the primary locale. If a CMS item is live in secondary locales but not the primary one, Webflow can't pick a fallback, so publish it in the primary locale too. If you translate with a third-party tool instead, check that tool's hreflang settings.
Custom code
Add one x-default line to every page in the set, pointing at the same fallback:
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/">
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/">
<link rel="alternate" hreflang="x-default" href="https://example.com/">Point it at a language chooser or your main version, and include it on every page in the set.