Hreflang Tag Generator
Add a URL for each language and region you target and get the full set of hreflang link tags, including x-default, ready to paste into your pages.
Language versions
Generated output
<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="nl" href="https://example.com/nl/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />Place these in the <head> of every page in the set, and make sure each page points back (reciprocal tags).
Getting hreflang right
When you sell the same products in multiple languages or regions, hreflang tags tell Google which version belongs to which audience. Done well, a Dutch shopper sees your Dutch page and a German shopper sees the German one, instead of the wrong language ranking, or your versions competing with each other as duplicates.
The value of each hreflang is a language code (like en) or a language-region code (like en-US or nl-BE). Add x-default to nominate a fallback, usually a language picker or your global homepage, for everyone you don't explicitly target. Use real, crawlable URLs, not redirects.
The single biggest hreflang mistake is missing return tags. Annotations have to be reciprocal: if your English page references the Dutch one, the Dutch page must reference the English one back. When return tags are missing, Google quietly ignores the whole set, so generate the complete, matching cluster for every page.
Maintaining reciprocal hreflang by hand is manageable for a few pages and impossible for a growing multilingual catalog. WISEPIM translates product content and manages the language relationships behind it, so your international SEO setup stays correct automatically as you add languages and products.
That's hreflang for one page.
WISEPIM translates your product content and keeps the matching hreflang relationships correct across your whole catalog, so adding a new market doesn't mean hand-editing tags on thousands of pages.
Related free tools
See all toolsPeople also search for
Frequently asked questions
What are hreflang tags?
Hreflang tags tell search engines which language and region each version of a page is for, so the right version is shown to the right user. They prevent the wrong-language page from ranking and reduce duplicate-content issues across international or multilingual sites.
What is the x-default hreflang value?
x-default marks the fallback page to show users whose language or region you don't explicitly target, typically a language selector or your main/global version. It's optional but recommended for international sites.
Do hreflang tags need to be reciprocal?
Yes. If page A points to page B with hreflang, page B must point back to A. Missing return tags are the most common hreflang mistake and cause Google to ignore the annotations entirely. Generate the full set for every page in the cluster.
Where do hreflang tags go?
In the <head> of each page, in the HTTP header, or in your XML sitemap, pick one method and use it consistently. WISEPIM manages translated product content and the matching hreflang relationships across your whole catalog so the international setup stays correct as you add languages.
What's the correct hreflang format for language and region?
Use a two-letter ISO 639-1 language code on its own, like en or nl, or pair it with a two-letter ISO 3166-1 country code for a region, like en-US, en-GB or nl-BE. The language comes first, the region second, and the country code is never used alone. Match these values to the URLs you actually serve.
Do I need hreflang if my whole site is in one language?
No. Hreflang only applies when you have alternate versions of the same content for different languages or regions. A single-language site doesn't need it. You only need it once you target, for example, both Dutch and Belgian-Dutch, or English for the US and the UK.