Primary Verdict
Hreflang issues found
This cluster returned 2 fail and 2 warn issues.
fail
4 issues
Validate the cluster, not just the tag syntax.
Updated
Loading tool interface...
Primary Verdict
This cluster returned 2 fail and 2 warn issues.
fail
4 issues
Locales: 4 | Targets: 4 | Self-ref: yes | x-default: yes
HTML: 4 | Sitemap: 4 | Sitemap used: https://example.com/sitemap-locales.xml
Alternates checked: 3 | Page lang: en-US | Canonical: https://example.com/us/product
Page included: yes | Matches HTML: no | Diagnostics: 1
| en-us | html, sitemap | yes | 200 | https://example.com/us/product | self | self | healthy |
| en-gb | html, sitemap | no | 200 | https://example.com/uk/product | yes | self | 1 redirect |
| fr-fr | html | no | 200 | https://example.com/fr/produit | no | mismatch | missing return | missing self-ref | canonical mismatch |
| x-default | html, sitemap | no | 200 | https://example.com/product | yes | self | healthy |
Missing from sitemap: fr-fr -> https://example.com/fr/produit
Extra in sitemap: de-de -> https://example.com/de/produkt
Diagnostics: HTML and sitemap annotations disagree on one locale target.
Point hreflang annotations directly at the final destination instead of redirecting URLs.
Make every alternate page link back to the source page and the rest of the cluster.
Ensure each alternate page canonical points to its own final URL, not a different locale.
Sync HTML and sitemap hreflang annotations so both sources publish the same locale-to-URL set.
The Hreflang Validator + Cluster Checker fetches a live localized page, collects its alternate language annotations, and validates the full cluster. It checks self-references, return tags, canonical alignment, redirect behavior, indexability, and sitemap consistency.
Why it matters for SEO: Hreflang errors rarely live in one tag. Clusters break when alternates redirect, canonicals point at the wrong locale, return tags go missing, or HTML and sitemap annotations drift apart.
International Rollouts: Validate new locale launches before templates and sitemap changes spread errors across the site.
Migration QA: Recheck hreflang after domain moves, folder changes, or regional store consolidations.
Ongoing Maintenance: Catch return-tag drift and canonical conflicts introduced by CMS updates or localization workflows.
After validating hreflang clusters, generate missing alternates, review canonicals, and confirm sitemap coverage across every locale set.
Go beyond syntax and verify whether the full hreflang set actually works across live alternate pages.
Check whether each locale target returns 200, links back correctly, and canonicalizes to itself.
Compare on-page and sitemap annotations so international SEO drift is visible immediately.
Answers about Hreflang Validator + Cluster Checker
You can validate hreflang tags by running a live localized URL through the validator. It checks the page annotations, follows alternate targets, and verifies reciprocity, canonicals, and sitemap alignment.
The most common hreflang failures are missing self-references, missing return tags, redirecting alternates, and canonicals that point to the wrong locale. These errors often cause search engines to ignore the cluster.
Yes, hreflang pages should usually canonicalize to themselves or to the closest same-language substitute when a direct equivalent does not exist. Cross-locale canonicals often invalidate alternate targeting signals.
No, you can use either HTML or sitemap hreflang annotations, but if you publish both they must match exactly. Mixed clusters are a common source of international SEO drift.