Tool · Validation

hreflang validator

Language targeting is one of the few places where a technically valid configuration is silently ignored. Paste the set and see what breaks.

Runs entirely in this page. Nothing is uploaded, stored or sent anywhere.

Paste your declarations

One per line · page, hreflang, target

Page URL, hreflang value, target URL — separated by spaces, tabs or commas The example above is deliberately broken: /es/ never points back at the others, and no page declares x-default.

Checks reciprocity, self-reference, x-default presence, duplicate language values and malformed language codes. It does not fetch anything — it validates the set you paste.

Common questions

What it does, and what it does not

Does it fetch my site?

No. You paste the annotations and it checks them in the browser. Nothing is fetched, uploaded or stored, and the page cannot make a network request at all.

What does it actually check?

Reciprocity, self-reference, duplicates and x-default across the cluster you paste. It does not check HTTP header or sitemap hreflang, which are separate delivery methods and need separate inspection.

Why does one missing return reference matter?

Because hreflang is reciprocal and all-or-nothing: if page A declares page B and B does not declare A, the cluster it belongs to can be disregarded. The failure is rarely one wrong page — it is a market that quietly stops being served the version written for it.

These answers describe the implementation rather than an intention: this page makes no network request of any kind, which is enforced by the site’s Content Security Policy and checkable in the source.