Hreflang Generator
Generate hreflang annotations for any multilingual or multi-regional site. Add language-region pairs (en-US, es-MX, ja-JP), set an x-default fallback, and the tool emits a clean block of <link rel="alternate" hreflang="..."> tags. Live validation catches invalid ISO 639 language codes, invalid ISO 3166 region codes, and the most common implementation bug: forgetting the bidirectional self-reference.
Why Hreflang is the Single Most Misimplemented Tag
Search Console reports show hreflang errors as the most common international-SEO issue by a wide margin — usually because the tags ship with bidirectional gaps (page A points to page B, but page B does not point back), invalid region codes (using "uk" for United Kingdom instead of "gb"), or missing the x-default fallback. Each error means Google ignores the whole annotation block and serves the wrong language version, which kills conversion rates in the target market. The fix is mechanical and the tool catches the errors before they ship.
How Bidirectional Validation Works
For every URL you add to the hreflang set, the generator requires every other URL to reciprocate. If you add en-US to /en/, es-MX to /es/, and the x-default to /, the output block for /en/ must reference all three; the block for /es/ must reference all three; the x-default page must reference all three. The validator warns if any URL in the set does not appear in every other URL's output — that is the bidirectional check that catches most implementation bugs. The tool also validates that the language code is in ISO 639-1 (or 639-2 for less-common languages) and the region is in ISO 3166-1 alpha-2.
Frequently Asked Questions
Do I need hreflang for every language variation?+
Only when the content is meaningfully different per region or language. A site that uses American English everywhere does not need en-US vs en-GB hreflang. A site with translated copy or region-specific pricing does.
Where should hreflang tags live — in the head or sitemap?+
Both work. For small sites with under 50 URL groups, head tags are easier to maintain. For large sites or sites with hundreds of language variants, sitemap-based hreflang scales better and avoids bloating every page's head.
What is x-default and when should I use it?+
x-default is the page Google should serve when no language match is appropriate — typically a country selector or your English homepage. Add it whenever you have hreflang annotations; it is the fallback that handles edge cases like a Brazilian user on an Italian browser.
Does hreflang affect ranking directly?+
No — it does not change which page ranks. It changes which page Google serves to a user, so the right version reaches the right market. Wrong-language pages have terrible engagement, which over time can hurt ranking signals.
Is en-uk a valid code?+
No. The correct code for United Kingdom is en-gb (ISO 3166-1 alpha-2 uses gb for Great Britain). Using en-uk is the single most common hreflang typo. The validator catches it.
Can I use hreflang without language, only region?+
No — the language tag is required, the region tag is optional. en-US is valid; just -US or just US is not.
What if I have more languages than URLs?+
Multiple language tags can point to the same URL. If your Spanish content covers Mexico, Spain, and Argentina with the same article, point es-MX, es-ES, and es-AR all to the same /es/ URL.
Does the tool fetch URLs to verify reciprocation?+
No — bidirectional validation is structural. The tool warns if the set you have configured is not internally consistent. Whether each page actually contains the tags after deploy is something you verify in Search Console or a crawl.
Built by Derek Giordano · Part of Ultimate Design Tools
Privacy Policy · Terms of Service