Skip to content
Utiloom

Hreflang Checker

Review one authored hreflang set for Google-supported language, script, region, URL, duplicate, fallback, and self-reference evidence.

LocalNo retention

Reviewed July 13, 2026

Guide, examples, and validation Show

About this tool

Validate the static mappings intended for one page without misrepresenting local syntax checks as live reciprocal-link or content verification.

Hreflang Checker reviews the static alternate mappings intended for one authored page entirely in the browser. It validates Google-oriented language, optional script, optional region, x-default, and bounded HTTP(S) URL inputs, confirms that the stated current page appears in the set, and generates escaped HTML without fetching any address.

  • Accepts Google-oriented ISO 639-1 language, optional ISO 15924 script, optional assigned ISO 3166-1 Alpha 2 region, and x-default values.
  • Rejects duplicate hreflang values and unsafe or malformed URLs while separating shared-URL, HTTP, origin, fallback, and self-reference review findings.
  • Generates escaped HTML link elements only when the current page URL and every authored mapping pass blocking validation.

How to use Hreflang Checker

Enter the exact current page URL, then add one comma-separated hreflang and alternate URL mapping per line. Resolve every blocking code, URL, length, or duplicate-value error; review self-reference, x-default, shared-target, protocol, origin, and generic-language findings; then copy the complete normalized set for deployment in the page head.

When this tool is useful

  • Review alternate language and region mappings before launching localized pages.
  • QA hreflang exports from a CMS or spreadsheet before engineering deploys them.
  • Catch duplicate locale rows or missing x-default entries during international SEO audits.

Practical tips

  • Use fully qualified URLs and include the current page itself in the alternate set.
  • Consider x-default for a selector or fallback page, but do not treat it as mandatory for every set.
  • Deploy the identical intended mapping on every localized variant and verify reciprocal links in live HTML or headers.

Examples you can test

Load an example, compare the result with the expected output, then replace it with your own input.

Audit two language alternates

Example input

en page links to ko page, ko page links back to en page

Expected output

Reciprocal hreflang relationship confirmed

Reciprocal links are required so search systems can trust the alternate-language cluster.

Find a wrong locale code

Example input

hreflang="kr"

Expected output

Warning for invalid or unexpected language-region code

Locale mistakes can prevent the intended page from appearing for regional users.

Validation checklist

  • Check that every alternate URL is absolute, crawlable, and canonical.
  • Verify reciprocal hreflang tags across all language versions.
  • Use valid language and optional region codes such as en, en-US, or ko-KR.

Frequently asked questions

What does this hreflang checker validate?

It validates one current page URL and up to 200 authored mappings for supported hreflang shape, assigned codes, absolute HTTP(S) URLs, credentials, fragments, whitespace, length, duplicate values, normalization, and current-page self-reference.

Is x-default required?

No. Google recommends considering x-default for unmatched language settings, especially on language selector or auto-redirect pages. The tool reports its absence as a review finding rather than a blocking error.

Can multiple hreflang values share one URL?

The tool preserves shared targets but asks you to review them. Sharing can be intentional, including an x-default fallback that reuses another page, so it is not treated as a syntax error.

Does the checker verify reciprocal return links?

No. It does not fetch any alternate, parse deployed HTML or headers, or verify that each live page returns the same set. Use a deployed crawler or URL audit for reciprocal-link evidence.

Which locale code format does this Google-oriented review accept?

Use a two-letter ISO 639-1 language such as en, optionally followed by an ISO 15924 script such as zh-Hant and an officially assigned two-letter region such as en-US. Use hyphens, not underscores. x-default is handled separately.

Related tools

Keep the workflow moving

Continue with tools that handle a related input, output, or validation step.

SEO

Canonical URL Checker

Compare canonical URL relationships with explicit evidence.

Local
SEO

OG Image Generator

Create and verify a 1200x630 social image locally.

Local
SEO

Redirect Rule Generator

Build reviewed exact-path redirect configurations.

Local
SEO

Slug Generator

Create a reviewed URL path segment from one title.

Local