Free hreflang checker

Hreflang-Validator

Check any page's hreflang tags in seconds. Find invalid language codes, missing return tags, x-default gaps, and hreflang–canonical conflicts before they cost you rankings.

We read the page's HTML and follow up to 12 alternate URLs to verify return tags. Nothing is stored.

/ Altified

Stop fixing hreflang by hand

Altified generates reciprocal hreflang tags, canonicals, and multilingual sitemaps for every language automatically.

Kostenlos starten

How to validate hreflang tags

Paste the URL of any language version and run the check. The validator fetches the live HTML, so test the public URL that search engines crawl, not a local or staging address.

  • Fix errors first: invalid codes, missing return tags, and canonical conflicts stop hreflang from working.
  • Review warnings next: a missing x-default or redirects are worth cleaning up.
  • Re-test after deploying, from more than one language version.

Hreflang canonical rules in one line

Every language version needs a self-referencing canonical plus the same complete hreflang set, including itself. Canonical says which URL represents this page; hreflang says which URLs are its translations. They should never point at each other's languages.

/ FAQ

Häufig gestellte Fragen

What does this hreflang validator check?

It reads the hreflang tags in the page head, validates every language and region code, flags relative URLs, duplicate or conflicting codes, a missing self-reference or x-default, and canonical conflicts. It then loads each alternate URL to confirm it responds, links back, is indexable, and canonicalizes to itself.

What are hreflang return tags?

Hreflang must be reciprocal. If your English page lists a French alternate, the French page must list the English page too. When the return tag is missing, search engines may ignore both annotations.

Can hreflang and canonical tags conflict?

Yes. Each language version should canonicalize to itself. If the French page canonicalizes to the English page, you are telling search engines the French page is a duplicate, and its hreflang annotation is ignored.

What causes hreflang conflicts?

The most common conflicts are one language code pointing to several URLs, country codes used as language codes (such as jp instead of ja, or en-uk instead of en-gb), alternates that redirect or return errors, and pages that list a different set of language versions.

Do I need an x-default tag?

It is recommended. x-default tells search engines which page to show visitors whose language or region you do not target, often a language picker or your main language version.

Does it check hreflang in XML sitemaps or HTTP headers?

This tool checks hreflang tags in the HTML head, which is the most common implementation. If you declare hreflang in a sitemap instead, use the hreflang sitemap generator to rebuild it from a known-good set.