Skip to content
SEO2026

International SEO · Google Search · hreflang

Hreflang Checker: Verify Reciprocal Links, Languages and x-default

Inspect hreflang annotations for multilingual SEO with no uploads or live requests. Paste the source HTML of one or two localized pages to find missing self-links, invalid locale tags, conflicting URLs and broken reciprocal return links.

Private browser-based checker

Hreflang diagnostics

Only rel=alternate hreflang tags in pasted HTML head sections are evaluated. The tool never contacts sites. You must supply both pages' source HTML to verify reciprocal links.

Preparing checker…

For return-link validation enter both the second URL and its HTML; without these inputs return links cannot be verified.

How to implement hreflang correctly

1. Implement correctly formatted hreflang

Include rel=alternate, hreflang and a fully qualified URL in the page head. Use uk for Ukrainian and en for English, optionally with a region such as en-GB. A standalone country code is not a valid language-region annotation.

2. Bidirectional linking is essential

If the Ukrainian page links to the English translation, the English version must link back. Google can ignore one-sided hreflang pairs. Both pages should also link to themselves. This checker covers only two provided documents, not your entire international URL cluster.

3. The role of optional x-default

x-default is an optional fallback for language settings not covered by the explicit versions. It can reference a language selector. If the two documents disagree on its destination, review whether their fallback configuration is intentional.

4. Hreflang versus canonicalization

Hreflang identifies localized versions; rel=canonical proposes the primary URL for duplicated content. Full translations generally need independent self-canonical URLs rather than canonicalizing all translations to one language. Use the Canonical Tag Checker to investigate inconsistencies.

5. HTML, HTTP Link and XML sitemap

Google supports three implementation methods. HTTP Link helps with non-HTML resources such as PDFs; XML sitemaps can simplify large multilingual sites. This workbench intentionally tests only HTML annotations; it does not silently treat missing HTML tags as proof no hreflang exists elsewhere.

6. Validate the actual multilingual pages

Check actual HTTP responses, redirects, robots.txt policies, noindex, canonicals, XML sitemaps and Search Console indexing separately. Language pages should contain genuinely localized content. This parser's findings are a source-level check, not a Google indexing verdict.

Frequently asked questions

Is hreflang mandatory for a bilingual site?

No. It is a recommended way to declare real language or regional alternatives, not a prerequisite for indexing.

Why are return links necessary?

Google expects language relationships to be bidirectional, reducing the risk of unrelated sites claiming one-sided alternate relationships.

Is x-default mandatory?

No. It helps with fallback pages but is optional.

Does hreflang override canonical?

No. They serve different purposes. Avoid cross-language canonicalization of genuinely distinct translations.

Does this tool fetch websites?

No. The checker processes locally pasted HTML. A return-link check requires source from the second URL.

Method and sources

Only rel=alternate hreflang tags in pasted HTML head sections are evaluated. The tool never contacts sites. You must supply both pages' source HTML to verify reciprocal links.

Continue technical SEO checking