hreflang Tags Tester
Use this free hreflang tags tester to inspect the hreflang tags on any public page in seconds. Paste a URL, run the check, and review the tags it finds — no sign-up and no software to install.
Enter a page URL. Our server fetches the page, reads its hreflang alternate tags, and checks the self-reference, the x-default tag, language-region formats, duplicates, and whether the alternate pages link back. This is a fetch-and-parse check only — it is not Google Search Console validation and it does not check rankings.
How to use the hreflang checker
- Enter the full URL of the page you want to inspect, including https://.
- Run the check and wait for the tool to fetch and parse the page.
- Review the list of tags found, the self-reference result, and the x-default result.
- Check the return-tag results for the alternate pages, then fix any errors the report flags.
What this hreflang test tool checks
This tool performs a server fetch-and-parse check of the page you enter. It looks for a self-referencing hreflang tag, an x-default tag, tags in valid formats, duplicate tags, and return tags on up to 10 alternate pages.
To be clear about its limits, this is not Google Search Console validation and it is not a ranking check. It reports what is present in the fetched page at the time of the check, and it does not confirm how Google treats those tags. Fetched pages are not stored.
Why hreflang matters
When a site serves the same content in several languages or for several regions, hreflang tags tell search engines which version belongs to which audience. If you check hreflang tags regularly, you can catch missing self-references, broken return links, and conflicting language codes before they confuse search engines or send visitors to the wrong version.
Use this page to test hreflang implementation on a new launch, after a site migration, or whenever an alternate version is added. As a standalone hreflang tag checker it is best used alongside a review of your sitemaps and page templates, so that every language version stays consistent.
Related tools
Frequently asked questions
No. This tool is a fetch-and-parse check only: it reads the tags on the page you enter and reports what it finds. Google Search Console validation is a separate process that reflects how Google has actually processed your pages, so use this tester for a quick check and Search Console for confirmation of how Google sees them.
A return tag means that an alternate page links back to the original page with its own hreflang entry, completing the two-way relationship. Search engines expect this reciprocity, so a missing return tag can weaken the whole hreflang set. If one version does not link back, check its template or sitemap entry for the missing reference.
It fetches the page you enter and parses its hreflang tags, checking for a self-reference, an x-default tag, valid tag formats, and duplicates. It also follows up to 10 alternate pages to check whether they link back with return tags. The report summarises what was found and flags the problems that need fixing.
A self-referencing hreflang tag is a tag on a page that points back to that same page in its own language and region. For example, the English page should include an hreflang entry for itself as well as for its translated versions. Without it, search engines may be unsure which version is the canonical one for that audience.
An hreflang tag is a piece of HTML that tells search engines which language and regional version of a page to show to a particular audience. It is usually placed in the head of the page or in a sitemap, and it points to the equivalent page in another language or for another region. When it is set up correctly, visitors are more likely to land on the version written for them.
The x-default tag points to the fallback page shown to visitors whose language or region does not match any of your other hreflang versions. It is usually the main homepage or a language-selection page. You do not strictly need one, but it is recommended, because it gives search engines a clear default instead of leaving that choice to guesswork.
Tags are often ignored when the language or region codes are invalid, when the referenced pages are blocked or return errors, or when return tags are missing. Inconsistent sets across translations can also cause problems, as can placing tags in only one location while the sitemap says something different. Run a fresh check after each fix and correct every version, not just the one you noticed first.