Hreflang Checker
Review language alternatives in a page’s initial HTML without crawling alternate pages.
Inspect a public website
Analyze URL sends the submitted URL, including its query parameters, to the WebToolspire API. The API checks public DNS and requests the target without your browser cookies or authorization. Do not submit secret URLs.
One URL, an eight-second server deadline, and at most five redirects. Remote HTML is limited to 128 KiB; JavaScript is not executed.
Understand your results
For international content teams reviewing HTML language alternatives.
The checker extracts HTML link rel=alternate annotations with hreflang from one initial source response. It screens language/region syntax and recognized labels, detects duplicate or conflicting values, resolves relative links, and checks for a self-reference. It does not fetch alternates or verify their return links.
How to use this tool
- Enter the public URL of one localized page.
- Analyze the initial source and inspect the annotation table and warnings.
- Check reciprocal annotations separately on the referenced pages and ensure the intended localized versions are indexable.
What the observations mean
The report inspects language-region annotations in one HTML source, including duplicate codes, invalid values, x-default, and a possible self-reference. It does not fetch alternate pages or establish reciprocal links.
Worked example
Review language alternatives authored in one public page’s initial head.
<link rel="alternate" hreflang="en" href="https://example.com/en/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/">For source containing these links, the report lists English and French alternatives. Review the source page’s own language URL and confirm each alternate’s return annotations independently.
Limits and processing
The API reads one bounded HTML document without crawling alternate pages. It cannot establish reciprocal annotations, translation quality, rendered tags, sitemap annotations or Google’s selected language result.
Common problems and practical fixes
- Invalid language value
- Use the intended supported language and optional region code, not an invented country-only language label.
- Duplicate language destinations
- Check whether one language code points to conflicting URLs in the same document.
- Alternates not recognized
- Inspect reciprocal annotations, canonical alignment, and final response URLs on the other pages separately.
Best practices
Use real language alternatives with matching content and preserve a clear canonical strategy. Source inspection does not verify translation quality or search-engine selection.
Practical tips
- Use x-default for an appropriate language-selection or fallback destination.
- Language-region labels use a hyphen; en_US is not the expected hreflang form.
- JavaScript-inserted, HTTP-header, and sitemap hreflang annotations are outside this HTML-only check.
Frequently asked questions
Practical answers for using the Hreflang Checker.
Are return links verified?
No. The report explicitly marks reciprocal verification as not performed; no alternate pages are fetched.
Does a valid-looking tag prove international SEO is correct?
No. Syntax screening does not verify content language, canonical selection, indexing, or full language-registry compliance.
Why is a self-reference useful?
A localized page commonly includes itself in the same alternate set. Missing self-reference is a review observation, not a definitive ranking diagnosis.