We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

Crawlmind
← All learn topics

Rule site.hreflang.x-default-missing

Add an x-default hreflang fallback

site.hreflang.x-default-missing is a check in Crawlmind's site audit that grades medium-impact issues of this kind. This page explains why the rule matters and the exact fix.

Impact: mediumEffort: lowFixable: 1-click

Why it matters

The `x-default` value tells Google which URL to serve when no locale-specific variant matches the user. Without it, Google has to guess: often defaulting to whatever variant happens to rank first, which may be the wrong language for a user from an unmatched country. Adding x-default is one-line work for a real ranking benefit in international traffic.

The fix

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

Pick the x-default target intentionally:

- **A locale-neutral page**, like `/page` rendering in your primary language with no country-specific pricing or compliance copy. Best for sites with a global audience.
- **The most popular variant**, like `/en-us/page` if 60% of your traffic is US. Pragmatic when you don't have the infrastructure for a neutral page.
- **A language-selector landing page** that lets the user pick. Honest when your content is genuinely locale-specific everywhere.

Whichever you pick, include `x-default` in EVERY page's hreflang block, all pointing to the same URL.

References