Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Files and configuration
  3. Hreflang Checker

Hreflang Checker

Check that your language versions declare each other correctly.

Every declared version is visited to check the actual reciprocity of the links and the validity of the codes under ISO 639-1 and ISO 3166-1. No usage limit.

What this tool is for

Hreflang tells Google that the same page exists in several languages or for several countries, so it serves the right version to the right visitor. The principle is simple; its implementation is one of the most regularly botched pieces of technical SEO.

The reason lies in a requirement written into the documentation: every page has to declare all its alternative versions, itself included. From that follows a rule you can check by eye: the declarations of all versions of one page have to be identical to one another. One missing link, and the versions describe different sets — there is no group any more, and nothing says so. The detail and the sources are in the guide on multilingual sites and hreflang.

This tool starts from one page, discovers every declared version, visits them for real, and checks that each points back to the others. It also checks the validity of the codes — a quiet and frequent source of error.

The most expensive misreading: declaring language versions when the content is identical in all of them. Translating the interface is not enough. Ten versions serving the same text are ten near-duplicate pages competing with one another.

How to read the results

Reciprocity is the decisive check. Every version has to declare all the others. The tool displays the full matrix: one empty cell is enough to invalidate the whole group.

Code validity checks conformity with the standards. The classic errors are an invented code, a country code used on its own, or eccentric capitalisation. An invalid code is simply ignored, silently.

Self-reference is often forgotten. Every page has to declare itself in its own list. Its absence is a frequent cause of invalidation.

The presence of x-default is not compulsory but is recommended. Without it, Google chooses for itself which version to serve to languages not covered.

Consistency with the canonical deserves attention. Every version has to declare itself its own canonical. A canonical pointing at another language cancels the whole arrangement.

Content similarity is flagged when two versions are too close. That is the sign of a missing translation, or of purely cosmetic localisation.

Common mistakes

Leaving out reciprocity. Error number one. It cancels everything, with no warning signal at all.

Using a country code on its own. hreflang="be" designates Belarusian, not Belgium. For Belgian French it is fr-BE. That kind of confusion produces declarations that look correct and are not.

Inventing codes. Codes have to exist in the standards. A made-up value is silently ignored, and the version concerned drops out of the group.

Declaring versions with no distinct content. Hreflang presupposes genuinely adapted versions. Without real translation, you create duplication instead of resolving it.

Redirecting automatically by browser language. A common and harmful practice: it prevents access to the other versions and disrupts crawling. Offer a visible choice instead, with no forced redirect.

Going further

Frequently asked questions

Does hreflang improve rankings?

No, it does not lift a page. It tells Google which version to serve according to the searcher’s language and country. The benefit is a better click-through rate and less bouncing, because the visitor lands on the version they understand — not a position gained.

Which language codes should I use?

The language code under ISO 639-1, optionally followed by an ISO 3166-1 alpha 2 country code: fr, fr-BE, en-US. The classic mistakes are inventing a code, using a language name instead of the code, or writing a country code on its own — a country without a language is not valid.

Do the links have to be reciprocal?

Yes, absolutely. The documentation requires every page to declare all its versions, itself included. If the French page declares the English one but the English one does not declare the French, the declaration is not reciprocal: the two pages then describe different sets, and there is no longer a pair to serve. It is the most frequent error, and nothing flags it.

What is x-default for?

To designate the version served when no other matches the searcher’s language. Typically that is a selection page, or your international version. It is not compulsory but it stops Google choosing arbitrarily.

Can I declare hreflang if my pages have the same content?

That is precisely the misreading to avoid. Hreflang presupposes genuinely adapted versions: translated, or at minimum localised in currency, contact details and legal notices. Declaring eleven versions serving the same English text creates eleven near-identical pages that Google treats as duplicate content.

Where should the declarations go?

Three possible places, never to be combined: in the HTML head, in the HTTP headers, or in the XML sitemap. HTML is the simplest to maintain; the sitemap is more economical on sites with many versions.