What Is hreflang?

At a glance

Search engines use hreflang to select an appropriate localized URL. Versions normally need reciprocal references and self-references.

Matching language and regional versions

hreflang identifies the language or region served by related URLs, such as zh-CN, zh-TW or en-US. Search engines can use language, location and query context to choose a suitable version, reducing cases where Chinese readers land on English content or UK readers see US pricing.

Language codes normally use ISO 639-1 and optional regions use ISO 3166-1 alpha-2. A region cannot stand alone without a language. x-default can identify a language selector or international fallback, but does not replace explicit localized versions.

Why reciprocal declarations form a complete set

• Each version should list itself and its corresponding alternatives. If A references B but B does not return the reference, the association may be ignored.
• HTML links, HTTP Link headers and XML sitemaps can express hreflang. One consistently maintained method is sufficient; contradictions across methods complicate diagnosis.
• Each language version normally has a self-referencing canonical. An English page canonicalized to a Chinese page may not be treated as an independent language version.
• Targets should be crawlable, successful and equivalent in content. Redirects, 404s, noindex and invalid language codes weaken the relationship.

Coordinating language, region and automatic redirects

Regional versions of the same language should have meaningful differences, such as currency, availability, legal requirements or contact information. Duplicating many regional URLs with only footer changes adds maintenance and quality problems. Forced IP redirects can also obstruct access to alternatives.

A clearer experience offers an explicit language switch, remembers user preference and permits direct access to each URL. Accept-Language and IP can inform suggestions rather than override the URL structure and hreflang relationships irreversibly.

Practical use and interpretation

Declared locales, target URLs, self-references and reciprocal links can be inspected directly. A complete set suggests organized international SEO, but search-platform data is needed to establish how engines use it.

A single-language homepage normally does not need hreflang. Missing or conflicting declarations become relevant when multiple language versions exist. If that architecture is unclear, its status remains unknown.

Points to consider

Incomplete configuration may contribute to the wrong language version appearing in search.

Frequently asked questions

Does a single-language site need hreflang?

Usually not. Its purpose is to associate multiple language or regional versions.

Should hreflang and canonical point to the same URL?

Each version normally canonicalizes to itself while hreflang connects corresponding versions. Canonicalizing all languages to one may create conflicts.

Can only the main page list the other languages?

Corresponding pages should return the references and include themselves, forming a complete set.