Hreflang Checker
Extract and validate hreflang tags. Check for missing x-default, duplicate values, and invalid language codes.
Hreflang is unforgiving in a way most SEO tags aren’t. Miss a closing bracket in a title tag and the page still ranks fine. Miss a single return link in an hreflang set, and Google’s own documentation is explicit about the consequence: it may disregard the entire relationship between those pages, not just the one broken link. We’ve seen this play out on a client site where the Spanish pages were live, correctly translated, and technically indexed but because they never linked back to the English versions that pointed to them, Google’s International Targeting report showed the whole cluster as unmatched. The English pages kept ranking for Spanish-language queries in Spain instead of the Spanish pages doing it.
That’s the exact kind of failure this tool is built to catch. Our free hreflang checker online tests every tag in a cluster against the actual bidirectional relationship Google requires, not just whether the syntax looks valid on one page.
What a Hreflang Tags Checker Actually Verifies
Google’s Search Central guidance lays out the rule plainly: if Page A declares an hreflang relationship to Page B, Page B has to declare one back to Page A, or the pairing gets ignored. That’s the return tag requirement, and it’s the single most common reason hreflang implementations fail silently industry audits consistently put implementation errors in the majority of multilingual sites, and missing return links are usually the top cause cited.
Beyond reciprocity, valid hreflang tags depend on correct formatting: language codes follow ISO 639-1 (lowercase, like en or es), optional region codes follow ISO 3166-1 Alpha-2 (uppercase, like US or MX), and URLs need to be absolute rather than relative. Run a page through our tool to test hreflang tags and it checks every direction of the relationship at once, flags incorrect code formatting, and confirms the target URLs actually return a 200 status instead of a redirect or error.
Where Hreflang Breaks in Practice
A handful of patterns come up repeatedly across the multilingual and multi-region sites we’ve audited:
- A new language version gets added to the site, but nobody updates the existing pages to point back to it, breaking reciprocity across the whole cluster
- Hreflang tags are declared in the HTML head while a separate sitemap also declares conflicting hreflang relationships, and the two sources disagree
- A page’s canonical tag points to a different URL than its own hreflang self-reference, which Google’s guidance treats as a conflict that undermines both signals
- No x-default tag is set, so users whose language doesn’t match any declared version get routed inconsistently instead of landing on a sensible fallback
The canonical conflict is the one we flag most often, and it’s rarely deliberate. A page canonicalizes to itself in theory, but a tracking parameter or trailing slash mismatch means the hreflang tag and canonical tag technically point to two different URL strings. Google treats that as ambiguous, and ambiguous signals tend to get deprioritized rather than resolved in your favor.
How the Checker Works
- Enter the URL of one page in the hreflang cluster
- The tool reads its hreflang declarations, then checks each linked alternate page for a matching return tag
- It validates language and region code formatting against ISO standards
- You get a clear map of the cluster, showing which relationships are confirmed and which are missing or broken
Why We Built This Alongside Our Guest Posting Services
International link-building campaigns only work if the target page is the one Google actually serves to that audience. We built this checker after watching earned links point at the “wrong” language version of a page because the hreflang cluster behind it was broken, effectively wasting the placement. It’s the same check we run before finalizing international campaigns for clients. No login, no limit on how many URLs you check in a session, and nothing stored beyond the check itself.
One honest limitation: this tool checks what’s declared in your HTML. If your hreflang setup lives in your XML sitemap or HTTP headers instead, point the checker at those directly and per Google’s own guidance, it’s best to use only one method consistently rather than mixing all three.
FAQs
What happens if a return tag is missing?
Google may ignore that hreflang relationship entirely, so the intended language version may not get served correctly.
Are hreflang codes case-sensitive?
Convention is lowercase for language and uppercase for region, though Google generally normalizes case — consistency still avoids confusion.
Do I need an x-default tag?
It’s optional but recommended, since it gives Google a fallback page for users who don’t match any declared language or region.
Run your pages through our free hreflang checker online now and confirm every version actually points back to the others.