Why language versions directly affect AI visibility
When users ask ChatGPT in English, engines prefer English sources; when they ask in Chinese, engines do not cite Chinese sources only — but a well-formed Chinese version strengthens entity consistency in Chinese-language contexts. The typical pattern for companies going global: a thin, rarely updated English showcase site and a rich Chinese main site — AI sees exactly the thinnest version of the company. Language versions are not a translation problem; they are a fact-supply problem. AI can only cite the language versions it can read — what it cannot read does not exist.
The reverse is also true: complete language versions that agree are themselves an entity signal. Same company, same facts, two languages: engines cite with more confidence; disagree, and they would rather cite nothing.
Three structures; only the first is recommended
One tree, paired fields (recommended)
One record per page, both languages stored side by side, published, updated and retired together. This site is built that way. Change one fact and both versions change together; retire a page and both go together. AI reads the same facts in either language.
Two independent trees
A separate site per language. Flexible short-term, guaranteed to drift — one side gets edited, the other does not, and AI reads two conflicting versions of your facts and has to guess. The cost is not in building them; it is in doing every later update twice and checking it twice.
Live machine-translation plugins
Cheapest, but translation quality, URL structure and structured data are all outside your control — a negative for AI citation. Machine-translated pages have no stable URL correspondence, and entity descriptions drift with the translation output — engines struggle to treat them as trustworthy sources.
How to get hreflang right
Hreflang tells search engines where the other language versions of a page live. Every language version must carry the full set: its own language, the counterpart language, and x-default (the default version). Two rules matter most: every page must include an hreflang link pointing to itself (self-referential), and language versions must point back at each other (return links) — the Chinese page points to the English page, and the English page must point back. A one-way annotation is ignored by search engines. The figure on this page shows the standard three-link pattern.
Beyond hreflang, both language URLs belong in the sitemap, and JSON-LD entity descriptions must agree across languages. Google's official guidance on multilingual sites is listed under Sources.
Three common mistakes
Mistake 1: unequal content across language versions. The Chinese site carries full product specs; the English site carries slogans. Overseas buyers ask AI in English, and the engine can only read the English surface — the company's most persuasive facts effectively do not exist. Fix: core pages complete in both languages, specs and cases in item-by-item correspondence.
Mistake 2: hreflang without return links. The Chinese page annotates the English version, but the English page never points back. Search engines treat one-way annotations as unreliable, so the correspondence is effectively never established. Fix: check return links appear in pairs at every publish.
Mistake 3: chaotic URL structure. The Chinese and English versions of the same content sit at unrelated URLs (say, Chinese at /product/ and English at /en-goods/) — hard to maintain, and hard for search engines and AI to confirm they are the same page. Fix: design URLs as language pairs (e.g. /zh/product/ and /en/product/), one address per page, stable for life.
Minimum viable setup
- Core pages (home, solutions, cases, contact) complete in both languages;
- The full hreflang set (self, counterpart, x-default);
- Both language URLs in the sitemap;
- JSON-LD entity descriptions consistent across languages.
News can publish in one language only — just accept it then serves only that language's market. For scale: in our measurement of 30 global-facing websites of Chinese exporting companies (Negency Flagship Report 2026, Issue 1, sampled on a single day, 30 October 2026), 17 had no JSON-LD at all and 13 had a missing or non-unique H1 — entity facts are often missing even in one language, and consistency across languages only raises the bar.
How to verify the language versions are right
Three checks: spot-check that hreflang return links appear in pairs; ask AI the same questions in both languages and compare whether the company facts agree; verify core pages correspond item by item across languages. Done right, AI's answers in both languages should describe the same company. For the rest of the website overhaul, in crawl, structure, facts and trust order, see What should a corporate website change for the AI search era?