Each edition needs its own canonical and the same complete set of reciprocal language alternatives. Check the published HTML, not only the map used to generate it.
1. Choose editions before choosing codes
This worked example uses the two editions of the guide you are reading. English lives at /seo/hreflang-english-chinese-websites/; Simplified Chinese lives at the same path under /zh/. These are real article addresses, rather than language homepages substituted for missing translations.
Our map uses en and zh-Hans. The second identifies Simplified Chinese script; it does not claim that every Chinese reader is in mainland China. Choose regional annotations only when the editions genuinely serve a regional distinction. Do not infer a country from a script or add a region just to make the configuration look more precise.
Before writing tags, compare the main content: question, answer, examples, limitations and next action. A translated navigation bar around an untranslated article is insufficient. Google recommends separate language URLs and a clear, consistent language in the visible content. Review the multilingual-site guidance.
2. Generate a complete reciprocal map
Enter the following three language-and-URL pairs as separate rows in the Hreflang Builder & Map Checker. The third entry makes English our fallback when no listed language fits. This is an editorial choice for this site, not a requirement that every bilingual site use English.
en https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/
zh-Hans https://www.jinchenggeo.com/zh/seo/hreflang-english-chinese-websites/
x-default https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/For each edition, the generated alternate set contains English, Simplified Chinese and the optional x-default fallback. Both pages include themselves and each other. Google documents absolute URLs and return links between editions; a one-way annotation leaves an incomplete relationship. Read the localized-versions specification.
The builder checks the supplied map and formats tags. It does not fetch remote pages, verify their translations or establish that Google has processed them. Keep the generated output as preparation evidence, then perform the deployment checks below.
3. Give each page its own canonical
The English edition has this head fragment:
<link rel="canonical" href="https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="en" href="https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="zh-Hans" href="https://www.jinchenggeo.com/zh/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="x-default" href="https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/">The Chinese edition uses the same alternates, but its canonical points to the Chinese URL:
<link rel="canonical" href="https://www.jinchenggeo.com/zh/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="en" href="https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="zh-Hans" href="https://www.jinchenggeo.com/zh/seo/hreflang-english-chinese-websites/">
<link rel="alternate" hreflang="x-default" href="https://www.jinchenggeo.com/seo/hreflang-english-chinese-websites/">Do not point the Chinese canonical to English merely because English is the main language. For these complete translations, each edition is independently useful. Canonicalization addresses duplicate or substantially similar URLs; language annotations describe editions. If a site has additional duplicate URLs within one language, resolve that separate problem deliberately. See our comparison of crawling, indexing and canonical controls.
Download the English head fragment and Chinese head fragment. These are reference snippets for these exact URLs, not complete HTML documents or a universal configuration. Replace the map with your own addresses before reusing it elsewhere.
4. Look for mismatches that a valid map cannot detect
| Observed mismatch | Why it matters | What to check |
|---|---|---|
| An article points to the Chinese homepage | The target does not answer the same reader question. | Link the actual translated article; omit an edition that is not ready. |
| Both editions declare the English canonical | The language relationship and preferred URLs conflict. | Inspect each live canonical and the intended duplicate set. |
| Tags point to a redirect or missing page | The published map differs from the stable destination map. | Use the final, working canonical URLs. |
| Only English returns the alternate tags | The relationship is not reciprocal. | Compare the rendered head on both language URLs. |
A tag can be syntactically valid while pointing to the wrong article. Review one complete language pair as a reader, then sample the rest of the template. A spreadsheet that lists “pass” for every URL without inspecting the page cannot prove equivalence.
5. Check publication in a repeatable order
- Open both final HTTPS URLs and read the main content in each language.
- Inspect the returned HTML head: one intended canonical and a complete alternate set.
- Follow the visible language switch in both directions; it should preserve the article topic.
- Confirm that neither intended public edition is blocked, missing or marked noindex.
- Check sitemap URLs and internal links against the same final addresses.
- Record the check date and keep search-engine processing as a separate status.
Our site emits language alternatives in HTML and the general sitemap. Google supports HTML, HTTP headers and XML sitemap annotations as alternative methods; repeating a method does not create an extra ranking benefit. If you maintain more than one, generate them from one map to avoid drift.
Let readers choose a language through visible links. Do not make access to the Chinese edition depend on a language cookie or force a redirect just because a browser reports English. If a page remains absent from search after the technical checks, use the indexing diagnostic. Hreflang is one relationship to verify, not a universal explanation for missing indexation.
Keep the pair intact when content moves
When a title, path or translation changes, update the mapping, navigation and internal references together. Preserve a historical address through an appropriate redirect when the replacement answers the same question. Do not redirect every retired URL to a language homepage.
Our domain-rebuild report describes the historical routes preserved on this site. Its redirect checks and this guide’s language checks cover different relationships. Save both sets of evidence when a bilingual migration changes URLs.
Follow the evidence.
- Google Search Central · Localized versions ↗
- Google Search Central · Multi-regional and multilingual sites ↗
- Google Search Central · Canonical URLs ↗
References checked Oct 16, 2026. Examples and workflow recommendations are editorial illustrations, not measured results. Provider guidance may change. Our editorial standards.
