PowerSupporter
TL;DR
Yes, but only if each language has its own indexable URL with correct hreflang and self-referencing canonical tags. A JavaScript language switcher on one URL gets only one language indexed by Google.
PowerSupporter's own site had English customers finding it in search, while a share of its Australian warehouse and custom-software customers search in Chinese and found nothing. A language-switcher button on a single URL looks bilingual to a visitor, but Google indexes only one version of that page, usually whichever language loads first.
Three Changes That Made Both Languages Indexable
- Separate URLs per language — for example
/product-erp.htmland/zh/product-erp.html, linked with reciprocalhreflangtags plus anx-defaultpointing at English. - Self-referencing canonical tags — each page's canonical points to itself, never to the other-language version.
- One shared business identity — a single
OrganizationJSON-LD with one@idused on both language versions, translated page content taggedinLanguage: zh-Hans, and Chinese keywords chosen from actual search terms rather than literal translation.
| Change | Fixes | If Skipped |
|---|---|---|
| Separate URLs + hreflang | Both languages indexable | Only one language shows in search |
| Self-referencing canonical | Each page indexed on its own | Chinese page dropped from index |
| Shared identity + native keywords | One identity, searchable terms | Duplicate identity; translated terms nobody searches |
PowerSupporter Editorial Team
Based in Melbourne, PowerSupporter builds custom software for Australian businesses — from warehouse management and inventory systems to bilingual websites and ongoing SEO.