Hreflang generator. Reciprocally validated.

All three work. Pick one method per page and stick to it. HTML link tags are the easiest to ship and audit visually but bloat the page head as locale count grows (20 locales = 20 link tags in every page's head). XML sitemap annotations centralize the reciprocal graph in one file, which scales best above 20 locales and avoids per-page tag drift. HTTP headers are required for non-HTML resources (PDFs, downloadable catalogs) and are rarely used on regular pages. Mixing implementations on the same URL is not forbidden but creates conflicts when tags disagree; the generator outputs all three side by side so you can pick and ship consistently.

x-default tells search engines which URL to serve when no language or region match is found for the user. It is the fallback. Use it on sites where: the default URL is a language selector or global landing page that redirects; your coverage is uneven (you have en-US and de-DE but not ja-JP, so Japanese users need a default); or you operate on a non-ccTLD and want Google to serve the international URL rather than guess. If every user's locale is covered by a specific hreflang, x-default is optional but recommended; Google treats it as a soft canonical for unmatched locales. The generator adds x-default as an optional row by default.

Every hreflang pair must be bidirectional. If the US page links to the UK page, the UK page must link back to the US page, AND both pages must list themselves. Non-reciprocal hreflang is the single most common international-SEO mistake; Google ignores the entire hreflang cluster on that URL when it detects non-reciprocity. The validator panel in the generator shows a grid of every locale pair and flags missing return links in red. Fix before shipping. On sites with 50+ locales, the reciprocal matrix becomes a 2500-cell problem that the sitemap-based output handles more reliably than per-page HTML tags.

Use language-only (en) when the content is the same across all English-speaking regions (US, UK, AU, CA all read the same page). Use language-region (en-US, en-GB, en-AU) when currency, date format, regional spelling, shipping options, or pricing differ. Shopify Markets and WooCommerce Multilingual both ship region-specific variants that warrant en-US vs en-GB differentiation. Never mix: do not put en and en-US on the same page; Google treats en-US as a subset of en and will de-duplicate incorrectly. The generator validates against ISO 639-1 language codes and ISO 3166-1 region codes.

Yes. Hreflang is the primary signal Google uses to serve region-appropriate pages in localized SERPs. John Mueller confirmed in 2024 that hreflang remains the recommended approach for international SEO, and Google's documentation continues to treat it as authoritative. What has changed is enforcement: Google is stricter about reciprocal validation now, and non-reciprocal clusters are silently ignored rather than partially honored. Bing honors hreflang. ChatGPT and Perplexity read hreflang when deciding which regional URL to cite in AI answers. Ship it correctly; the SEO benefit compounds across search and AI surfaces.

No. Every URL and locale you enter lives in memory for this browser tab only. Nothing is transmitted to a server, stored in a database, or synced. The Copy buttons put text on your clipboard; the Download buttons write local files. Close the tab and the data is gone. The tool uses localStorage to remember your last locale preset, which you can clear by wiping browser data.