How do I check if my hreflang tags are correct?

Use BehindTheSearch's free Hreflang Tag Checker tool. Enter any URL to instantly check for missing self-referencing tags, invalid locale codes, duplicate hreflang values, relative URLs, x-default absence, and HTTP vs HTTPS conflicts. You can also crawl your entire website to audit hreflang across all pages.

What is a hreflang return tag?

A hreflang return tag means that if Page A references Page B in its hreflang tags, then Page B must also reference Page A in its own hreflang tags. This bidirectional confirmation is required for Google to trust the hreflang relationship. Our hreflang checker tool validates return-tag consistency across your crawled pages.

What does x-default mean in hreflang?

The hreflang x-default value designates a fallback page for users whose language or region does not match any of your specified hreflang locales. For example, hreflang="x-default" typically points to a language selector page or your most universally applicable version. Adding x-default is considered best practice for all multilingual websites.

Do hreflang tags affect SEO?

Hreflang tags do not directly affect rankings but are critical for international SEO. Correct hreflang implementation ensures Google serves the right language or regional page to the right users, reducing bounce rates, improving engagement signals, and preventing your different language versions from competing against each other in the same market.

What are the most common hreflang errors?

The most common hreflang errors are: (1) missing self-referencing hreflang tag, (2) missing return tags on referenced pages, (3) invalid BCP-47 locale codes, (4) duplicate hreflang values for the same locale, (5) relative URLs instead of absolute URLs, (6) HTTP hrefs on HTTPS pages, and (7) absence of x-default. Our free hreflang validator checks for all of these automatically.

Free Hreflang Tag Checker | International SEO Validator

Hreflang Tag
Checker Free

Instantly validate hreflang tags on any single URL, or crawl your entire website to find missing self-references, invalid locale codes, broken return tags, x-default gaps, HTTP conflicts, and duplicate hreflang issues. Free hreflang tester. No login. Instant results.

Single URL hreflang validation

Full site crawl up to 50 pages

Return-tag consistency check

8 hreflang checks per page

🌎

Locale Validator

BCP-47 code verification

🔁

Return-Tag Check

Bidirectional link validation

🚩

x-default Check

Fallback locale detection

📄

CSV Export

Team-ready results export

🌎

What Is a Hreflang Tag? (Complete Explanation for SEO)

A hreflang tag is an HTML link element attribute that tells Google and other search engines which language and geographic region a specific page is intended for. It is placed in the <head> section of a page as a <link rel="alternate" hreflang="language-region" href="URL"> element.

Hreflang Tag Syntax and Format

The correct hreflang tag syntax uses BCP-47 language codes. The language portion is a two or three letter ISO 639-1 code (e.g. en, fr, de, zh). The optional region portion is a two-letter ISO 3166-1 Alpha-2 country code (e.g. GB, US, IN). They are joined with a hyphen.

<!-- English for all regions -->
<link rel="alternate" hreflang="en"    href="https://example.com/en/" />
<!-- English for United Kingdom -->
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/" />
<!-- French for France -->
<link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/" />
<!-- Fallback for all others -->
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Where Can Hreflang Tags Be Placed?

Google supports hreflang implementation in three locations: in the HTML head as link elements (most common), in the HTTP header as Link response headers (useful for PDFs and non-HTML files), and in an XML sitemap using the xhtml:link attribute inside each <url> block. All three methods are equally valid. Our hreflang validator checks the HTML head implementation.

What Is the Difference Between Hreflang and Canonical?

A canonical tag tells Google which URL is the preferred version when duplicate or near-duplicate content exists. A hreflang tag tells Google which language and regional version of a page to serve to which users. They serve different purposes and are often used together on multilingual sites. A page can have both a canonical tag and hreflang tags simultaneously without conflict, as long as the canonical on each alternate page points to itself and not to the primary language version.

📈

Why Hreflang Tags Matter for International SEO

Hreflang tags are the single most important technical signal for international SEO. Without correct hreflang implementation, your multilingual website will face serious ranking and user experience problems in every market you target.

