Hreflang Generator
Map the language versions of one page and generate hreflang tags. Review the URLs, choose HTML, HTTP headers or XML, then download the markup for installation.
Markup
No markup generated.
Mapping
| Language | URL |
|---|
Match the pages first
Start with a single piece of content: one product, service or guide. Find its corresponding version in each language. An English buying guide and a German homepage are not a useful pair just because they belong to the same business.
A quick editorial check helps: would someone switching languages still find the answer or product they came for? If not, fix the mapping before generating tags. This is the part a code generator cannot decide for you.
Choose the codes
Enter a complete URL for each version. Use en for English generally, en-GB for English in the United Kingdom, or zh-Hant for Traditional Chinese. A region is optional; a language is not. Use GB, not UK, and avoid broad regional labels such as EU or 419.
The editor checks codes and URL syntax. It rejects repeated language codes instead of choosing a destination for you. Different codes may share a URL, but review the warning: the page needs to make sense for those audiences.
Add a fallback
The optional x-default URL gives unmatched audiences a destination. You might choose a language selector or an appropriate existing version. Do not invent another page solely to fill this field. Google’s explanation of x-default describes how the fallback can help users and URL discovery.
Use one method
HTML tags belong in the document’s <head>. HTTP Link headers can also describe non-HTML documents. XML uses sitemap entries with language alternates. Google treats these methods equally; maintaining all three adds work without an extra search benefit. Each version should reference itself and its alternates, with return references on the other pages. See Google’s implementation guidance.
This generator supplies one shared HTML block and header value. For XML, it separates the downloads by origin while preserving the full alternate set. Keep each XML file with its matching site. The ordinary Sitemap Generator is a different workflow for a broader URL list without language mapping.
Keep signals aligned
Hreflang and canonical tags do different jobs. Avoid pointing every translation’s canonical at the English page by habit. Google’s canonical guidance calls for a canonical in the same language when using hreflang, or the best substitute when that is unavailable.
Before changing production, retain the current configuration and check whether your translation plugin already owns these tags. Adding a second independent set makes later maintenance harder. This tool does not replace any existing configuration.
Check the result
After installation, inspect the actual page source, response header or published sitemap. Check more than the first page in the group. Test a translated URL, its return reference and the fallback. A preview here cannot confirm what your CMS eventually serves.
Run the Redirect Checker when a mapped address unexpectedly moves, and the SEO Checker for page-level signals. Neither generated tags nor a clean report guarantees Google indexing. Keep your URL mapping available for whoever next edits the translation.
Common questions
Does this install hreflang on my website?
No. It generates files for review. It does not edit your theme, SEO plugin, HTTP headers or live sitemap.
Can alternate pages use different domains?
Yes. HTML and header output includes the complete group. XML output is separated by origin, with all alternate references retained in each file.
Does this check my existing hreflang tags?
No. It validates the submitted mapping and generates markup. It does not fetch the pages, identify their language or confirm that return tags are installed.
Planning multilingual outreach?
For publisher research around a localized page, share its URL, language and target market. We will review the brief before you approve any outreach work.