Quick answer: International SEO helps websites serve audiences across languages and countries. Hreflang identifies equivalent localized URLs so Google can select an appropriate version in search results. It requires valid language codes and reciprocal annotations, but does not translate content, determine its language, guarantee rankings, or replace canonicalization.
Key facts
- Hreflang identifies localized alternatives; Google does not use it to detect page language. Tell Google about localized versions of your page
- HTML links, HTTP headers, and XML sitemaps are equivalent implementation methods. Tell Google about localized versions of your page
- Each version must reference itself and its alternates; relationships without return links are ignored. Tell Google about localized versions of your page
- A region code alone is not a valid hreflang value. Tell Google about localized versions of your page
- Use x-default to identify a fallback for unsupported languages or regions. How x-default can help you
TL;DR: Map equivalent localized pages, publish consistent reciprocal hreflang annotations through one maintainable method, and audit both implementation and country-level search outcomes.
- International SEO
- Optimizing a website to reach audiences across languages and countries with appropriate localized content.
- Hreflang
- An annotation identifying the language and optional regional audience of an equivalent alternate URL.
- Hreflang cluster
- A group of equivalent localized URLs connected through self-referencing and reciprocal annotations.
- x-default
- A special hreflang value identifying the fallback URL for audiences not matched by specified languages or regions.

