We reviewed the current Google Search Central documentation on localized versions, canonicalization, locale-adaptive pages and Search Console on July 29, 2026, and revised outdated information and overstated SEO claims.
hreflang is not a magic tag that directly raises search rankings. It tells Google how language and regional URLs for equivalent content relate, helping it select an appropriate URL for search users. Consistency in translation quality, URL design, canonicalization, indexability and internal links matters too.
A correct hreflang implementation shares a complete mapping on each page
For Japanese, English and Traditional Chinese versions, place links for all three on each page. Use fully qualified URLs, include the page itself and ensure reciprocal references.
| Purpose | Tell search engines how language and regional URLs for equivalent content relate |
|---|---|
| Typical uses | Multilingual sites, regional pages in one language, and pages with region-specific currency, shipping or products |
| Key requirements | Self-reference, reciprocal links, fully qualified URLs and valid language and region codes |
| Implementation methods | HTML <link>, HTTP Link headers or XML sitemaps |
| canonical | Each language version generally points to a canonical URL in the same language |
| x-default | A fallback URL for users not matched by another language or region annotation |
| Checks | Inspect source, responses or sitemaps, URL Inspection, status 200, indexability, canonicals and return links |
| Last reviewed | July 29, 2026 |
What is hreflang? A way to identify language and regional URL relationships
hreflang is an annotation that tells search engines how URLs for localized versions of the same content relate. For example, Japanese and English versions can be linked as localized versions of one page.
Google may discover other language versions without hreflang, but explicitly identifying the relationships helps it select URLs appropriate to language or region.
URLs differ by language or region
/ja/and/en/have translated pagesen-USanden-GBhave different prices or shipping terms- Equivalent pages span country domains or subdomains
No alternate URL exists
- Only a Japanese page is published
- Text switches on the same URL without separate URLs
- Content is entirely different and the pages are not equivalents
hreflang and the HTML lang attribute serve different purposes
<html lang="ja"> helps browsers and assistive technology identify a document's primary language. hreflang describes relationships between URLs. Google says it determines a page's language algorithmically from its content rather than directly relying on hreflang or HTML lang.
lang supports accessibility and document semantics; hreflang maps localized URLs.hreflang is not a direct ranking boost
Showing a suitable language URL can help users understand content and may reduce visits and exits from the wrong language. hreflang alone does not improve content quality or authority. Evaluate traffic and conversions alongside localization quality, search intent, speed, internal links and regional product fit.
Plan URLs first: provide crawlable URLs for each language
Before adding hreflang, make each localized version available at a distinct URL. When content changes only by IP address or Accept-Language, Googlebot may not be able to crawl every language or regional version.
Subdirectories
example.com/ja/example.com/en/
Often easy to manage within one site.
Subdomains
ja.example.comen.example.com
Can separate operations and infrastructure, but measurement and management may also be split.
Country-code domains
example.jpexample.co.uk
Clearly indicate regional focus, but each domain requires its own operation, evaluation and cost.
Do not rely solely on automatic redirects
You may suggest a language based on estimated location or browser preferences, but let users and crawlers access each URL directly. Forced redirects that block alternate languages can interfere with crawling, sharing, language switching and travel.
/ja/product/Self-reference and links to all languages/en/product/Output the same complete set/zh/product/Return links are required too/languages/A language selector or default pageDomains may differ. What matters is that equivalent pages recognize one another and form a consistent group.
Correct hreflang syntax: basic HTML implementation
For HTML pages, inside <head>, use rel="alternate" on <link> elements. The following example links Japanese, English, Traditional Chinese and a language selector.
<link rel="canonical"
href="https://example.com/ja/product/" />
<link rel="alternate" hreflang="ja"
href="https://example.com/ja/product/" />
<link rel="alternate" hreflang="en"
href="https://example.com/en/product/" />
<link rel="alternate" hreflang="zh-Hant"
href="https://example.com/zh/product/" />
<link rel="alternate" hreflang="x-default"
href="https://example.com/languages/product/" />
Include the same four hreflang links on the English and Chinese pages. What changes is each page's own canonical: the English page points to the English canonical and the Chinese page to the Chinese canonical.
Include the page itself
On the Japanese page, use hreflang="ja" to reference that page. This is a self-reference.
Add return links on the other pages
If Japanese points to English, English should also point to Japanese. A one-way annotation may be ignored.
Use fully qualified URLs
/en/product/ is relative; use https://example.com/en/product/, including protocol and host.
Link only equivalent pages
Avoid mismatches such as a Japanese product page and an English product listing. Match URLs by search intent and main content.
Choosing language and region codes
Start with an ISO 639-1 language code and add an ISO 3166-1 alpha-2 region code after a hyphen only when needed. A country code cannot be used on its own as a region.
| Target | Recommended example | Avoid | Reason |
|---|---|---|---|
| Japanese generally | ja | jp | The first code is a language; a country code alone is invalid for regional targeting |
| Japanese for Japan | ja-JP | ja_JP | Use a hyphen, not an underscore |
| English for the United Kingdom | en-GB | en-UK | Google does not use UK as a region code |
| Traditional Chinese | zh-Hant | zh-traditional | Use an ISO 15924 script code |
| Simplified Chinese | zh-Hans | cn | cn is a country code, not a language code |
| General English | en | en-WORLD | A language code alone is sufficient without a regional target |
ja or ja-JP: which should you use?
For the same page for Japanese speakers worldwide, ja is sufficient. For Japanese prices, shipping, laws or store information specifically aimed at Japan, consider ja-JP. Adding more regional variants is not automatically better; do so when content or terms differ.
ja-JP、en-GB, with a lowercase language and uppercase region code.Three implementation methods: HTML, HTTP headers and XML sitemaps
Google supports all three without a search advantage for any one method. Choose one that fits your site and operations. Combining methods offers no extra search benefit and can create inconsistencies.
| Method | Suitable for | Advantages | Considerations |
|---|---|---|---|
| HTML | Small to medium HTML sites | Easy to inspect in source and understand per page | Many languages lengthen the head and require template management |
| HTTP headers | Non-HTML files such as PDFs | Can be configured without changing the document | Requires server or CDN configuration and is less visible in a browser |
| XML sitemap | Sites with many URLs and languages | Makes centralized mapping easier | XML becomes verbose and requires generation and update controls |
HTTP header example
Link: <https://example.com/ja/guide.pdf>; rel="alternate"; hreflang="ja",
<https://example.com/en/guide.pdf>; rel="alternate"; hreflang="en",
<https://example.com/guide-selector/>; rel="alternate"; hreflang="x-default"
XML sitemap example
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://example.com/ja/product/</loc>
<xhtml:link rel="alternate" hreflang="ja"
href="https://example.com/ja/product/" />
<xhtml:link rel="alternate" hreflang="en"
href="https://example.com/en/product/" />
<xhtml:link rel="alternate" hreflang="x-default"
href="https://example.com/languages/product/" />
</url>
<url>
<loc>https://example.com/en/product/</loc>
<xhtml:link rel="alternate" hreflang="ja"
href="https://example.com/ja/product/" />
<xhtml:link rel="alternate" hreflang="en"
href="https://example.com/en/product/" />
<xhtml:link rel="alternate" hreflang="x-default"
href="https://example.com/languages/product/" />
</url>
</urlset>
With a sitemap, include the same alternate URL set inside each localized URL's <url> element. List canonical URLs that return 200 and can be indexed.
How hreflang and canonical work together
hreflang indicates language and regional alternatives; canonical indicates a preferred URL among duplicate or similar URLs. They serve different purposes and cannot replace one another.
Each language points to its own language's canonical URL
Japanese page → Japanese canonical
English page → English canonical
Then add reciprocal hreflang references
Canonicalizing every language to Japanese
Pointing English or Chinese pages to a Japanese canonical can conflict with the alternate relationships and make those other language URLs less likely to remain in search.
<!-- Japanese page /ja/product/ -->
<link rel="canonical" href="https://example.com/ja/product/" />
<!-- English page /en/product/ -->
<link rel="canonical" href="https://example.com/en/product/" />
<!-- Use the same hreflang set on both pages -->
<link rel="alternate" hreflang="ja" href="https://example.com/ja/product/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/product/" />
Duplicate URLs in the same language
If an English page is also available with parameters, canonicalize it to the English preferred URL and use that URL in hreflang too. Keep the sitemap, internal links, canonical and hreflang aligned.
Using x-default for unmatched users
hreflang="x-default" identifies a fallback URL when none of the specified localized versions matches the user's language and region settings. It is a fallback rather than a specific language code.
Language or country selector
A page where visitors choose language or shipping region is a common x-default use.
Use English as the default
This is appropriate if the actual policy is to show English to unsupported users, but not merely because an English page exists.
<link rel="alternate" hreflang="ja-JP"
href="https://example.com/jp/" />
<link rel="alternate" hreflang="en-US"
href="https://example.com/us/" />
<link rel="alternate" hreflang="en-GB"
href="https://example.com/uk/" />
<link rel="alternate" hreflang="x-default"
href="https://example.com/country-selector/" />
x-default is optional. There is no need to add a token fallback when a clear fallback URL does not exist.
Implementing hreflang in WordPress and CMSs
Multilingual features such as WPML or Polylang can generate hreflang in WordPress, but installation alone does not guarantee correctness. Themes, SEO plugins, translation plugins and CDNs can produce duplicates or conflicts.
Register equivalent translations in the CMS
Use article identities or translation groups to identify equivalent pages, rather than guessing from URL patterns alone.
Choose one output source
Assign responsibility so the theme and multiple plugins do not duplicate hreflang annotations.
Do not force links to untranslated pages
Exclude a language URL when a corresponding translation is unavailable. Do not point every page to that language's homepage instead.
Synchronize publication state
When a translation is unpublished or its URL changes, update other languages' annotations, sitemaps and internal links too.
Model translation mappings as data in Go or static site generators
Simply substituting a path in a template can fail when slugs differ or translations are missing. It is safer to assign a translation-group ID and generate the set from published languages and canonical URLs.
{
"translationGroup": "product-123",
"alternates": [
{"lang": "ja", "url": "https://example.com/ja/shohin/"},
{"lang": "en", "url": "https://example.com/en/product/"},
{"lang": "zh-Hant", "url": "https://example.com/zh/product/"}
],
"xDefault": "https://example.com/languages/product/"
}
Twelve common hreflang errors and fixes
Errors can involve syntax, URL responses, canonicals, indexability and translation relationships. Check them in this order to narrow down causes.
| Error | What happens | Fix |
|---|---|---|
| 1. Missing return link | A one-way annotation may be ignored | Output the same complete set on the other page |
| 2. Missing self-reference | The cluster is incomplete | Include each page's own language URL |
| 3. Relative URL | Interpretation can vary by environment or host | Use a fully qualified HTTPS URL |
| 4. Country code alone | JP、US are region codes, not language codes | ja-JP、en-US: put the language first |
| 5. Invalid region code | en-UK、en-EU may not be recognized | Use an official ISO 3166-1 alpha-2 code |
| 6. 404 or 5xx | The alternate URL is unavailable | Point directly to a public URL that returns 200 |
| 7. Redirect URL | Extra processing and conflicting signals | Point directly to the final canonical URL |
| 8. noindex | The alternate URL cannot appear in search | Make it indexable or remove it from the set |
| 9. Canonical points to another language | hreflang and canonicalization conflict | Canonicalize to a URL in the same language |
| 10. Page content does not correspond | A product detail and a category, for example, do not match | Link pages with corresponding primary content and search intent |
| 11. Methods disagree | HTML and sitemap contain different URL sets | Use one method or generate both from the same data source |
| 12. Missed updates | Old references remain after URL changes or removal | Add automated checks and change review to the publishing workflow |
Avoid linking every page to each language's homepage
An untranslated article and an English or Chinese homepage do not represent the same page. Omitting that language's hreflang is more accurate. Separately provide a site-wide language switcher or notice about planned translation for users.
Wording may vary, but the purpose should match
Prices, currencies, shipping, contacts, legal information and inventory can naturally differ by region. A product purchase page and an about page, however, are not equivalents. Ask whether each page serves the same purpose for its region.
How to check hreflang without relying only on Search Console
Google Search Console's former International Targeting report has been retired. Do not assume a dedicated hreflang error list exists; combine URL Inspection with checks of actual output.
Inspect where annotations are output
For HTML check the original head as well as the rendered DOM; for HTTP inspect response headers; for XML inspect the submitted sitemap.
Check responses for all URLs
Check for status 200, robots.txt blocks, noindex and unnecessary redirects.
Check set symmetry
Compare language codes and URLs on each page, including self-references, return links and x-default.
Check canonical consistency
Use URL Inspection to compare the declared and Google-selected canonical with URLs in hreflang.
Observe search results and traffic
Check clicks by country and landing page in Search Console, and review language-specific landing pages and conversions in analytics. Look for unexpected language URLs.
Prelaunch checklist
Metrics for evaluation
Before and after implementing hreflang, examine not only ranking but whether visitors land on the intended language URL. Combine country, query and page in Search Console; in analytics review language-specific landing pages, subsequent actions and conversions such as inquiries or purchases.
Operational design for large sites
hreflang is often more fragile during later additions, removals and URL changes than at initial implementation. As languages and pages grow, manage it with data and tests instead of manual edits.
Use one authoritative mapping
Choose a CMS, database or translation system as the source of truth and generate HTML and sitemaps from it.
Track publication state per language
Manage draft, review, published and retired states; include only published canonical URLs in clusters.
Check mechanically in CI
Test code formats, self-references, return links, duplicates, HTTP status and canonical consistency.
Update changes together during migrations
Switch 301 redirects, canonicals, internal links, sitemaps and hreflang in the same release.
Minimum automated tests
for each localized page:
assert canonical is absolute HTTPS URL
assert canonical language == page language
assert hreflang set contains self
assert each language code maps to one canonical URL
assert all alternate URLs return HTTP 200
assert no alternate URL is noindex
assert every alternate page links back
assert all pages in the group expose the same set
Frequently asked questions about hreflang
Does hreflang improve search rankings?
It does not guarantee a direct ranking increase. It helps Google choose the URL appropriate to a user's language or region. Fewer wrong-language visits may benefit user experience or conversions, but results are not guaranteed.
ja or ja-JP: which is appropriate?
It depends on the target. For Japanese without a regional restriction use ja; for Japan-specific prices, shipping or legal conditions consider ja-JP.
Does each page need a self-referencing hreflang?
Yes. Google's guidance says to include the page itself as well as other language versions, with the same complete set on every page.
Do relative URLs work?
Specify alternate URLs as fully qualified URLs beginning with https://. Pages can be linked across domains.
Can different language pages share one canonical?
Generally avoid this. Point each language version to its canonical in the same language and express language relationships with hreflang.
Is x-default required?
No. Use it when there is a language selector or an actual fallback for users who do not match a specified locale.
Is using both HTML and sitemaps a stronger signal?
Google treats HTML, HTTP headers and XML sitemaps equivalently and says combining all three offers no additional search benefit. Usually choose one maintainable method.
Can Search Console show hreflang errors?
The former International Targeting report has been retired. Use URL Inspection for index status and Google's selected canonical, and verify source, responses, sitemaps and return links yourself.
Conclusion: organize URL mappings and operational rules before adding tags
Successful hreflang depends on accurately managing which pages correspond, not just adding a line of markup. Publish each localized version at a distinct URL, group equivalent pages and align self-references and reciprocal links.
- Make language and regional URLs directly crawlable
- Output the same complete set including each page itself
- Use fully qualified URLs and valid language and region codes
- Generally point canonical to a preferred URL in the same language
- Use x-default only when an actual fallback exists
- Choose a maintainable method from HTML, HTTP headers and XML sitemaps
- Continuously check status, indexability, canonical and return links after launch
Multilingual SEO requires localization of search terms, wording, prices, trust information and contact paths, not mechanical literal translation. Use hreflang to communicate those well-formed page relationships to search engines.
・Google Search Central: Tell Google about localized versions
・Google Search Central: Specify a canonical URL
・Google Search Central: Crawling locale-adaptive pages
・Search Console Help: Retirement of the International Targeting report
・Search Console Help: URL Inspection tool