Hreflang Validator
Enter a URL and we will validate every hreflang tag on the page.
Enter a URL to validate.
Hreflang validation for multilingual sites
If your site serves both Hebrew and English audiences — or any other language pair — you must define hreflang tags. These tags tell Google: "this page is in Hebrew, an equivalent English version exists at URL X." Without them, Google can serve the wrong version to the wrong audience, and over time may treat both versions as duplicate content and demote both. Our tool scans a single URL and shows every hreflang tag detected, including x-default.
When to validate
Whenever you add a new language to the site, after a change to the multilingual URL pattern, and after a domain migration. Even if you set everything correctly once, multilingual plugins can sometimes skip tags on specific pages — so validate at least 5–10 pages as a sample. Test both the homepage and an inner article, because they often have different hreflang configurations.
How to read the output
Every well-configured page should have at least 3 tags (for HE/EN): hreflang="he" pointing to the Hebrew version, hreflang="en" pointing to the English, and hreflang="x-default" pointing to the default. Every URL in the tag must be absolute (https://) — never relative. Each version must point back to its sibling — a one-way link (A→B only) invalidates the entire set. Our tool reports any inconsistency it detects.
Common hreflang mistakes
What breaks it: hreflang only in the HTTP header without HTML (different platforms read different sources); wrong language codes (he-IL instead of he, or en-US without a generic en fallback); URLs that 404 or 301 from inside the hreflang tag; missing x-default; and the same language declared on two different URLs. The tool flags each separately.
How to fix
Fix it inside your multilingual plugin (Polylang, WPML), in your sitemap, or via HTTP headers. After fixing, resubmit the sitemap to Search Console and use "Inspect URL" to force re-indexing. In Rank+ we manage hreflang automatically: when you connect a multilingual site, the platform discovers every variant, builds a unified sitemap with xhtml:link entries for each language, and keeps the tags synchronized on every post.
Cases we have seen in the wild
Example 1 — a Hebrew/English site. The English version dropped completely from US search results. The check revealed the multilingual plugin emitted hreflang tags only in sitemap.xml, but in HTML on every page only "he" was declared. Google saw the entire site as Hebrew. Example 2 — a Hebrew/Arabic store. hreflang="ar" appeared but its URL pointed to the Hebrew page instead of the Arabic one. Cause: routing bug in the theme. Example 3 — a blog whose articles were only partially translated. hreflang tags pointed to pages that did not exist. Fix: an automatic fallback to the language's root page when a translation is missing.