Skip to content
CheckerGoogleRank Version française
  1. Home
  2. Files and configuration
  3. Hreflang Checker

Hreflang Checker

Check that your language annotations are valid — and reciprocal, which is where most fail.

Annotations are read from the page, then each declared alternative is fetched to verify that it declares the original back. Codes are validated against ISO 639-1 and ISO 3166-1. No usage limit.

What this tool is for

When the same content exists in several languages, search engines face a choice: which version to show, and whether the others are duplicates. hreflang answers both questions — these pages are translations of one another, show this one to this audience.

It is also among the easiest things in technical SEO to get subtly wrong. The annotations are invisible, no error appears anywhere, and a set that is 90 percent correct is treated exactly like one that is entirely absent. Sites run for years with hreflang that does nothing at all.

This checker verifies the three conditions that actually decide: valid codes, a self-reference on every page, and genuine reciprocity — which requires fetching each declared alternative and reading what it says back.

How to read your results

Reciprocity is the check that fails most often. Every declaration must be mutual. If your French page points to the English one and the English one says nothing, Google discards the entire group — including the parts that were correct.

The self-reference must be present on every page. A page listing its alternatives without listing itself has an incomplete set, and incomplete sets are ignored. This is a one-line fix that resolves a surprising number of cases.

The codes must exist. The language part follows ISO 639-1, the optional region part ISO 3166-1 alpha-2, and the separator is a hyphen. Case does not matter. What does matter is that po, ch and uk-for-Ukrainian are not real codes, and each appears regularly in the wild.

x-default handles everyone your declared languages do not cover. It is optional and worth having: without it, a visitor whose language you never declared gets whichever version the engine picks.

The most common mistakes

Declaring a language that does not exist as a page. An annotation pointing at a 404 invalidates the group. This happens routinely when a language section is planned before it is built, or removed without cleaning up the annotations.

Confusing language with country. en-GB and en-US both target English speakers in specific countries. If your content does not differ meaningfully between them, one en serves better than two near-identical versions competing.

Inventing codes from the country name. Polish is pl, not po. Japanese is ja, not jp. Danish is da, not dk. The intuitive guess is wrong often enough that the list is worth checking rather than recalling.

Using relative URLs. hreflang requires absolute URLs with protocol and host. A relative path is ignored, silently, with no indication anywhere.

Adding hreflang instead of fixing thin translations. Correct annotations on machine-translated pages published without review do not rescue them — Google's spam policies name unreviewed automatic translation explicitly. hreflang organises good content; it does not upgrade poor content.

Related tools

Frequently asked questions

What does reciprocity mean?

If page A declares page B as its English version, page B must declare page A as its French version. Google ignores one-directional annotations entirely — not just the missing side, but the whole group. Reciprocity is the single most common reason hreflang silently does nothing.

Must every page declare itself?

Yes. A page has to include an hreflang pointing at its own URL, alongside the alternatives. It feels redundant and it is required. A set of annotations that omits the self-reference is incomplete and treated as invalid.

What is x-default for?

It names the page to serve when no declared language matches the visitor. A language selector page is the textbook use; in practice, pointing it at your main market works better for most sites. It is optional, but without it visitors outside your declared languages get an arbitrary choice.

Which codes are valid?

ISO 639-1 for language, optionally followed by ISO 3166-1 alpha-2 for region: fr, fr-FR, fr-CA, en, en-GB. The codes are case-insensitive, so PT and pt are equally valid. What is not valid is inventing one — po for Polish is a frequent error, the correct code is pl.

Does hreflang improve rankings?

It does not raise a page's ranking. It changes which version is shown to whom, and prevents your own language versions being treated as duplicates competing against each other. The gain is showing the right page to the right visitor, which improves engagement rather than position.

Do I need hreflang for a single-language site?

No. With one version there is nothing to disambiguate, and declaring anything creates risk without benefit. Add hreflang the day a second version genuinely exists — not in anticipation of one.