hreflang for English and Chinese pages

The short answer: hreflang is an annotation that tells Google which pages are equivalent versions of the same content in different languages or regions — it does not translate a page, does not decide the language Google displays, and works correctly only with reciprocal, self-referencing, fully qualified links (Google: Tell Google about localized versions). For an English-and-Chinese site, the practical work is choosing codes that match your actual content and audience, wiring the annotations both ways, and validating that the targets really work.

Choose codes for the content you actually have

Language and language-region codes are the heart of the matter, and the W3C's guidance is the reference for constructing them correctly: a language tag may be language-only (en, zh), language-script (zh-Hans, zh-Hant), or language-region (en-SG, zh-CN) (W3C: Language tags in HTML and XML). Two rules keep an English-and-Chinese setup honest:

Choose codes for actual content and audience. Use en-SG only if the English page genuinely targets Singapore; use zh-Hans (simplified script) or zh-Hant (traditional) only where the content is genuinely written in that script for that readership. Do not conflate script with region: a zh-Hans page is not automatically a China page, and a Hong Kong or Taiwan page may be zh-Hant.
Do not annotate aspirational versions. If a Chinese translation is machine output or half-finished, annotating it as an equivalent version tells both Google and readers it is a full alternative — which it is not. Google determines a page's language from its content, and hreflang cannot override what the content itself says (Google: Tell Google about localized versions).

Implementation, in brief

Google accepts three equivalent mechanisms, all documented (Google: Tell Google about localized versions):

HTML <link rel="alternate" hreflang="…"> elements in each page's <head>.
HTTP Link headers, useful for non-HTML files.
A sitemap listing each URL with its hreflang alternates.

Whatever the mechanism, the requirements are the same: each version must list all versions including itself (self-reference is required); alternate links must use fully qualified URLs with protocol; and targets must not be redirects or error pages. Google's multi-regional guidance adds the wider frame: use localized URLs, and expect the most important signal to remain each page's own content, properly localized — hreflang is an aid, not a substitute for a genuinely translated page (Google: Managing multi-regional and multilingual sites).

Validate before and after

Validate the wiring as a routine, not a one-off:

Every hreflang target URL returns HTTP 200 with the intended language content — no redirects, no 404s.
Every set is reciprocal: if the English page lists the Chinese page, the Chinese page lists the English page and itself.
The hreflang and lang annotations agree with the actual content language; where they conflict, content wins in Google's interpretation (Google: Tell Google about localized versions).
Re-check after any CMS change or redesign — hreflang breakage is a classic silent regression.

And keep the outcome honest: hreflang helps Google serve the right version to the right user; it does not guarantee any ranking, nor which version appears for any given query (Google: Managing multi-regional and multilingual sites). If you want this checked on your own site, our GEO & SEO services work on a scoped basis — explained findings, approved fixes, same-condition retests. Write to us via contact.

Correct reciprocal hreflang between an English and a Chinese page — and the broken case.

Frequently asked questions

Does hreflang decide which language a user sees?

Not by itself. It is a hint about equivalent versions; Google determines page language from content and serves versions based on its own evaluation (Google: Tell Google about localized versions).

Do I need hreflang if I only have one language?

No. hreflang is for sites with multiple language or region variants of the same content. A single-language site needs none.

Should I use zh-CN or zh-Hans for Chinese pages?

Whichever matches the content and intended audience: zh-Hans/zh-Hant describe the script; zh-CN, zh-SG and similar add regional targeting. Follow W3C tag construction rules and do not assume script implies region (W3C: Language tags in HTML and XML).

Can I use hreflang to point at machine-translated pages?

Only if the translation is a genuine equivalent version. Annotating a low-quality or incomplete translation as an equivalent misleads both users and systems; Google's guidance expects genuinely localized content (Google: Managing multi-regional and multilingual sites).

Sources

developers.google.com/search/docs/specialty/international/localized-versions (read 10 November 2026)
w3.org/International/articles/language-tags/ (read 10 November 2026)
developers.google.com/search/docs/specialty/international/managing-multi-regional-sites (read 10 November 2026)

GEO & SEO optimisation service · Make an enquiry · More GEO and AI search answers

Owned editorial content by TopGEOClaim (ACN International Pte. Ltd., Singapore). Drafted with AI assistance, reviewed, and checked against the linked sources. It describes public documentation, not customer results, and does not promise any search or AI placement. Vendor behaviour may change; check the linked sources.