Hreflang mistakes that send the wrong language into search

Treat hreflang as a set of agreements

If the English page points at the Traditional Chinese page, the Chinese page must point back, and both should reference themselves. One-way tags are a common reason the annotation is dropped.

Use valid codes. For this market, zh-HK is the usual pairing with en or en-HK. A generic zh tag can surface a page to readers who needed a different Chinese variant.

Only pair pages that are real equivalents

Hreflang is for the same document in another language or regional edition, not for a loosely related blog post. Pairing a service page with a news article confuses the cluster.

Each URL in the cluster should be indexable, return 200, and use a canonical that points to itself. Canonicalising a translated page back to English removes it from the cluster.

• Return-tag every alternate.
• Keep canonicals self-referencing inside the cluster.
• Put the same mappings in the sitemap if the head becomes hard to maintain.

Check the pages people actually land on

Search Console’s international targeting and a manual query with a language preference will show whether the intended URL appears. A correct tag with a weak translation still loses to the page that matches the query language.

Hong Kong sites often need the copy adapted, not only tagged. Cantonese-influenced phrasing and local examples do more than an hreflang attribute on a literal translation.

Do I need hreflang if the site is only English?

No. Add it when you publish real alternate language or regional URLs. A single-language site should not invent alternates.

Should Traditional Chinese pages canonicalise to English?

No. Each language URL should canonicalise to itself and point to the others with hreflang. A canonical to English tells search the Chinese page is a duplicate.