Bilingual (English / 繁中) content and AI search

In short

• Hong Kong customers ask AI assistants questions in English, in Traditional Chinese and in a mix of both. Your English and Chinese pages each need to be found, understood and trusted on their own.
• Google's documentation is specific: one URL per language, the language judged from the visible text, the versions linked to each other, and no automatic redirects based on a guessed language.
• The practical work is a clean site structure, correct hreflang and lang tags, and Chinese pages that are genuinely written for Chinese readers rather than thin copies of the English.

Why two languages matter more in AI search

A traditional results page shows ten links, and a reader can skip the one in the wrong language. An AI answer usually summarises a handful of sources and links to a few of them. If your Chinese page is missing, thin or confusing, the assistant may describe your business from your English page, from a directory, or from a competitor that has a proper Chinese page.

Google says its AI Overviews and AI Mode may run several related searches across subtopics and data sources to build a response, a process it calls query fan-out. Each of those searches is a chance for one of your pages to be picked up, but only if the page for that language exists, is indexed and answers the question in that language. A bilingual site gives you two sets of pages that can be found, not one set and a half.

What Google says about multilingual sites

Google's guide to managing multi-regional and multilingual sites sets out a few rules that apply directly to English and Traditional Chinese sites:

• One URL per language. Google recommends different URLs for each language version rather than switching language with cookies or browser settings, which its crawler may never see.
• Language comes from the visible text. Google determines a page's language from its content, not from code. It suggests keeping the main content and navigation in one language per page and avoiding side-by-side translations.
• Translate the whole page. If only the menus and footer are translated while the body stays in English, readers and search results get a confusing mix.
• Do not auto-redirect. Redirecting visitors based on a guessed language can stop both people and search engines from reaching every version. Add visible links between the versions instead and let the reader choose.

hreflang and lang: what each one does

Two tags are often confused.

hreflang tells Google that pages are language or regional versions of each other, so it can point a user to the most suitable one. Google's localised versions guide lists the details that trip people up:

• Each version must list itself as well as every other version.
• The links must go both ways. If two pages do not point to each other, Google ignores the tags.
• The code starts with a language and can add a script or a region. Google's own examples include zh-Hant for Traditional Chinese and zh-Hans for Simplified Chinese.
• An x-default entry can name a fallback page for readers whose language matches none of your versions.

lang is the attribute on your page's html element. The W3C recommends always declaring the default language there, and marking any passage in another language with its own lang attribute. Google, however, says it does not use hreflang or lang to detect a page's language. Both tags are worth getting right, but neither can turn an English page into a Chinese one. The text has to do that.

For structured data, schema.org's inLanguage property states the language of a piece of content using a BCP 47 code, the same family of codes used by lang and hreflang. Use it consistently with the page itself.

Writing Chinese pages that stand on their own

Structure gets your Chinese page found. Writing decides whether it is worth citing.

• Write for Hong Kong readers. Use Hong Kong written Chinese and local terms. A page full of Mainland vocabulary or machine-translated phrasing reads as an afterthought to people and is a weaker match for the questions they actually type.
• Answer the same questions in full. If the English page has an FAQ, pricing approach or process section, the Chinese page should have it too, not a shortened summary.
• Keep facts identical. Company names, addresses, phone numbers and service names should match across both versions and your listings. Our article on address and phone consistency covers how to check this.
• Match markup to the text. Google's AI features guidance asks for important content in text form and structured data that matches the visible page. Chinese pages should carry their own Chinese FAQ and organisation details, not English markup copied across.

A short bilingual checklist

1. List your key pages and check that each has an English and a Chinese URL.
2. Open each pair and confirm the body, menus and footer are fully in one language.
3. Check hreflang: every page lists itself and its partner, and the partner links back.
4. Check the lang attribute on each page matches its language.
5. Remove any automatic language redirect and make sure a visible language switch is on every page.
6. Read the Chinese pages aloud. If they sound translated, rewrite the key ones.
7. Ask ChatGPT, Perplexity and Google the same question in English and in Chinese, and note which of your pages, if any, they use.

The short version

AI tools answer in the reader's language and look for sources in that language. If both your English and your Chinese pages are complete, clearly labelled and linked to each other, you give them two good reasons to mention you. If you want a review of how your site handles both languages, see our AI marketing and GEO service or contact us.