--- title: "Hreflang Tags in Nuxt" description: "Set hreflang tags in Nuxt to tell search engines which language version to show users. Avoid duplicate content penalties across multilingual sites." canonical_url: "https://nuxtseo.com/learn-seo/nuxt/routes-and-rendering/i18n" last_updated: "2025-12-17" --- Hreflang tags tell search engines which language version of your page to show users. Without them, Google might show your French content to English speakers or rank the wrong regional version, creating [duplicate content](/learn-seo/nuxt/controlling-crawlers/duplicate-content) issues across languages. ```html ``` [Google recommends hreflang](https://developers.google.com/search/docs/specialty/international/localized-versions) when you have: - Same content in different languages - Regional variations (en-US vs en-GB) - Partial translations mixed with original language Hreflang is a signal, not a directive. Search engines can ignore it if they think a different version better matches user intent. ## Quick Reference ```ts [useHead] useHead({ link: [ { rel: 'alternate', hreflang: 'en', href: 'https://example.com/en' }, { rel: 'alternate', hreflang: 'fr', href: 'https://example.com/fr' }, { rel: 'alternate', hreflang: 'x-default', href: 'https://example.com/en' } ] }) ``` ## Hreflang Format Hreflang values use [ISO 639-1 language codes](https://www.linguise.com/blog/guide/list-of-the-hreflang-language-codes-how-to-implement-them/) and optional [ISO 3166-1 Alpha-2 region codes](https://hreflang.org/what-is-a-valid-hreflang/):
Format Example Use Case
Language only en English content for all regions
Language + region en-US English for United States
Language + region en-GB English for United Kingdom
Special fallback x-default Default for unmatched languages/regions
Language codes must be lowercase. Region codes must be uppercase. Separate with hyphen: `en-US`. ### Common Examples ```text en English (all regions) fr French (all regions) es Spanish (all regions) en-US English for USA en-GB English for UK fr-CA French for Canada es-MX Spanish for Mexico zh-CN Simplified Chinese (China) zh-TW Traditional Chinese (Taiwan) ``` ### Region Codes Are Tricky [UK is Ukraine](https://www.weglot.com/blog/hreflang-language-codes), not United Kingdom. Use `GB` for Great Britain. [Chinese uses zh-CN/zh-TW or zh-Hans/zh-Hant](https://www.seroundtable.com/google-iso-3166-1-for-hreflang-24663.html) for simplified/traditional variants since ISO 639-1 only defines one `zh` code. ## Manual Implementation If you're not using @nuxtjs/i18n, set hreflang manually with `useHead()`: ```vue ``` ### Creating a Composable Extract hreflang logic into `composables/useHreflang.ts`: ```ts // composables/useHreflang.ts - auto-imported in Nuxt export function useHreflang(locales: string[]) { const route = useRoute() const links = computed(() => { const baseUrl = 'https://example.com' return [ ...locales.map(locale => ({ rel: 'alternate', hreflang: locale, href: `${baseUrl}/${locale}${route.path}` })), { rel: 'alternate', hreflang: 'x-default', href: `${baseUrl}/${locales[0]}${route.path}` } ] }) useHead({ link: links }) } ``` Use it in pages: ```vue ``` ## Automatic Implementation with @nuxtjs/i18n The [@nuxtjs/i18n](https://i18n.nuxtjs.org/) module automatically generates hreflang tags for all configured locales. Nuxt handles return links, self-referential tags, and x-default automatically. ```ts // nuxt.config.ts export default defineNuxtConfig({ modules: ['@nuxtjs/i18n'], i18n: { locales: [ { code: 'en', iso: 'en-US', file: 'en.json' }, { code: 'fr', iso: 'fr-FR', file: 'fr.json' }, { code: 'de', iso: 'de-DE', file: 'de.json' } ], defaultLocale: 'en', strategy: 'prefix', // URLs like /en, /fr, /de // SEO features baseUrl: 'https://example.com', detectBrowserLanguage: { useCookie: true, cookieKey: 'i18n_redirected', redirectOn: 'root' } } }) ``` Nuxt automatically generates: ```html ``` ### URL Strategies The i18n module supports different URL patterns:
Strategy Example Notes
prefix /en/about , /fr/about Default locale also gets prefix
prefix_except_default /about , /fr/about Default locale has no prefix
prefix_and_default /about , /en/about , /fr/about Both work for default
no_prefix /about Locale in cookie/domain only
```ts // nuxt.config.ts export default defineNuxtConfig({ i18n: { strategy: 'prefix_except_default', // /about (en), /fr/about defaultLocale: 'en' } }) ``` ### Domain-Based Locales For sites with different domains per language: ```ts // nuxt.config.ts export default defineNuxtConfig({ i18n: { locales: [ { code: 'en', iso: 'en-US', domain: 'example.com' }, { code: 'fr', iso: 'fr-FR', domain: 'example.fr' }, { code: 'de', iso: 'de-DE', domain: 'example.de' } ], strategy: 'no_prefix', differentDomains: true } }) ``` Generates: ```html ``` ## X-Default Tag The `x-default` hreflang provides a fallback URL when no language matches the user's preferences. [Google recommends x-default](https://www.weglot.com/guides/hreflang-tag) for all hreflang clusters. ```html ``` ### When to Use X-Default Set x-default to: - Your primary language version - A language selector page - The most universally understood language version ```ts // Point x-default to language selector useHead({ link: [ { rel: 'alternate', hreflang: 'en-US', href: 'https://example.com/en-us' }, { rel: 'alternate', hreflang: 'en-GB', href: 'https://example.com/en-gb' }, { rel: 'alternate', hreflang: 'fr-FR', href: 'https://example.com/fr-fr' }, { rel: 'alternate', hreflang: 'x-default', href: 'https://example.com/choose-language' } ] }) ``` [According to Victorious](https://developers.google.com/search/docs/specialty/international/localized-versions#x-default), x-default improves user experience by routing unmatched users to an appropriate fallback instead of a random language version. ## Hreflang Rules ### 1. Bidirectional Links (Return Links) Every page referenced in hreflang must link back. If page A links to page B, page B must link to page A. [This is the most common hreflang error](https://developers.google.com/search/docs/specialty/international/localized-versions). ```html ``` ### 2. Self-Referential Links Each page must include a hreflang tag pointing to itself: ```html ``` ### 3. Use Canonical URLs Only All hreflang URLs must: - Return HTTP 200 status - Be indexable (no `noindex`) - Not be blocked by robots.txt - Point to canonical URLs (not redirects) [According to I Love SEO](https://developers.google.com/search/docs/specialty/international/localized-versions), using non-200, non-indexable, or non-canonical URLs is the root cause of most hreflang mistakes. ```vue ``` ### 4. Canonical vs Hreflang Canonical tags and hreflang serve different purposes. Don't use canonical to point between language versions. [that signals duplicate content](https://developers.google.com/search/docs/specialty/international/localized-versions), not translations. ```html ``` ```html ``` ## Implementation Methods You can implement hreflang using HTML `` tags, HTTP headers, or XML sitemaps. [Best practice is to choose one method](https://backlinko.com/hreflang-tag) and stick to it. Mixing methods creates conflicting signals. ### HTML Link Tags (Recommended) Most flexible approach. Set per-page using `useHead()`: ```vue ``` ### HTTP Headers Useful for non-HTML resources (PDFs, etc.). Configure in server routes: ```ts // server/routes/document.pdf.get.ts export default defineEventHandler((event) => { setHeader(event, 'Link', [ '; rel="alternate"; hreflang="en"', '; rel="alternate"; hreflang="fr"', '; rel="alternate"; hreflang="x-default"' ].join(', ')) return sendStream(event, createReadStream('/path/to/document.pdf')) }) ``` ### XML Sitemap The [@nuxtjs/sitemap](https://nuxtseo.com/sitemap) module automatically generates hreflang annotations in sitemaps when used with @nuxtjs/i18n: ```ts // nuxt.config.ts export default defineNuxtConfig({ modules: ['@nuxtjs/sitemap', '@nuxtjs/i18n'], sitemap: { // Sitemap automatically includes hreflang from i18n config } }) ``` Generates: ```xml https://example.com/en https://example.com/fr ``` ## Common Mistakes ### Missing Return Links ```html ``` ### Non-Canonical URLs ```html ``` ### Noindex Pages ```html ``` All pages in hreflang cluster must be indexable. Remove `noindex` or remove the page from hreflang annotations. ### Blocked by Robots.txt If a URL is blocked in `robots.txt`, crawlers can't access it to validate hreflang links. Ensure all alternate URLs are crawlable. ### Mixing with Canonical ```html ``` ## Testing Hreflang ### Manual Inspection View page source and verify: - All alternate links are present - Self-referential link exists - x-default is set - All URLs return 200 - All URLs are canonical (not redirects) ### Google Search Console After implementing hreflang, check [Google Search Console](https://search.google.com/search-console) > International Targeting for errors: - Missing return tags - Incorrect language codes - Invalid URLs ### Third-Party Tools - [Hreflang Tags Testing Tool](https://hreflang.org) - [Merkle Hreflang Checker](https://technicalseo.com/tools/hreflang/) - Search Console reports ## Full Example: Multilingual Nuxt App Complete implementation with @nuxtjs/i18n: ```ts // nuxt.config.ts export default defineNuxtConfig({ modules: ['@nuxtjs/i18n'], i18n: { locales: [ { code: 'en', iso: 'en-US', file: 'en.json' }, { code: 'fr', iso: 'fr-FR', file: 'fr.json' }, { code: 'de', iso: 'de-DE', file: 'de.json' }, { code: 'es', iso: 'es-ES', file: 'es.json' } ], defaultLocale: 'en', strategy: 'prefix', langDir: 'locales', baseUrl: 'https://example.com', detectBrowserLanguage: { useCookie: true, cookieKey: 'i18n_redirected', redirectOn: 'root' } } }) ``` ```json // locales/en.json { "home": { "title": "Welcome", "description": "Welcome to our site" } } ``` ```json // locales/fr.json { "home": { "title": "Bienvenue", "description": "Bienvenue sur notre site" } } ``` ```vue ``` Nuxt automatically generates hreflang tags for `/en`, `/fr`, `/de`, `/es` versions of every page.