Prevents Wrong Language Version Appearing in Search

Without hreflang tags, Google may serve your English page to a French user or your US-targeted page to a UK audience. This results in high bounce rates, poor engagement signals, and lower rankings for your regional pages. Correct hreflang tells Google precisely which version to show to each user based on their browser language and geographic location.

Prevents Duplicate Content Penalties Across Language Versions

When you have multiple language versions of the same page, Google could interpret them as duplicate content without hreflang guidance. Properly implemented hreflang signals to Google that these are intentional regional or language alternates of the same content, eliminating duplicate content risk across your entire multilingual site architecture.

Improves Crawl Efficiency for Large Multilingual Sites

Hreflang tags help Google's crawler understand the full scope of your language alternate network, allowing it to crawl and index all regional versions more efficiently. Without hreflang, Googlebot may miss or deprioritise some language versions during crawl budget allocation.

Direct Impact on Search Visibility by Country and Language

Correct hreflang implementation is directly linked to your site's visibility in Google's country-specific search indexes. For example, a properly tagged en-IN page will be more likely to rank on Google.co.in for Indian users searching in English than an untagged equivalent. This is why a free hreflang checker tool is an essential part of any international SEO audit workflow.

⚠️

The 8 Most Common Hreflang Errors and How to Fix Them

Our hreflang tag checker automatically detects all eight of the most damaging hreflang errors. Here is what each one means and how to fix it.

Error 1: Missing Self-Referencing Hreflang Tag

Every page that implements hreflang must include a tag pointing to itself. For example, your English UK page at https://example.com/en-gb/ must include <link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/">. Without the self-reference, Google ignores all hreflang tags on that page. This is the most common hreflang error found by our validator.

Error 2: Missing Return Tags

If Page A links to Page B in its hreflang tags, Page B must also link back to Page A. This bidirectional confirmation is required for Google to trust the hreflang relationship. If the return tag is missing on Page B, Google treats the entire hreflang cluster as incorrectly implemented and may ignore it. Our crawl mode checks return-tag consistency across all crawled pages simultaneously.

Error 3: Invalid BCP-47 Locale Codes

Using incorrect language codes like en_US (underscore instead of hyphen), english, or non-existent codes like uk (correct is uk for Ukrainian or en-GB for English United Kingdom) will cause Google to ignore those hreflang tags entirely. Always use standard BCP-47 codes. Our hreflang validator checks every locale code against the BCP-47 standard automatically.

Error 4: Duplicate Hreflang Values

Having two or more hreflang tags with the same hreflang attribute value on the same page (e.g., two hreflang="en-US" tags) causes Google to ignore all duplicate entries. Check your CMS plugins and theme headers carefully as these often add duplicate hreflang tags when combined with manual implementation.

Error 5: Relative URLs in Hreflang Href

Hreflang tags must always use absolute URLs including the full protocol, domain, and path. Using relative URLs like href="/en-gb/" instead of href="https://example.com/en-gb/" causes the hreflang tag to be invalid and ignored by Google.

Error 6: HTTP URLs on HTTPS Pages

If your site uses HTTPS but your hreflang href values point to HTTP URLs, Google will treat those as conflicting signals. Always use HTTPS URLs in hreflang tags on HTTPS pages. This commonly occurs after an HTTP-to-HTTPS migration where hreflang tags are not updated.

Error 7: No x-default Tag

The hreflang="x-default" tag designates a fallback page for users whose language or region does not match any of your specified locales. While not strictly mandatory, Google recommends it as best practice. It typically points to a language selector page or your main international landing page.

Error 8: Noindex Combined with Hreflang

If a page has a noindex meta robots tag combined with hreflang tags, the page will be excluded from Google's index. This can break the hreflang return-link chain for pages that reference it as an alternate. Never apply noindex to a page that is referenced by other pages' hreflang tags.

🔧

Hreflang Implementation Methods and When to Use Each

Google supports three valid methods for implementing hreflang tags. The right choice depends on your site architecture, CMS capabilities, and whether you need to apply hreflang to non-HTML files like PDFs.

