CrawlCheck

Agent view · Guides · 2026-10-02

Hreflang audit: fixing return-link and x-default errors

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/hreflang-audit-return-links-x-default-and-the-common-errors: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/hreflang-audit-return-links-x-default-and-the-common-errors>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes15,475
words2,183
sha-256e42b6927b963a7bc950808a05ff882d27d590016c69dadfdb5fa89fc8b880ef2
repr-digestsha-256=:5CtpJ7ljp7yVCAigX/iC0n1ZABbGna39tfqJ/IuIDvI=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795311492;expires=1795315092;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="J3Tg66KWmOaXQ9JLeE_cbQ";tag="crawlcheck-page"
signaturesig1=:drIIXFzINHWbbZQ0U8H6BvWhvh9M7MpvyNh51Q03qapBUban/0rTwZkqu/0adB7ev1bln1nfsfS706qKc082Bg==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Guides · 2026-10-02 · By [VSNARY | Emmanuel Orta](/author) · 6 views

# Hreflang audit: fixing return-link and x-default errors

Hreflang tells a search engine which language or regional version of a page to show. It only counts when every version links back. The rules, the six errors that make Google ignore a set, and how to audit it from the outside.

Hreflang annotations tell Google which language or regional version of a page to show a searcher. Each version must list every version in the set, including itself, with an ISO 639-1 language code and optional ISO 3166-1 region code, and every link must be returned by the page it points to or Google ignores it. x-default names the fallback for unmatched users. Each URL must be the canonical, indexable version. Annotations can go in the HTML head, HTTP headers or the XML sitemap. Bing relies mainly on the content-language meta tag and the page's own language rather than hreflang.

Check your own site free

Check my site

About a minute. First scan free with your email, nothing installed.

On this page

- The rules
- Return links are the rule that breaks most sets
- The six common errors
- Where to put the annotations
- Other search engines
- Language, region and when to use each
- Large sets belong in the sitemap
- Auditing a set from outside

Every [hreflang](/glossary/hreflang) [URL](/glossary/url) has to be the single [canonical](/glossary/canonical), indexable version of the page, and across every full scan CrawlCheck has run, 5.5% of sites serve the same homepage with a 200 on both the bare domain and the www hostname instead of redirecting one to the other.

A site that publishes the same page in several languages has to tell search engines which version belongs to which audience, or it risks the English page ranking in Germany and the German page competing with it. Hreflang is the mechanism Google uses for that. It is also one of the easiest annotations to get almost right, and almost right is ignored. This guide covers the rules, the errors that invalidate a set, and how to audit one.

## The rules #

Every version of a page carries a `link rel="alternate"` element for every version in the set, including one pointing at itself, each with an `hreflang` value and an absolute URL. Values are an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha-2 region code: `de`, `pt-BR`, `en-GB`. The special value `x-default` names the page to show users whose language matches none of the others, often a language selector or the main version. Our own homepage carries this set in its head:

```
<link rel="alternate" hreflang="en" href="https://crawlcheck.io/">
<link rel="alternate" hreflang="de" href="https://crawlcheck.io/de/">
<link rel="alternate" hreflang="fr" href="https://crawlcheck.io/fr/">
<link rel="alternate" hreflang="es" href="https://crawlcheck.io/es/">
<link rel="alternate" hreflang="pt" href="https://crawlcheck.io/pt/">
<link rel="alternate" hreflang="x-default" href="https://crawlcheck.io/">
```

Each of the four translated pages carries the identical six lines. Pages we have not translated, such as this guide, carry none, because an annotation must point at a page that exists and says the same thing in another language.

## Return links are the rule that breaks most sets #

Google only trusts an hreflang link when the page it points to links back. If the English page lists the German page but the German page does not list the English one, the pair is ignored. That rule stops a third party from claiming to be your German version. It also means one template that forgets the annotations, or one page that was translated later, quietly breaks the pairs it belongs to. A set of five versions has ten pairs, and every one must be reciprocal.

## The six common errors #

| Error | Effect | Fix |
| --- | --- | --- |
| missing return link | that pair is ignored | emit the full set from one shared template |
| no self-reference | the set may be treated as incomplete | each page lists itself too |
| invalid code (`en-UK`, `jp`, `es-LA`) | the annotation is ignored | use ISO 639-1 language and ISO 3166-1 region: `en-GB`, `ja` |
| URL is not canonical, redirects or is [noindex](/glossary/noindex) | the annotation points at a page that cannot be shown | reference the final, indexable, self-canonical URL |
| canonical points to another language | Google keeps one version and drops the others | each language version is its own canonical |
| relative URLs | resolved inconsistently | always absolute, with protocol |

The canonical conflict deserves emphasis because it is common in CMS setups: a translation plugin sets every language's canonical to the English URL, which tells Google the translations are duplicates of the English page, and Google obliges. The interaction with canonicals generally is in [the canonical URL audit](/guides/canonical-url-audit-one-page-one-address).

