Hreflang Tag Generator - International SEO Tags
What's included
Features
en, en-us, fr-ca, or deAbout this tool
Need Search Engines to Show the Right Language or Country Page?
You have equivalent pages for different languages or regions, but Google may show the wrong version if the alternate relationship is unclear. A US visitor might see the UK page, a French page might compete with an English page, or translated documentation might not connect back to the canonical source. Hreflang tags solve that mapping problem by telling search engines which URL belongs to each language or regional audience.
This Hreflang Tag Generator creates two common implementation formats: HTML <link rel="alternate" hreflang="..."> tags for the page head, and XML sitemap alternates using the required xhtml:link namespace. Add each locale and URL, include x-default when you have a global fallback, then copy or download the output.
The two output modes are built from the same underlying row list, but the sitemap format is structurally more repetitive than most people expect: because each <url> block must declare its full set of alternates on its own, the generator nests every locale's xhtml:link entry inside every single <url> block — five locales means five <url> blocks, each containing all five xhtml:link lines, not five lines total. This is exactly what the sitemap spec requires (each URL entry has to be self-describing), and it's the detail people miss when hand-editing sitemap alternates and end up with an incomplete, one-directional set.
Duplicate detection works by lower-casing every locale code and comparing the count of valid rows against the size of a Set built from those lowercased values — so en-US and en-us are correctly caught as the same duplicate value even though they're typed differently, which matters since hreflang codes are case-insensitive but easy to enter inconsistently across a large row list. The x-default check does the same lowercase comparison against the literal string x-default, so the fallback indicator stays accurate regardless of how it was capitalized when typed. Every URL and locale value passed into the output is run through an attribute-escaping step that converts &, ", <, and > into their entity equivalents, so a URL containing a query-string ampersand can't break the generated HTML or XML.
Hreflang works only when the pages form a clean alternate set. Every URL should be canonical, indexable, accessible, and equivalent in search intent. Each page should include a self-reference and reciprocal references to every other alternate. If a page redirects, uses noindex, points to a different canonical URL, or is blocked in robots.txt, the hreflang signal can fail.
Everything runs locally: the row list and generated output are held in component state and downloaded straight from a Blob URL, so your URL map and international page structure are never sent anywhere. Use this tool alongside Sitemap.xml Generator when managing alternates in XML, Meta Tag Generator to keep canonical tags aligned, and Schema Markup Generator when localized pages also need structured data for articles, products, FAQs, or local business pages.
Step by step
How to Use
- 1Add every language or regional alternateCreate one row for each equivalent page:
en,en-us,en-gb,fr,fr-ca, or any valid language-region combination. Include the current page URL too, because hreflang sets should be self-referencing as well as reciprocal. - 2Use canonical absolute URLsPaste the final HTTPS URL for each page, not a tracking URL, redirect URL, or staging URL. The alternate URLs should match canonical tags generated with Meta Tag Generator and the discovery URLs you include in Sitemap.xml Generator.
- 3Add an x-default fallbackInclude
x-defaultfor the global fallback, language selector, or default version shown when no better language or region match exists. The tool shows whether an x-default row is present because missing fallbacks are common on international SEO implementations. - 4Choose HTML tags or sitemap XMLUse HTML output when you can add link tags to each page head. Use sitemap XML output when the site has many localized pages and you prefer managing alternates in an XML sitemap with the required XHTML namespace.
- 5Fix duplicate locale warningsCheck the duplicate locale count before publishing. Each hreflang value should appear once per alternate set. Duplicate
en-usor repeated region codes can make search engines ignore or distrust the annotations. - 6Deploy reciprocally across all alternatesEvery page in the set should reference itself and all other alternates. If the English page references French and German, the French and German pages should reference English, each other, and themselves too.
- 7Validate with Search Console or crawlersAfter deployment, inspect international targeting reports, crawl the pages, or review rendered head output. Look for missing return tags, blocked alternate URLs, non-canonical alternates, noindex pages, and language codes that do not match the page content.
Real-world uses
Common Use Cases
en-us, en-gb, en-ca, and en-au when similar English pages differ by currency, shipping, spelling, legal terms, or offers. Regional hreflang keeps country-specific pages aimed at the right audience.Got questions?
Frequently Asked Questions
Create one hreflang annotation for every equivalent language or regional URL, including a self-reference for the current page. For example, an English page should list itself, the Spanish page, the French page, and any x-default fallback. This generator creates either HTML link tags for the page head or sitemap XML alternates using xhtml:link. Publish the same complete alternate set on every page in the group.
x-default identifies the fallback URL when no language or regional version is the best match for a searcher. It is commonly used for a global homepage, country selector, or default English page. You should use it when you have a page that is appropriate for unmatched users. It does not replace language-specific hreflang values; it sits alongside them as the fallback.
Both methods are valid. HTML link tags are simple for small sites where you control the page head template. XML sitemap hreflang is often easier for large sites, ecommerce catalogs, or documentation systems with many localized URLs. Choose one primary implementation method and keep it consistent. Do not let HTML and sitemap annotations disagree, because conflicting hreflang sets are difficult to debug.
Yes. Hreflang annotations should be reciprocal. If page A names page B as an alternate, page B should name page A and every other page in the same alternate set. Missing return tags are one of the most common hreflang errors. Search engines may ignore incomplete sets because they cannot confirm that the pages are intentional equivalents.
Avoid pointing hreflang at non-canonical URLs. Each hreflang URL should normally be indexable, canonical, accessible, and equivalent in content purpose to the other alternates. If an alternate URL redirects, is noindexed, is blocked by robots.txt, or canonicalizes to a different URL, the hreflang signal can fail. Align hreflang URLs with canonical tags and sitemap URLs.
en targets English-language users broadly. en-us targets English users in the United States, and en-gb targets English users in the United Kingdom. Use language-only values when the content is not region-specific. Use language-region values when pricing, spelling, shipping, legal copy, currency, or availability differs by country or region.
Yes. A complete hreflang set normally includes self-referencing tags. The Spanish page should include an es tag pointing to itself, plus tags for every other language or region in the same set. Self-references make the alternate cluster explicit and reduce ambiguity when search engines process the annotations.
Yes, if the pages are true regional alternates and serve users in different countries, even if the language is similar. For example, en-us and en-gb pages may both be English but differ in currency, shipping, spelling, taxes, or availability. Do not use hreflang just to connect loosely related pages. The pages should satisfy the same search intent for different language or regional audiences.
Common causes include missing return tags, duplicate locale values, non-canonical alternate URLs, blocked pages, noindex tags, redirects, invalid language codes, or content that is not equivalent. Google also treats hreflang as a signal, not a command. Start by crawling the alternate set and confirming that every page returns 200, is indexable, references itself, and references every other page consistently.
Usually no. Hreflang is for pages that have equivalent versions targeting different languages or regions. A single-language site does not need hreflang unless it has regional variants, such as separate US, UK, Canada, or Australia pages. If all users should see the same page, focus on canonical tags, sitemap coverage, internal linking, and regular metadata instead.