Hreflang generator
Add each language or regional version once. Get the complete reciprocal set as HTML, an HTTP header, or XML sitemap entries.
Generated hreflang
Add at least two localized URLs.
Every localized page needs the complete set
Each language version must reference itself and every other version. The generated HTML and HTTP header output is the same complete set for every page in the group.
Google's localized page documentation also requires complete URLs and reciprocal links. One page pointing to another without a return link can be ignored.
Choose one implementation method
HTML tags, HTTP headers, and XML sitemaps are equivalent methods for Google Search. Pick the one your team can keep accurate. Maintaining the same annotations in three places creates more chances for them to drift.
Use language, script, and region codes carefully
Start with a two-letter language code such as en or fr. Add a region only when the page genuinely targets it, such as en-GB. Script values such as zh-Hant are also accepted, and x-default can point unmatched users to a language selector or fallback page.
Keep canonicals aligned with localized URLs
Each localized page normally needs a canonical that represents that same localized version. The canonical tag checker can inspect the HTML before you publish the hreflang set.
Your URLs stay in the browser
The generator validates and formats the entries in this browser tab. It does not fetch the URLs or upload the list.