What are international SEO and hreflang?
International SEO helps a website serve people across languages and countries. Hreflang links versions of the same page for different audiences. It helps Google choose a suitable language or regional URL. Google does not use it to detect the page’s language, as its documentation explains.
International SEO and hreflang have distinct roles. International SEO covers how you plan and serve local content. Hreflang shows how those pages relate to each other. It does not translate or adapt the content.
| Site type | What it serves | Example |
|---|---|---|
| Multilingual | Different languages | A product page in English and French |
| Multiregional | Different markets | US and UK pages with local prices |
A site can be both. A language tells you how a reader communicates. A market tells you which country or region a page serves. A hreflang cluster groups versions of the same page—not every page in the same language.
Crawling and indexing are how search engines find pages and store information about them.
This guide covers URL planning, hreflang setup, common errors, and checks. It is not a full guide to translation or technical SEO.
When does hreflang help an international website?
Use hreflang when you have matching pages in different languages or regional versions of one language. It helps Google choose a URL suited to the reader’s language or market, according to Google Search Central.
| Use case | Example | Reader need |
|---|---|---|
| Translated pages | The same guide in English and Spanish | A guide in a suitable language |
| Regional pages | French product pages for France and Canada | Local prices, stock, and shipping details |
What makes regional versions useful?
Each version should serve the same core purpose while meeting local needs. Prices, units, examples, and cultural context may differ. A product page might show local stock. A guide might use familiar terms and measurements.
Hreflang is not a promise of higher rankings or lower bounce rates.
Market-specific keyword research helps you find the terms local readers use. Those terms may differ even within a shared language.
Content localization and optimization should make each version accurate and useful. Review the content whether a person or a machine made the first translation.
Plan equivalent URLs and user-controlled language selection
Start with a map of matching pages. Then give visitors a clear way to choose their language and region.
- Build a locale map. For each page, record its content ID, audience, URL, matching versions, and any fallback. A shared product or article ID helps you connect pages whose translated names differ.
- Map pages, not whole sites. Group the US, UK, and French pages for the same jacket. Do not use a different product or a locale homepage to fill a missing translation.
- Use separate URLs. Google recommends a distinct URL for each language. Avoid changing one URL’s language based only on cookies or browser settings. See Google’s guidance. You can use domains, subdomains, or folders; compare them in the guide to URL structure.
- Let visitors choose. Add clear links to matching language versions. Name the region when it matters. Google recommends these links and advises against automatic language-based redirects in its international site guidance. If a version is missing, say so. For redirect setup, see redirects and broken links.
Choose valid language, region, script, and fallback values
A hreflang value names a language. It can also include a region or writing system. Google supports ISO 639-1 language codes, ISO 3166-1 Alpha-2 region codes, and ISO 15924 script codes. A region alone is not valid. See Google’s code rules.
| Value | Meaning |
|---|---|
| en | English, with no region specified |
| en-US | English for the United States |
| en-GB | English for the United Kingdom |
| fr-FR | French for France |
| fr-CA | French for Canada |
| zh-Hant | Chinese in the Traditional script |
- Start with the language. Use a language-only value when a page serves speakers across countries.
- Add a region when needed. Use it for pages with local prices, stock, or terms. Use en-GB, not en-UK. Use en-US for US English, not US alone.
- Add a script when relevant. A script is a writing system, not a market. Folder names need not match the codes: a /uk/ path can use en-GB.
x-default is an optional fallback for languages or regions you do not serve. It can point to a language selector or a default content page, as Google explains. It need not point to English content or the site root.
Keyword-to-page mapping assigns search terms to pages. Keep that task separate from choosing language and region codes.
How do you implement reciprocal hreflang annotations?
Reciprocal means the links go both ways. Each page must list itself and its matching versions. Those versions must link back. Google ignores relationships without return links, according to its hreflang guidance.
Choose a maintainable method
You can use HTML head links, HTTP Link headers, or XML sitemap entries. Google treats these methods as equal. Using all of them adds no Search benefit, as Google Search Central explains. Choose the method your team can keep up to date.
Generate the complete HTML set
Build the links from your locale map. Place them in each page’s HTML head. In this example, add every line below to every URL shown. That includes the product’s language selector.
| HTML example: one link per row |
|---|
| <link rel=”alternate” hreflang=”en-US” href=”https://example.com/us/products/widget”> |
| <link rel=”alternate” hreflang=”en-GB” href=”https://example.com/gb/products/widget”> |
| <link rel=”alternate” hreflang=”fr-FR” href=”https://example.com/fr/products/widget”> |
| <link rel=”alternate” hreflang=”x-default” href=”https://example.com/choose/widget”> |
The US page lists itself and the French page. The French page links back to the US page. Both use the full set.
For the fallback’s role, see the value guide above. All alternate URLs must include HTTP or HTTPS. They may use different domains, according to Google’s URL rules.
Use headers or sitemap annotations
HTTP Link headers are an option for files such as PDF manuals. For the English and French manuals below, send the same complete header with each file. The table separates the header parts for clarity. Join the values with a comma in one Link header.
| Header part | Example |
|---|---|
| Name | Link: |
| English value | <https://example.com/en/widget.pdf>; rel=”alternate”; hreflang=”en” |
| French value | <https://example.com/fr/widget.pdf>; rel=”alternate”; hreflang=”fr” |
XML sitemaps list site URLs. If you use them for hreflang, give each URL entry the full set of matching versions, including itself. This follows the same return-link rule.
Common mistakes: conflicting signals and mismatched alternates
Check both the hreflang labels and the pages they point to. A valid label is not enough if it leads to the wrong content.
Check annotations and target URLs
- Missing links. Check each group against the self-link and return-link rules above.
- Wrong codes or labels. Use the value guide above. Make sure each label matches the page’s language and audience.
- Conflicting groups. Check whether the same locale points to different URLs across the group. A URL may serve both a language value and x-default when it is also the default content page; see Google’s fallback guidance.
- Unsuitable targets. Flag redirects, missing pages, and pages that cannot be indexed. Review indexability and noindex before keeping those targets.
Check canonical alignment
Hreflang does not replace canonicalization. A canonical identifies the preferred page among duplicate pages. When you use hreflang, Google recommends a canonical in the same language. If none exists, use the best available substitute language. See Google’s canonical guidance.
Google treats localized versions as duplicate content only when their main content stays untranslated, according to Google Search Central.
Do not point every genuine translation’s canonical to the source-language page. Review duplicate regional pages in the same language separately. A noncanonical URL calls for review; it is not always an error.
How can you validate hreflang and measure localized visibility?
Check your live hreflang setup against the locale map. Then track which URLs appear in each market. Traffic changes alone do not prove that hreflang caused a change.
Audit whole hreflang clusters
Check the whole group, not just one page. Use a crawler that can read your chosen method across all the domains involved. Inspect the HTML head, HTTP headers, or sitemap entries.
- Content: Confirm that each page covers the same product or topic for its stated audience.
- Codes and URLs: Apply the code and full-URL rules above.
- Links: Check for self-links and return links across the full group.
- Fallback: If you use x-default, check that it leads to the intended selector or default page.
- Targets: Open the URLs and review their canonical choices using the guidance above.
These checks follow Google’s hreflang rules, its x-default guidance, and its canonical guidance.
Measure localized visibility
Define which page you expect to appear in each market. Compare that plan with the URLs shown in your search data. Where your data allows, compare impressions and clicks by country and page over similar periods. Keep a log of content, URL, and site changes that could affect the trend.
Use market-specific rank tracking to look for wrong-locale URLs. Do not assume that a user’s country tells you their language. Treat visibility data as a signal to investigate, not proof that Google accepted every hreflang link.
For related reporting guidance, see the Google Search Console guide.
Recheck affected groups after a translation, URL change, or locale launch. Make this part of your technical SEO audit.
Frequently asked questions
Does the HTML lang attribute replace hreflang?
No. The HTML lang attribute states the document’s language. Hreflang links matching pages for different languages or regions. Google does not use hreflang to detect the page’s language, as its documentation explains.
What should you do when a product or article has no translation in one target language?
Leave that language out of the group. Keep the links for the versions that exist. Do not fill the gap with an unrelated homepage or category page. An x-default fallback can point to a selector or default content page, as Google explains, but it does not create a translation.
Can you add a new language version without rebuilding every existing hreflang cluster?
Yes. Update only the groups affected by the new pages. Add each new URL to its matching versions, and make sure it links back. Keep each page’s self-link. Google ignores relationships without return links, according to its hreflang guidance.