Build Hreflang Tags for English and Chinese Pages
How to prepare hreflang alternates, x-default URLs, and sitemap language rows without creating fake localized versions.
Introduction
Hreflang is most useful when you have real alternate pages for different languages or regions. It is also one of the easiest SEO tags to generate incorrectly: missing return links, wrong locale codes, copied URLs, or alternates for pages that do not actually exist.
The Hreflang Tag Generator helps you turn a locale and URL list into copy-ready alternate tags. The hard part is still editorial: only add alternates for pages that are real equivalents.
Real-world scenario
You have an English tool page and a Chinese version:
https://ascend-lab.com/tools/json-formatter
https://ascend-lab.com/zh/tools/json-formatterThe English page should reference the Chinese page, and the Chinese page should reference the English page. A typical pair looks like this:
<link rel="alternate" hreflang="en" href="https://ascend-lab.com/tools/json-formatter">
<link rel="alternate" hreflang="zh-CN" href="https://ascend-lab.com/zh/tools/json-formatter">
<link rel="alternate" hreflang="x-default" href="https://ascend-lab.com/tools/json-formatter">What to check before generating tags
The pages are equivalents. Do not link unrelated pages just because they share a category.
Each page has a self-canonical. The English URL canonicalizes to English, and the Chinese URL canonicalizes to Chinese when both should be indexable.
Return links exist. If page A lists page B as an alternate, page B should list page A.
Locale codes are specific enough. Use language codes like en or zh-CN consistently with your URL strategy.
Common mistakes
Generating hreflang for missing pages. Alternate tags should not point to 404s, redirects, or placeholders.
Canonicalizing all localized pages to English. That can conflict with the goal of letting localized pages stand on their own.
Forgetting x-default. x-default can point to the default language or language selection path when that matches the product strategy.
Practical QA pass
Check one URL pair from both directions. Open the English page, confirm it links to itself as en, the Chinese page as zh-CN, and the default URL as x-default. Then open the Chinese page and confirm the same set appears there too. Hreflang is reciprocal, so a one-sided tag is a common source of confusion.
Next, compare canonical tags. A Chinese page that has its own searchable content should canonicalize to the Chinese URL, not the English URL. If you intentionally do not want the localized page indexed, do not add fake hreflang just to make the site look bilingual.
Limits
Hreflang helps search engines understand alternate language targeting. It does not translate content, validate quality, or guarantee which version appears for every query.
Next steps
- Hreflang Tag Generator — create alternate link tags from locale URL pairs
- Canonical URL Generator — confirm each alternate has the right preferred URL
- Sitemap URL Checker — review localized URLs before submitting a sitemap
- Meta Tag Previewer — check localized title and description copy
Final practical note
Start with one bilingual pair and make it perfect. Once canonicals, hreflang, sitemap URLs, and visible language links all agree, repeat the pattern for the next page set.