How it works
- Enter a page URL and, optionally, the sitemap that holds your hreflang entries. If you leave the sitemap empty, the tool looks for one through robots.txt.
- It gathers hreflang from three sources —
<link rel="alternate" hreflang> tags, the HTTP Link header and sitemap xhtml:link entries — and records where each entry came from. - It fetches every alternate URL (up to 50, five at a time) and reads its status, redirects, noindex, canonical and its own hreflang set.
- You get a URL × language matrix, an error list and a suggested corrected hreflang block.
What it checks
- Language and region codes — validated against built-in ISO 639-1 language and ISO 3166-1 alpha-2 region lists.
x-default is accepted. Common mistakes are caught: en-UK (the tool suggests en-GB), underscores such as en_US, region-only codes and invalid codes. - Self-reference — each page should list itself in its own hreflang set.
- Return links — if page A points to page B, page B must point back to A.
- Alternate URL health — targets that redirect (3xx), fail (4xx/5xx) or carry noindex are errors.
- Canonical conflicts — when a target's canonical points elsewhere, its hreflang is ignored.
- Duplicate codes — the same language code mapped to more than one URL.
- Relative URLs — hreflang targets must be absolute.
- Source agreement — HTML, header and sitemap annotations that disagree with each other.
- Warnings — no
x-default, and hreflang sets that differ between the pages of a group.
Why it matters
Hreflang helps a search engine show a French visitor your French page and a visitor in the UK your en-GB page instead of the US version. It only works when the annotations are consistent across every page in the group: a missing return link, a redirecting alternate or a canonical pointing to another URL can cause Google to ignore the annotation. These mistakes are hard to see by hand because they span several pages and sometimes three different sources. The score is our own measure, not a Google rule: it starts at 100 and drops 15 for each error and 5 for each warning, with a floor of 0. A clean result shows the annotations are consistent; it cannot guarantee which version Google will show to a given user. Google's documentation on localized versions of a page explains the rules in full.
How to fix common problems
Start with the matrix: a cross in a cell tells you which page is missing which language, and clicking it shows the reason. Add the self-referencing entry to every page, then add the missing return links so each page lists the full set. Point hreflang at the final URL rather than a redirect, remove noindex from pages you want served, and make sure each alternate's canonical points to itself. Replace codes like en-UK or en_US with en-GB and en-US. Pick one source — HTML, header or sitemap — or keep them identical. The Hreflang Generator builds a complete, consistent set, and the Indexability Checker confirms each alternate can be indexed.
Frequently asked questions
Why does a missing return link matter?
Hreflang works as a confirmed pair. If page A lists page B as its German version but page B does not list A, Google may treat the annotation as unconfirmed and ignore it. The checker fetches every alternate and compares its hreflang set with the starting page, so missing return links show up as errors in the matrix.
Is en-UK a valid hreflang code?
No. The region part uses ISO 3166-1 alpha-2 codes, and the code for the United Kingdom is GB, so the correct value is en-GB. The checker flags en-UK and suggests the fix. It also flags underscores, as in en_US, because hreflang uses a hyphen.
Do I need an x-default entry?
It is not required, so the checker reports a missing x-default as a warning rather than an error. It is useful as the fallback for visitors whose language or region does not match any listed version, such as a language selector page or your main international page.
Can I use HTML tags and a sitemap at the same time?
You can, but the sources must agree. If the HTML lists five languages and the sitemap lists four, or they point to different URLs, the checker reports a source conflict. Keeping hreflang in one place is usually easier to maintain. The Sitemap Finder & Validator helps locate the sitemaps a site declares.
How many alternate URLs does the tool check?
It fetches up to 50 alternate URLs per run, five at a time. For each one it records the status code, any redirect, noindex, the canonical tag and that page's own hreflang set, which is what makes the return-link and consistency checks possible.
Does a perfect score mean Google will show the right version?
No. A clean result means the annotations are valid and consistent by our checks. Hreflang is a signal, and Google can still show a different version based on other factors. Each version also has to be indexed, which hreflang does not guarantee.