Meta Tag Generator
Fill four fields and copy a block of head meta tags.
Generate hreflang alternate tags for a multilingual page. Give a base URL and a list of language codes, and get the link tags plus an x-default fallback to paste in the head.
Your browser is preparing the tool. It runs 100% locally.
Enter a page URL and a comma-separated list of language codes (like en, fr, de, es), and the tool writes one rel=alternate hreflang link tag per language, plus an x-default fallback. These tell Google which language or region version to show each user. The tool builds the alternate URLs by adding a ?lang= parameter to your base URL. If your translations live at different URLs (like /fr/ or a subdomain), edit the hrefs to match. The Hreflang Tag Generator works inside your browser.
Hreflang tags map the language and region versions of a page to each other so search engines serve the right one: French speakers get the French URL, and so on. Type your base URL and the codes you support, and the tool outputs an alternate tag for each, finished with an x-default tag for everyone else.
It generates the alternate addresses as your-url?lang=fr, your-url?lang=de and so on. That suits a site that switches language by query parameter, but many sites use subdirectories, subdomains or country domains instead. On those sites, replace the hrefs with your real localized URLs before shipping.
For each code you enter, the tool writes a link element with rel alternate, the hreflang attribute set to that code, and an href pointing at your base URL with a lang query parameter appended (joined onto the existing query string if there already is one). It then adds a final tag with hreflang x-default as the catch-all version.
Language codes follow ISO 639-1 (en, fr, de), optionally with an ISO 3166-1 region (en-US, en-GB, pt-BR). The tool takes your codes as-is, so it is on you to use valid ones. Google ignores an annotation with an invalid code.
for each code: link rel=alternate hreflang=CODE href=your-URL?lang=CODE
plus: link rel=alternate hreflang=x-default href=your-URLThe ?lang=CODE href is an assumption about your URL structure. Replace it with your real localized URLs (for example /fr/ or a country domain) if they differ. Codes are used as typed; use valid ISO 639-1 (plus optional ISO 3166-1 region).
| Inputs | base URL, language codes (comma-separated) |
|---|---|
| Output | one alternate tag per code, plus x-default |
| href pattern | your-URL?lang=code (an assumption; edit to match) |
| Code format | ISO 639-1 plus optional ISO 3166-1 region |
| Placement | in the head of every language version |
| Where it runs | In your browser, nothing uploaded |
The main limit: the generated hrefs use a ?lang= query parameter on your base URL. If your translations actually live at /fr/ paths, fr. subdomains or country domains, replace each href with the real URL, or the tags will point at addresses that do not exist.
Hreflang must be reciprocal. Every page in the set has to list every version, including itself, and each target must link back. If the return tags are missing, Google ignores the annotations, so the same complete set belongs in the head of each language version, with its own self-reference.
It does not validate your codes. Use real ISO 639-1 language codes (and ISO 3166-1 regions where needed); a typo like en-UK (the correct region is GB) silently breaks that entry.
hreflang is for language and region variants of the same content, not for unrelated pages. It guides which version to show; it is not a ranking boost and it does not replace translating the page properly.
The tool generates one page's tags. You will paste a complete, matching set into each localized page, or move them to an XML sitemap or HTTP headers for large sites.
Map English, French and German versions of a page to each other.
Separate en-US from en-GB, or es-ES from es-MX, with region codes.
Give search engines a clear fallback for unmatched languages.
Produce a template of alternate tags to adapt to your real URLs.
Different URL structure? Keep the codes but swap the hrefs for your real localized URLs. Big site? Put hreflang in an XML sitemap or HTTP headers instead of the head.
Generates one alternate tag per code plus x-default; it is explicit that the ?lang= hrefs are an assumption to edit and that hreflang must be reciprocal or Google ignores it.
Fill four fields and copy a block of head meta tags.
Top words in your content and the share each one takes.
Add utm_source, utm_medium and utm_campaign to any URL.
Write the og: tags that control link previews on social apps.
See roughly how a title and description could look in Google.
schema.org JSON-LD for articles, products, FAQs and more.
It's free, needs no account, and nothing you enter is sent to a server.