Multilingual and multi-region sites: how Google's hreflang annotations work
Review Google's hreflang methods, language codes and return-link rules for multilingual and multi-region websites.
If your site has pages in more than one language, or the same language for more than one country, you can tell Google which page is which. The tool for this is called hreflang. This article summarises Google's own page on it, as read on 15 November 2026 (the page says it was last updated 2026-09-21). It covers Google Search only. Read the page before you implement anything.
When Google recommends using it
Google says it may find alternate language versions on its own, but it is usually best to indicate them explicitly. It names three situations where doing so is recommended:
- you keep the main content in one language and translate only the template (navigation, footer), as forums often do;
- you have small regional variations of similar content in one language, for example English for the US, GB and Ireland;
- your content is fully translated into several languages, for example German and English versions of every page.
The page says localized versions are only treated as duplicates if the main content of the page stays untranslated.
Three ways to say it, all equivalent
Google lists HTML link elements in the page head, an HTTP Link header (useful for files such as PDFs), and an XML sitemap. It says the three are equivalent from Google's point of view. You may use more than one, but there is no benefit in Search and it can be harder to manage, so pick one.
Two things the page says directly: Google does not use hreflang or the HTML lang attribute to detect a page's language, because it determines language with its own algorithms; and the language or country text in a subdomain such as "en-gb" is not used to work out the target audience, so you have to map the audience explicitly.
Rules that apply to every method
- Each language version must list itself and all the other versions.
- Alternate URLs must be fully qualified, including https, and may be on different domains.
- If two pages do not point to each other, the annotations are ignored. Google says this stops someone on another site from naming itself as your alternate.
- If a full set of two-way links is hard to maintain, you can omit some languages on some pages. Google says it is most important to link newly added language pages in both directions with your main, original language pages.
- If you have several URLs for the same language in different countries, for example en-IE, en-CA and en-AU, Google suggests also providing a generic en page for everyone else. It can be one of the specific pages.
- Consider an x-default fallback page for users whose language does not match any version. Google says it was designed for language selector pages and works best with those.
- In HTML, the link elements must sit inside a well-formed head element, and a hreflang link element should not be combined with other attributes such as media.
In a sitemap, each URL entry lists every variant, including itself, using xhtml link children and the xhtml namespace. The page says those child entries do not count toward the sitemap's URL limit, and that a sitemap can only contain URLs under the directory it is hosted in.
Codes
- The value is a language code in ISO 639-1, optionally followed by a region code in ISO 3166-1 Alpha 2, for example en-GB or de-BE. Case does not matter to Google; uppercase region codes follow the standard.
- You cannot give a country code alone. Google's example: "be" is the language code for Belarusian, not Belgium, so for Belgium you would use de-BE, nl-BE or fr-BE for the language you mean.
- Codes outside those standards, such as es-419, are not supported. Reserved codes such as EU, UN and UK are ignored by Google Search for hreflang.
- For Chinese, zh-TW lets Google derive the Traditional script; you may also write the script explicitly, such as zh-Hant or zh-Hans.
The mistakes Google names
- Missing return links (page X points to Y but Y does not point back).
- Wrong language codes, including region alone.
- Wrong region codes. The page lists two third-party tools for generating and testing tags and says Google does not maintain or check them. We have not tested them.
Omnistu advice for an app or business site (not from the source)
- Decide first whether you need separate pages at all. If the content is the same for everyone, extra variants add work for no reader benefit.
- Do not machine-translate pages in bulk and publish them without review; see our article on Google's spam policies for the scaled content text.
- Ask the developer which of the three methods the site uses and to show a page's tags or a sitemap entry. Check that each page lists itself and every other variant, and that the pages link back.
- Keep one owner for the list of languages, so a new language is added to every page's set at once.
Limits
One Google page, read in full on 15 November 2026. It covers Google Search only; other search engines were not read. We did not test any tool or implementation, and we make no claim about how hreflang affects rankings or traffic. Translation quality, local law and content localisation are outside this article.
By Omnistu.