hreflang present but no x-default
hreflang_no_xdefaultShort answer
The page has hreflang annotations for its language versions but none of them is x-default. x-default tells Google which version to show to users whose language or region does not match any listed version; without it Google picks one itself. This issue affects whether language versions are matched correctly. Add hreflang="x-default" pointing to the language selector page or to the version you consider the default (often the English one).
Why it matters
Without x-default, a user in a country you have no version for gets whichever version Google guesses, which can be the wrong language. Google recommends x-default whenever hreflang is used.
How Glimana detects it
The rule fires when a page has one or more hreflang entries (from HTML <link> tags, HTTP headers or the sitemap) and none of them has hreflang="x-default". The evidence shows the number of entries found.
How to fix it
Add one more link in the same place the others are declared, pointing to the fallback version. It may be the same URL as one of the language versions:
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing">
<link rel="alternate" hreflang="tr" href="https://example.com/tr/fiyatlar">
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing">
WPML and Polylang: enable "x-default" in the plugin's language/SEO settings and choose the default language. TranslatePress: Settings › Advanced › hreflang x-default.
Shopify Markets generates hreflang including x-default for the primary market; if it is missing, the theme is emitting its own hreflang block in theme.liquid. Remove the custom block or add the x-default line to it.
Add the x-default entry wherever you generate the alternates (layout template, Link header, or the sitemap's xhtml:link list), and include it in the full set on every version.
How the fix is verified
Re-crawl; the task closes when the page's hreflang set includes x-default.