## Where to put the annotations #

Three places are equivalent for Google: `link` elements in the HTML head, a `Link` HTTP header (useful for PDFs), or `xhtml:link` entries inside the XML sitemap. Pick one. Using two invites them to disagree, and sitemap annotations are invisible to anyone reading the page. If the annotations are injected by JavaScript after load, many clients never see them; render them in the server HTML.

## Other search engines #

Bing has said it uses hreflang only as a weak signal and relies mainly on the `content-language` meta tag or header and the language of the page text itself. Set `lang` on the `html` element of every version to match its content, which also helps screen readers and translation tools. Yandex supports hreflang. An [answer engine](/glossary/answer-engine) reads the page it fetched, so a correct `lang` attribute is what makes that page's language unambiguous to it.

## Language, region and when to use each #

Use a language code alone unless the content really differs by country. One Spanish page for every Spanish speaker is `es`; separate pages for Spain and Mexico with different prices, spelling or legal text are `es-ES` and `es-MX`. A region code cannot be used alone: `hreflang="MX"` is invalid, because the value always starts with a language. If you publish regional variants, also consider a language-only entry pointing at the most general version, so a Spanish speaker in a country you have no variant for still gets Spanish rather than the `x-default`.

Hreflang is a hint about which version to show, not a redirect and not a guarantee. Google can still show a different version if it judges it more relevant. Do not redirect visitors automatically by IP or browser language; search crawlers mostly fetch from one country and would only ever see one version. [Offer](/glossary/offer) a visible language switcher instead, with each link marked with its own `hreflang` and `lang` attributes, as ours is.

## Large sets belong in the sitemap #

A page with twenty language versions needs twenty-one `link` elements in every head, which adds weight to every page and every template. At that size the sitemap form is easier to keep correct: each `url` entry lists its alternates as `xhtml:link` elements, generated from one table of translations, and the HTML stays clean. The same reciprocity rules apply inside the sitemap, and the sitemap must be one Google can read, which is covered in [the sitemap audit guide](/guides/xml-sitemap-audit). Whichever form you choose, generate it from data rather than writing it by hand, and audit it after every new translation, because each one adds a pair to every existing version.

## Auditing a set from outside #

Fetch each version's server HTML, extract every `hreflang` link, and build the graph. For every link from A to B, confirm B returns 200 without redirecting, is not `noindex`, is its own canonical, and links back to A. Confirm every page lists itself, every code is valid, and there is exactly one `x-default`. Then check that the `lang` attribute on each page matches its hreflang. Our [post on translating crawlcheck.io](/blog/crawlcheck-in-german-french-spanish-and-portuguese) describes how we generate the set from a single list of languages so that a new page cannot ship with a partial one.
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fhreflang-audit-return-links-x-default-and-the-common-errors%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fhreflang-audit-return-links-x-default-and-the-common-errors%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Hreflang%20audit%3A%20fixing%20return-link%20and%20x-default%20errors)[Email](mailto:?subject=Hreflang%20audit%3A%20fixing%20return-link%20and%20x-default%20errors&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fhreflang-audit-return-links-x-default-and-the-common-errors)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Related findings

[2026-10-02 IndexNow: which engines use it and how to check it worked IndexNow tells engines a URL changed. One submission reaches Bing, Yandex, Seznam, Naver, Yep and others; Google does not. Setup a](/guides/indexnow-what-it-does-who-reads-it-and-how-to-check-it-worked)[2026-09-16 Canonical URL audit: do tags, redirects and sitemap agree? Audit canonicals from the responses, not the tag: apex and www both serving, half-done aliases, template canonicals and sitemaps t](/guides/canonical-url-audit-one-page-one-address)[2026-09-30 CrawlCheck in German, French, Spanish and Portuguese CrawlCheck's main pages and every scan report now come in four more languages. What is translated, what stays English, and how the](/blog/crawlcheck-in-german-french-spanish-and-portuguese)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Registry:** [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) | **Pages:** [IP ranges](/data/ip-ranges) · [Keys](/keys) · [Continuity](/spec/continuity) · [Conduct: Ccbot](/agents/conduct/ccbot) | **Datasets:** [Problems: ARD legacy path](/datasets/problems/ard-legacy-path) | **Blog:** [Which AI crawlers the top 10,000 sites block most, October 2026](/blog/which-ai-crawlers-top-sites-block-most-october-2026) | **Glossary:** [AI visibility score](/glossary/ai-visibility-score) · [Retrieval recall](/glossary/retrieval-recall) · [RDF dataset](/glossary/rdf-dataset) · [Human-in-the-loop](/glossary/human-in-the-loop)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /guides/hreflang-audit-return-links-x-default-and-the-common-errors.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.