What you’ll need
A public page URL, sitemap URL, or saved HTML/XML.
Check language annotations, target responses and return links.
Free to use · No saved inputsA public page URL, sitemap URL, or saved HTML/XML. New here? Start with “Try an example”.
A public page URL, sitemap URL, or saved HTML/XML.
Extract HTML, HTTP Link-header or sitemap annotations and check locale codes, self references and supplied/fetched returns.
Up to ten alternate targets per run. Missing or unreachable evidence stays unknown.
Your translated pages exist, but the language annotations may point to missing pages or fail to connect back. This hreflang checker inspects the relationships around a page or supplied sitemap. Use it after adding a locale, moving translated URLs or changing an international template. It helps you find the specific annotation that needs review instead of rebuilding every language link.
Choose a live page, sitemap or saved markup as the evidence source. Use a page with known translations so you can judge whether the extracted cluster is complete.
Run the check and review locale codes, self references and alternate URLs. For live checks, inspect the available target and return-link evidence.
Correct invalid codes or broken relationships in the source template. Rerun the original page and a translated counterpart to check the repair.
A failed return reference is a specific relationship to investigate. An unreachable target is unknown evidence, not proof that an annotation is absent. Live alternate checks are bounded, so a large language family may require more than one inspection. The tool does not assess translation quality.
Use Hreflang Generator & Checker when you need to rebuild complete annotation clusters from a spreadsheet.
Up to ten alternate targets per run. Missing or unreachable evidence stays unknown.
If page A declares page B as an alternate, the corresponding annotations should connect the language versions consistently. Review both sides of the relationship rather than assuming one tag completes the setup.
No. It checks supplied or fetched annotations and responses. Search appearance also depends on other signals, and this tool does not inspect Google’s chosen result for every searcher.