Method	Best For	Pros	Cons
HTML Head	Standard HTML pages	Easy to manage; visible in source	Adds HTML overhead; can slow large pages
HTTP Header	PDFs and non-HTML	Works on any file type	Requires server config access
XML Sitemap	Very large sites	Centralised; no page-level changes	Sitemap must be kept updated; crawl delay

Hreflang in WordPress and Popular CMS Platforms

In WordPress, hreflang tags are typically managed by plugins such as Yoast SEO (with the multilingual addon), WPML, or Polylang. These plugins generate hreflang tags automatically based on your configured language relationships. Common issues include plugins generating both HTML head hreflang and sitemap hreflang simultaneously, which can create duplication errors detectable by our hreflang tester.

Hreflang for Subdirectory, Subdomain, and ccTLD Structures

Hreflang works identically across all URL structures. For subdirectories (example.com/fr/), subdomains (fr.example.com), and ccTLDs (example.fr), the same bidirectional return-tag requirement applies. Cross-domain hreflang implementations using ccTLDs are slightly harder to validate because return tags live on separate domains, which is exactly why a hreflang checker that can crawl across domains is valuable for international SEO audits.

How to Test Hreflang Tags After Implementation

After implementing or updating hreflang tags, use our free hreflang tag checker above to validate every page instantly. Also check Google Search Console under Enhancements then International Targeting for hreflang errors reported by Google. Allow 48 to 72 hours after implementation before checking Search Console, as Googlebot needs time to re-crawl and process the updated tags across your full multilingual site.

🔭

Advanced Hreflang: Sitemaps, JavaScript, and Large-Scale Validation

For complex international sites with hundreds or thousands of language alternates, understanding how hreflang behaves at scale is critical for avoiding errors that are difficult to diagnose without a proper hreflang audit tool.

Hreflang in XML Sitemaps: Correct Format

When implementing hreflang via XML sitemap, each <url> block must include <xhtml:link> elements for all language alternates including itself. Every URL in the hreflang cluster must have its own <url> block in the sitemap, and every block must list all alternates. The sitemap must declare the xmlns:xhtml namespace. Mistakes in this format are a common source of hreflang errors that go undetected for months.

Hreflang and JavaScript-Rendered Pages

If your hreflang tags are injected by JavaScript after the initial HTML response, Googlebot may not process them during the first crawl wave. This is a significant issue for React, Vue, and Angular applications that render the HTML head client-side. Use server-side rendering (SSR) or static generation for hreflang tag output. Our hreflang checker tool reads the initial HTML response, which accurately reflects what Googlebot sees in its first-pass crawl before JavaScript rendering.

Hreflang Checker vs Google Search Console: Which to Trust?

Google Search Console's International Targeting report shows hreflang errors that Google has actually encountered during its crawl. Our free hreflang tag checker tool proactively scans your live pages before Google crawls them, giving you the ability to find and fix errors before they appear in Search Console. Use both tools together: our checker for proactive validation, and Search Console for confirming Google has processed your hreflang implementation correctly after you push fixes live.

How Many Hreflang Tags Can a Page Have?

There is no official Google limit on the number of hreflang tags a page can have. However, pages with very large hreflang clusters (50+ alternates) can experience performance issues if all tags are placed in the HTML head. For sites with more than 20 language alternates, the XML sitemap implementation method is generally recommended over the HTML head approach for better page load performance and easier centralised management.

Hreflang for Ecommerce and Product Pages

Ecommerce sites with thousands of product pages across multiple regions face the greatest hreflang implementation challenges. Each product page in each language must have correct return tags pointing to all other language versions of the same product. Even a single missing return tag on one product breaks the entire hreflang cluster for that product across all regions. Use our crawl mode regularly after any product catalog update to catch newly introduced hreflang errors before they impact your international search visibility.

Hreflang TagChecker Free

How the Hreflang Tag Checker Validates Your International SEO

Enter URL

Fetch & Parse

8 Checks Run

Return-Tag Audit

Scored Report

Complete Guide to Hreflang Tags, Errors, and Best Practices