Hreflang Tag Generator

First, missing return tags: if page A lists page B as an alternate, page B must list page A back, or Google ignores the annotation entirely — this is why you paste the complete identical block on every page in the group. Second, invalid codes: en-UK instead of en-GB, jp instead of ja, or using a country code where a language code belongs. Third, relative URLs: hreflang href values must be absolute, including protocol. These three account for the large majority of hreflang failures in Semrush and Ahrefs audit data.

Only if you target different countries with separate English pages — for example example.com/us/ and example.com/uk/ with different prices, currencies, or spellings. Then en-US and en-GB annotations stop Google from treating them as duplicates and showing the wrong one. A single English site serving everyone needs no hreflang at all; do not add it ritually.

It names the fallback page for users whose language or region matches none of your alternates — a Japanese searcher when you only have English, Spanish, and German versions. It usually points to your global or English page, or to a language-selector page. It is optional in the spec but strongly recommended in practice, and this tool warns when it is missing. The x-default URL can be the same URL as one of your language rows; that is a valid and common pattern.

Functionally they are equivalent — pick one and be consistent (using both invites contradictions). Head tags are easier to template for small sites. Sitemaps win for large sites: with 30 locales, head tags add 30+ lines of markup to every page (bytes on every request), while the sitemap centralizes the mapping and is easier to regenerate from a database. Sites above a few thousand pages per locale almost always choose the sitemap route.

Yes — that is a valid pattern. A single page can serve, say, both en and en-US (one URL listed twice with different hreflang values), and the x-default typically duplicates an existing URL too. What you cannot have is the reverse: one locale pointing at two different URLs, which is the duplicate-locale warning this tool raises.

No. Hreflang is a swapping signal, not a ranking signal: when any version of the page ranks, Google swaps in the most appropriate locale version for that searcher. Rankings are shared across the group via canonical-like consolidation, but you will not rank higher just by adding hreflang — you will stop showing German users the French page, which lifts CTR and cuts pogo-sticking.