Hreflang Tag Generator

Builds a set of link rel="alternate" hreflang="..." tags from a list of language/region codes paired with their matching URLs, telling search engines which URL to serve for each locale of the same page.

For each row, enter a language code (and optionally a region, like en-US) and the full URL of that page's version in that language. Add more rows for additional languages, remove rows you don't need, and the generated tag block updates live below the list — copy it into the page's head.

Adding en → https://example.com/en/page and tr → https://example.com/tr/page produces two lines: one hreflang="en" tag pointing to the English URL, and one hreflang="tr" tag pointing to the Turkish URL. Add a third entry with lang x-default pointing to a language-selector or default page to cover visitors whose language doesn't match any entry.

Use an ISO 639-1 language code such as en or tr. Add an ISO 3166-1 region only when you have distinct content for that region, e.g. en-US versus en-GB — adding a region you don't actually have separate content for just adds tags without adding value.

Each language version's page should list an hreflang tag pointing to itself, not just to the other versions — search engines expect the full set of alternates to appear identically on every page in the group. The special code x-default marks the fallback URL to show when a visitor's language doesn't match any of the listed alternates, commonly a language-selector page or your default locale.

This tool only formats the tags you enter — it doesn't verify that the URLs exist, doesn't check that each target page also returns the same tags with itself included, and doesn't detect language/URL mismatches. Missing return tags on a target page are one of the most common reasons hreflang doesn't work as expected.

Tag syntax follows Google Search Central's hreflang documentation, based on IETF BCP 47 language tags. Generation happens entirely in your browser; the codes and URLs you enter are never sent to a server.