How does Hreflang Checker work?
This type of hreflang check is necessary for multilingual websites, online stores, SaaS projects, and other resources where the same content is published for multiple languages or countries. Hreflang checker online helps quickly identify technical discrepancies before a manual international SEO audit.
The hreflang tag checker loads a page, searches for the hreflang attribute, and analyzes the relationships between the specified versions. The check includes the hreflang values themselves, the language version URLs, the presence of reciprocal links, the correctness of the canonical URL, and the accessibility of the target pages. If one of these signals contradicts the others, the URL requires additional verification.
The logic of the analysis is consistent:
Page URL → hreflang tags → language code and region code → return links → x-default → canonical tag → HTTP status → errors found.
This procedure helps to check not just a single HTML tag, but the entire set of signals by which search engines link localized pages together.
What does the hreflang validator check?
The hreflang validator analyzes the key markup parameters that influence the correctness of a language cluster. This includes the presence of rel="alternate", code syntax, URL compliance, feedback, and the technical condition of the pages.
| Examination | Correct option | Possible problem |
|---|---|---|
| hreflang | The language or language and region code is correct. | Invalid or unsupported code |
| Return link | The alternative page links back | Missing return tag |
| x-default | Specified if necessary for a general fallback page | The required default version is missing |
| Canonical | The page links to its main URL | Canonical conflict |
| HTTP status | The target URL is accessible without errors. | 301, 302, 404, or other non-200 URL |
| Self-reference | The current page is present in the group | Self-referencing hreflang missing |
Presence of hreflang tags
Hreflang tester checks whether rel="alternate" elements are present on a page and what alternate URLs they contain. For each entry, the language or region value, the target page address, and the presence of duplicate entries are analyzed.
Correct markup should describe the actual international versions of a page. If the same language is associated with multiple conflicting URLs or a link points to an outdated address, duplicate hreflang or other implementation errors occur.
Language and regional codes
The ISO 639-1 code is typically used for the language, and the ISO 3166-1 code for the country. For example, en denotes English, while en-GB specifies the English version for the United Kingdom. The language and region are separated by a hyphen.
The en_UK entry will be incorrect: it uses an incorrect separator and an invalid country code. The hreflang validator should detect incorrect language codes and other values that search engines cannot interpret correctly.
X-default
The Hreflang x-default checker determines whether a version is specified that can be used as a general option for users without specific language or regional mapping. The x-default value is typically used for a general language selection page or a universal version of a website.
Not every structure requires this attribute, so its absence shouldn't automatically be considered a critical error. x-default should be checked in conjunction with the international page architecture and language targeting logic.
What errors does the hreflang check find?
Most problems arise not from the missing tag itself, but from inconsistencies between pages within a group. A single incorrect URL, outdated canonical, or missing return tag can disrupt the relationship between multiple versions.
Hreflang checker helps find such errors before they become major technical debt. Websites should be checked especially carefully after domain transfers, directory structure changes, or the launch of new localizations.
There is no return link
If page A specifies page B as an alternative, and B doesn't contain a backlink, a missing return tag appears. This relationship remains one-way.
The fix involves synchronizing the hreflang set on linked pages. After the change, both sides need to be re-checked.
Invalid language or region code specified
Invalid hreflang is often caused by incorrect language or country formatting. For example, the developer may use an arbitrary abbreviation instead of the standard language code.
Codes should be checked against ISO 639-1 and ISO 3166-1 standards. For a single language without geographical division, a language code is sufficient.
Duplicate hreflang values
Duplicate hreflang occurs when a single language value is assigned conflicting URLs. The search engine receives multiple candidates for the same version.
You need to determine the correct URL and remove the extra entry. You should also check to see if a duplicate is being created in both the HTML and XML Sitemap.
Self-referencing hreflang missing
Self-referencing hreflang means that the current page is included in its own set of alternatives. For example, a Ukrainian URL lists itself withuk, and related language versions.
If the current page is missing, the group may be incomplete. This correction is usually made in the general markup generation template.
Missing x-default
If a project uses a common fallback page but doesn't specify it via x-default, the hreflang x-default checker will display a warning. This warning should be checked taking into account the site's structure.
For a project without a shared version, the absence of x-default in itself doesn't indicate an error. The solution depends on user routing between languages.
Hreflang leads to a page with a redirect
It's best to direct hreflang directly to the final page, rather than to a URL that responds with a redirect. This shortens the processing chain and reduces the risk of inconsistencies after future changes.
If a redirect is detected, first find the final working URL. Then update the hreflang and check the feedback on the target page.
Hreflang leads to a 404 or other non-200 URL
A link to a deleted or unavailable page renders the corresponding language alternative useless. Such a link should be restored, replaced, or removed from the markup.
You should check not only 404 errors, but also server errors, access restrictions, and unstable responses. A working version should return a predictable HTTP status.
Hreflang URL is blocked from indexing
A noindex page may be present in the technical markup, but the search engine won't be able to use it as a regular indexable alternative. A similar problem occurs when the URL is unavailable to crawlers.
You need to check the meta robots, canonical, and crawlable URLs. Hreflang alone doesn't remove other indexing restrictions.
Relative or incorrect URLs are used
In hreflang, it's best to use a full, absolute URL with protocol and domain. This simplifies validation and eliminates dependency on the current page context.
If a relative URL is encountered, it should be replaced with an absolute one and the validation repeated. The protocol, subdomain, and final slash are checked simultaneously.
I check hreflang along with other page signals. If the language URL is specified correctly but redirects, noindex is disabled, or the canonical points to a different version, the search engine receives inconsistent data. Therefore, during an audit, I simultaneously look at hreflang, return links, canonical, HTTP status, and the indexability of all URLs within a language cluster.
How to check hreflang online?
To check hreflang online, simply enter the full URL of the desired page and run the analysis. The tool reads the available markup, compares the detected language versions, and displays parameters that require attention.
You should check the specific URL, not just the domain's homepage. Errors often occur on individual templates, categories, products, or articles, even if hreflang implementation on other pages is configured correctly.
Paste the page URL
Specify an absolute URL in the format https://example.com/uk/page/. An absolute URL reduces the risk of ambiguous processing and immediately indicates which language version is being analyzed.
If a site uses separate subdomains or domains for different countries, the address of the desired page is checked on the corresponding host. For a complete audit, it is advisable to repeat a similar check for related versions.
Run a hreflang check
Once launched, the hreflang checker retrieves the page markup and collects the alternate links it finds. The values are then compared, and the code syntax, links, canonical, and target URL availability are checked.
The result should be read as a technical report. The mere presence of a tag doesn't mean the entire group is assembled correctly, so associated checks are essential.
Check the found language versions
First, compare the list of URLs with the actual site structure. Each language version should have the expected language or region, and links shouldn't lead to outdated, closed, or redirected pages.
After that, check self-reference, x-default, return links, and canonical. If the tool shows multiple warnings for a single URL, they should be reviewed together.
Correct errors and rerun the scan
After making edits, rechecking hreflang confirms that the updated code is already accessible to search engines. This is especially useful after migrating a site, changing a URL, adding a new language, or changing templates.
If the error persists, you should check the HTML <head>, HTTP Header, or XML Sitemap, depending on where exactly the hreflang is set on the site.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history on a website builder. We built the semantic core for both cities, reworked the landing pages and built the link profile from zero. Four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and closed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
Answers to your questions
What is Hreflang Checker?
Hreflang Checker is an online checker for markup across language and regional versions of a page. The tool reads hreflang tags, compares alternate URLs, and helps find errors in code, return links, x-default, and canonical tags.
This type of analysis is useful when launching a new language, migrating a website, and conducting regular technical audits of a multilingual project.
How to check hreflang online?
To check hreflang online, enter the full page URL and run the check. The service will display the found language versions and technical parameters, which can be compared with the actual site structure.
After correcting the errors, the analysis should be repeated. This will ensure that the new markup is being delivered to users and search engine crawlers.
Should I use x-default in hreflang?
x-default is used for the default page when no specific language or regional version is defined for the user. A common example is the general country or language selection screen.
Not every website needs one. The decision depends on the project's structure and whether a real fallback page exists.
Should hreflang URLs have backlinks?
Yes, linked pages must confirm the hreflang link on both sides. If one version points to another, the reverse page must contain the corresponding entry.
Missing reciprocal links is a common hreflang error. The tags on all affected pages need to be corrected.
Can hreflang be used with canonical?
Yes, these elements are used simultaneously and serve different purposes. Hreflang describes language alternatives, while canonical defines the primary URL of a specific page.
For a typical multilingual structure, each localized version has its own canonical. Hreflang links are created between the versions.
What to do if hreflang leads through 301 or 302 redirect?
It's best to replace the redirected URL with a final URL that returns a valid response. This way, the search engine robot doesn't have to go through an additional redirect.
After replacing, check the new URL, canonical, and return link. This will prevent another conflict within the group.
Is it possible to specify one hreflang for multiple countries?
If a page is intended for all users of a specific language, a common language code, such as en, can be used. Separate regional variations are only necessary if the site actually separates versions by country.
Language and region combinations are used for different countries, such as en-US and en-GB. These should not be created unless necessary.
Does hreflang error affect page indexing?
Hreflang itself isn't an indexing directive. An error in it can disrupt proper language version matching, but a page's status is also determined by meta robots, canonical, the HTTP response, and other signals.
If a URL is simultaneously closed by noindex, redirected, or canonicalized to another page, the issue needs to be addressed comprehensively.
Where is it better to place hreflang: in HTML or sitemap.xml?
Both methods are suitable when implemented correctly. For a small site, it's often easier to maintain hreflang in HTML, while for a larger project, centralized generation via an XML Sitemap is more convenient.
The main requirement is the same URL logic, correct codes, and synchronous updating of all language versions.
Related services
Page SEO analysis
Online SEO analysis: check URLs, technical errors, meta tags, content, and key SEO factors. Get clear optimization recommendations for free.
CMS Detector / Detect a site CMS
Identify a website's CMS online by domain or URL. CMS Detector checks for engine features, popular platforms, and web technologies and displays results in seconds.
Indexability check
Check if your page is indexable by Google: robots.txt, noindex, canonical, HTTP status, and other technical indicators. Online URL indexability checker.
Google index check
Check if a URL or website page is indexed in Google. Methods include Search Console, site:, the bulk checker, and reasons why pages are not indexed.
PageSpeed / Core Web Vitals Checker
Core Web Vitals Checker and PageSpeed test online: check your site's speed, LCP, INP, CLS, and get clear optimization recommendations.
HTTP Status Checker
HTTP Status Checker by Seo-Gen: check URL response codes, redirects, and 4xx/5xx errors online. Suitable for single-page and bulk URL checking.
Redirect Checker
Online Redirect Checker: Check 301 and 302 redirects, redirect chains, HTTP codes, and final URLs. Quickly check redirects without installation.
Broken Link Checker
Broken Link Checker by Seo-Gen: Find broken and inactive links, 404 errors, and problematic URLs on your website. Online verification of internal and external links.
Robots.txt Checker
Robots.txt Checker for online robots.txt file analysis and verification. Find Allow, Disallow, and User-agent errors, and check URL accessibility for Googlebot and other search robots.
Robots Meta Checker
Meta robots Checker checks Meta Robots and X-Robots-Tag, detects noindex, nofollow, and directive conflicts. Paste the URL and check the page settings.
Correct hreflang markup should link to actual language and regional pages, use the correct codes, workable URLs, consistent canonicals, and backlinks. Checking each element individually isn't enough, as errors often lie in the links between pages.
Enter the URL into Seo-Gen's Hreflang Checker, run the hreflang check, and fix any discrepancies found. After making changes, run the analysis again to ensure the updated markup is accessible to search engines.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: Hreflang Checker – check hreflang
Hreflang and canonical: how should they work together?
The hreflang canonical checker is used to detect discrepancies between two important page signals. On a multilingual website, each version typically has its own self-canonical, and the relationship between the versions is defined via hreflang.
For example, a Ukrainian page is canonicalized to its Ukrainian URL, while an English page is canonicalized to its English URL. Both pages are listed in the hreflang group, confirming their relationship with each other.
What is hreflang used for?
Hreflang tells search engines which URLs represent alternative language or regional variations of the same content. It's used when a site publishes versions for different languages, countries, or language/country combinations.
Markup helps Google choose the most appropriate URL for a specific user. It doesn't replace the page's indexability or fix issues with robots, canonical, or HTTP response.
What is canonical used for?
The canonical URL indicates the preferred address among identical or very similar pages. It is used to consolidate duplicate signals and should match the actual structure of a specific language version.
If a canonical link leads to a different language page, the hreflang group becomes inconsistent. Therefore, the canonical tag is checked together with the hreflang, not separately.
What canonical should be on language pages?
For a typical multilingual structure, a safe scenario would be as follows: a Ukrainian page has a self-canonical to a Ukrainian URL, an English page to an English URL, and a German page to a German URL. Hreflang links are built between these URLs.
Exceptions are possible in complex projects, but they must be made deliberately. Mass canonicalization of all languages to a single URL usually prevents search engines from perceiving them as separate, indexable pages.
What hreflang and canonical conflicts should I look for?
The problem occurs when hreflang specifies one URL, while canonical declares another as the primary URL. Additionally, it's worth checking canonicals with redirects, links to non-canonical URLs, and different variations of the same URL with slashes, parameters, or protocol.
When is hreflang needed?
Hreflang is needed for websites where a single topic or commercial page exists in multiple localized versions. These are most often multilingual projects, international stores, SaaS services, educational platforms, and corporate websites.
If pages differ only in language or target region, proper markup helps tie them together into a coherent group. For a single-language site without regional copies, hreflang is usually not required.
The site operates in several languages.
For a website with Ukrainian, English, and German versions, each page can contain links to the corresponding translations. This gives search engines a clear map of the international versions.
Links must be symmetrical and maintained as new pages are added. A template error can affect an entire section of the site.
One language is used for different countries
A single language can be divided by region, for example, en-US and en-GB. This is useful when prices, delivery terms, product selection, or other information differ for specific countries.
If regional differentiation is not necessary, the general language code en can be retained. Creating country-specific variants without any real difference between pages is not recommended.
The same content is located on different domains or subdomains
Hreflang can link pages across directories, subdomains, and individual domains. The technical implementation remains the same: each version must link to the others using valid absolute URLs.
For different domains, it's especially important to check return links and the availability of all URLs. Configuration errors often go unnoticed when manually reviewing a single version.
Where can hreflang be specified?
Hreflang can be implemented in several supported ways. For standard HTML pages, <link> elements within the <head> element are most commonly used, but for some projects, it's more convenient to pass links via HTTP Header or XML Sitemap.
Avoid duplicating the same schema in multiple places unless necessary. The more complex the generation system, the higher the risk of getting different sets of URLs in the HTML and sitemap.
In the HTML code of the page
Example entry:
<link rel="alternate" hreflang="uk" href="https://example.com/uk/" />
This code is placed within the HTML <head>. For each available version, a separate entry is added with the corresponding language or region.
In the HTTP header
HTTP Headers can be used for resources where regular HTML code is unavailable or difficult to modify. The principle remains the same: specify an alternate URL and the corresponding hreflang values.
When auditing, this option should be checked at the server response level. Simply viewing the HTML source will not be sufficient.
In XML Sitemap
An XML sitemap can contain information about language alternatives for website pages. This approach is convenient for large projects where the markup is centrally generated along with the sitemap.
Whenever the URL changes, it's important to update the sitemap accordingly. Outdated links within the sitemap create the same errors as outdated HTML markup.
How to interpret the hreflang analysis result?
The verification result should be considered in conjunction with the site's architecture. Even completely valid syntax doesn't confirm that the correct URL has been selected for a specific language or region.
First, obvious technical errors are corrected, then the page grouping logic is checked. After changes, the hreflang validator is re-run.
No errors found
If the hreflang validator finds no errors, the checked tags, codes, and links are technically consistent. This is a good result for a particular URL.
However, there may be separate issues with indexing, content, or site structure. These are checked using other technical audit tools.
Warnings found
A warning doesn't always indicate a critical error. For example, the absence of x-default may be acceptable for a project that doesn't have a common fallback version.
Each message should be compared to the actual site structure. There's no need to automatically fix everything without checking the page's purpose.
Conflicting URLs found
If hreflang analysis reveals a conflict, the final URL, canonical, HTTP status, and indexability are checked first. Then, the alternatives are compared across all related pages.
Most often, the cause is an outdated address, an incomplete template, or an unsynchronized update of language versions.
Why is correct hreflang important for international SEO?
Correct hreflang helps search engines understand which version of a page is intended for a specific language or region. This makes it more likely for users to see the appropriate localized page in international search results.
Markup doesn't guarantee ranking gains and doesn't replace other technical requirements. For stable performance, pages must be accessible, indexable, have consistent canonicals, and have correct internal links.
Return links and reciprocal hreflang
Pages within the same hreflang group must confirm their relationship with each other. If page A specifies page B as an alternative, page B must have a corresponding backlink to page A.
A missing return link disrupts the integrity of a group. Therefore, check hreflang tags includes a check for reciprocal links and helps identify URLs where markup is present only on one side.
Canonical URL
Hreflang and canonical tags serve different purposes. Hreflang links language or regional versions, while the canonical tag identifies the primary address of a specific page among similar or duplicate URLs.
The hreflang canonical checker helps spot conflicts when, for example, a Ukrainian page is included in a hreflang group, but its canonical points to the English version. In this situation, the search engine signals diverge.
HTTP statuses hreflang URLs
Each URL specified in the hreflang should lead to a working page. Under normal circumstances, the target page returns a 200 status, is crawlable, and does not require an intermediate redirect.
If the hreflang leads to a 301 redirect, 302 redirect, 404 error, or other non-200 URL, it's best to check the address and replace it with the final working page. This way, the markup remains straightforward and understandable for search engines.