Hreflang Check

Hreflang Check is a free technical SEO tool that scans any URL you enter and reports, within seconds, whether its hreflang tags use valid language/region codes, include reciprocal return tags, and cover self-referencing and x-default. The goal is to make sure your multilingual site tells Google exactly which language to serve to which country.

The problem is widespread: in a study of 18,786 hreflang-enabled sites, 31.02% had conflicting hreflang directives, 16.04% were missing self-referencing tags, and 47.95% used no x-default (Search Engine Land / SALT.agency, 2023). This tool shows you, in one click, whether the same errors live on your page.

The tool fetches your URL and parses every <link rel="alternate" hreflang="..."> tag defined on the page (or via HTTP header / sitemap). It then audits each tag and produces a compliance report.

• Language/region code validity: Checks whether codes like en, tr, de-DE, ru-RU follow the ISO 639-1 (language) and ISO 3166-1 (country) standards, catching wrong spellings such as en-UK (the correct form is en-GB).
• Return tag (reciprocity): If page A points to B, page B must point back to A. The tool flags any broken two-way link, because Google ignores non-reciprocal hreflang tags.
• Self-referencing: Each page should carry a hreflang tag pointing to its own language; the tool warns if it is missing.
• x-default: Shows whether a fallback version is defined for users who match no specific language/country.
• Conflict and absolute-URL checks: Flags cases where multiple URLs are assigned to one language, links are relative instead of absolute, or hreflang conflicts with the canonical.

You get an off-site auditor's view of your international targeting without server access, coding, or plugin installation.

A wrong hreflang can make Google serve the wrong-language page to the wrong country, bury the correct version, and let language variants cannibalize each other. The tag fails silently: you get no error message, you just lose rankings and clicks.

The most critical scenarios are:

• Broken return tag: Google discards a hreflang tag that has no return link. So even if your Turkish and German versions technically exist, the engine may treat them as separate pages and show the wrong language.
• Invalid code: A code like en-UK or a made-up region can render the whole cluster's tag ineffective. The study found 8.91% of sites carried at least one invalid language code (Search Engine Land, 2023).
• Cannibalization: Language versions with no clear signal compete on the same query. To see this risk more broadly, scan page overlaps with the Cannibalization tool.

Google's own documentation stresses that hreflang is a signal, not a redirect; that is exactly why the signal must be consistent and reciprocal for the whole thing to work.

The four most common are broken return links, missing self-referencing, invalid language/country codes, and missing x-default. The table below summarizes how often each appeared in a large-scale study and how the tool flags them.

Source: SALT.agency, analysis of 18,786 sites, 2023.

The catch: most of these errors are invisible. The page loads, users notice nothing, and only the search signal breaks. That is why regular automated auditing is far more reliable than manual review.

It takes three steps: paste the URL, scan, read the report.

1. Enter a URL: Paste the full address of the page you want to audit (for example the English version of your homepage). On a multilingual site, testing one representative page per language is a good start.
2. Run the scan: The tool pulls the hreflang tags from the page's HTML (plus HTTP header and sitemap definitions if present) and runs the code/reciprocity checks.
3. Review the report: Valid tags are marked green, missing or broken ones red. Each warning includes the problem type and the recommended correct code.

Tip: after fixing one language version, re-scan the other languages too. Because return tags are reciprocal, fixing a single page is usually not enough; the entire cluster must stay consistent. Since the scan is repeatable, you can build a quick pre-publish check into your routine.

Use the report as a fix list to make your hreflang block symmetric and absolute-URL across all language versions. In practice, that means:

• Code fixes: If the tool flagged something like en-UK, replace it with en-GB on every relevant page. Language is lowercase, country uppercase (tr, de-DE).
• Complete the return tags: If a broken link was reported, add the return tag to the referenced page. Every page should list all languages in the cluster + itself + x-default.
• Absolute URLs: Use full https:// addresses instead of relative paths.
• Canonical alignment: The URL a hreflang points to must not conflict with that page's canonical. Verify this with Canonical Check.
• Sitemap method: With many languages, defining hreflang in the XML sitemap instead of HTML simplifies management; check your sitemap's health with the Robots & Sitemap tool.

After the fixes, run the Indexability Check to confirm the page is actually crawled and indexed, because hreflang means nothing on a page that never gets indexed.

Hreflang does not work alone; it stays healthy alongside the canonical + indexing + internal-linking trio. On an international site, all these signals must tell the same story.

Recommended audit flow:

1. Validate language signals with Hreflang Check.
2. Confirm each language version self-canonicalizes with Canonical Check.
3. Verify pages are open to Google with Indexability Check.
4. Strengthen the link architecture between language versions with the AI Internal Linking tool.
5. Track how the same content is positioned across languages with SERP Analysis.

All of these tools are free to use. If you want to build a multilingual architecture correctly from the ground up, or resolve an existing hreflang mess professionally, get in touch with our team for technical SEO support. At Sora Yazılım we manage international site architecture and indexing health end to end.

The tool pays off most on sites that serve one language to several countries, or several languages to one market: it exposes the broken signals that let the wrong version rank in the wrong country. A typical case shows how.

Picture a B2B software company publishing in five languages. The German pages are carefully translated, yet searchers in Austria and Switzerland keep landing on the English version. The team blames the content, but the cause is technical: the German pages declare hreflang toward the English version, while the English pages never link back. Because Google discards non-reciprocal tags, the German cluster simply never forms.

One scan surfaces the "missing return tag" warning, the template gets a two-line fix, and the correct language starts appearing in German-speaking markets. E-commerce sites hit a close cousin of this problem: parameterized category URLs that do not exactly match the hreflang targets quietly dissolve the cluster. In both cases no visitor ever reports the bug — only a routine scan catches it.

Google AI Overviews, ChatGPT and Perplexity usually cite a single page per answer, in the user's language; if your hreflang signals are inconsistent, the cited version may be in the wrong language — or a competitor may be cited instead of you. That makes hreflang a visibility issue, not just a targeting detail.

In a classic SERP, even a wrong-language version at least appears somewhere in the list. In AI-generated answers the model typically picks one source URL, so if your English page is what gets matched to a German question, your chance of being cited drops sharply. From a GEO (Generative Engine Optimization) standpoint, hreflang has become an infrastructure signal that decides which of your language versions gets represented in AI answers at all.

A practical companion step: give every language version complete structured data in its own language — the Schema Generator can produce per-language JSON-LD. Consistent hreflang plus language-specific schema helps AI systems read your site's language map correctly.

Success looks like this: impressions and clicks from each country concentrate on the language version you targeted at that country. Google Search Console is the most practical place to watch it happen.

• Country + page breakdown: Filter the GSC Performance report by country and check which URLs collect impressions. If German traffic still lands on English URLs, the signal has not settled yet.
• Wrong-language landings: In analytics, watch country-level landing pages; users who immediately click the language switcher are telling you something.
• CTR comparison: Once the correct version ranks in the correct market, click-through rate usually improves; hunt down country-level low-CTR pages with the CTR Opportunities tool.

Keep in mind that Search Console retired its old International Targeting report back in 2022, so GSC alone no longer surfaces hreflang errors. Periodic external scans — for example re-running this tool after every release — are the only reliable monitoring method. The target state: zero critical warnings in the scan and a stable country-to-language match in GSC.