Visual guide to hreflang language, region, return links, and x-default

How to Use Hreflang Correctly

Author: JVDS Design Studio Reading time: about 8 min

A common multilingual-site mistake is adding hreflang="en" to the English page and stopping there. A working implementation requires every version to list itself and all corresponding versions, use complete addresses and valid language-region codes, and provide reciprocal links.

Hreflang describes a page-to-page relationship; it is not a language label for an entire website. Only genuinely equivalent content versions should belong to the same set.

01 When Should You Use Hreflang?

Use it when the same topic has versions in different languages, or when content in the same language varies by region. Translating only the navigation and footer while leaving the body unchanged does not create a complete language version.

A single-language site, unrelated pages, or content available only through browser translation should not use a false equivalence.

Visual explanation that every version must include itself and all other versions

02 Every Version Must Include Itself and All Other Versions

The English page must list its own English URL plus every corresponding Chinese, Japanese, and other URL. The Chinese page must list the exact same set. If two pages do not point to each other, Google may ignore the annotations.

When a language is added, update the entire page set rather than the new page alone.

03 Use Valid Language and Region Codes

Use ISO 639-1 language codes and, optionally, ISO 3166-1 Alpha 2 region codes, such as en-US. Do not use a country code alone, and do not use UK as the region code; the United Kingdom is GB.

When language alone is sufficient, use en, zh-Hans, or zh-Hant instead of adding meaningless regional detail.

Visual explanation of using x-default as a fallback when no language matches

04 Use x-default as the No-Match Fallback

A language selector, global home page, or default version can use hreflang="x-default" to provide a destination when no language matches.

It is optional and does not mean English by default. Point it to the page that genuinely works best as a fallback.

05 HTML, HTTP Headers, and Sitemaps Are Equivalent

Google supports hreflang in the HTML head, HTTP response headers, or an XML Sitemap. Choose one method that is easy to maintain. Using all three provides no additional search benefit and increases the risk of inconsistency.

Non-HTML files such as PDFs can be annotated through HTTP headers or a Sitemap.

Visual explanation of coordinating hreflang with canonicals and URL structure

06 Coordinate Hreflang With Canonicals and URL Structure

Each language page should generally canonicalize to itself instead of every version pointing to the primary language. Each URL must be independently accessible and indexable, and should use a complete HTTPS address.

Automatic redirects, incorrect redirects, and mismatched language versions undermine the annotations.

Common Hreflang Errors

Error
Result
Fix
Missing return links
The relationship may be ignored
Use the same complete set on every version
Invalid codes
The language or region is not recognized
Check against ISO standards
Relative URLs
The implementation does not meet requirements
Use complete absolute URLs
Every page canonicalizes to the primary language
Language pages may not be indexed independently
Each version usually uses a self-referencing canonical
Pages are not equivalent
Users reach the wrong version
Group only genuinely equivalent pages
Three methods contain conflicting data
Maintenance and diagnosis become difficult
Choose one primary implementation

Frequently Asked Questions

Does hreflang improve keyword rankings?

Its main purpose is to help Google choose the right language or regional version for a user. It is not a direct ranking bonus.

How should Simplified and Traditional Chinese be marked?

You can use zh-Hans and zh-Hant, optionally with a region such as zh-Hant-TW, but only when the content truly differs.

Can hreflang connect pages on different domains?

Yes. Versions do not need to share a domain, but they must link back to each other with complete URLs.

Do multilingual pages need matching URL paths?

No, although a consistent structure makes maintenance and mapping easier.

Can we redirect automatically based on IP?

Use caution. Provide independently accessible URLs and a language selector so users and crawlers can reach other versions.

Service
View
Related service
Related article
Read the article
Design work
Project inquiry
Link copied

From Idea to Launch, We Build It Together

Building useful, scalable digital products around user experience

Tell Us About Your Project