A language switcher is easy to draw and surprisingly easy to build badly. The usual result is an English page with Thai navigation, a Chinese headline, and a booking button that returns to English just when the customer is ready to buy.
That failure mode costs more than it used to. Thailand's Ministry of Tourism and Sports reported that China led every source market for foreign arrivals between 1 January and 1 August 2026, with 3,078,486 Chinese visitors—well ahead of the second-largest market. Every one of them is a potential customer who may search, compare, and decide in Chinese before ever typing a word of English or Thai.
It sounds like the fix is simple: translate the site into Chinese and be done with it. It isn't. A site that's translated but not truly localized—broken navigation, currency in the wrong format, a payment method nobody in the target market uses—can do more damage to trust than having no Chinese page at all. This article covers how to structure URLs and hreflang correctly, localize the actual buying journey, and avoid the technical mistakes that quietly cost both rankings and customers.
One language per page, one clear URL per audience, and one complete experience per customer.
The Half-Translated Journey: when the language switches but the path doesn't
Call it the Half-Translated Journey—a visitor starts in one language, and somewhere between the homepage and the booking button, the experience quietly reverts to a different one: navigation stuck in Thai, an error message that only exists in English, a confirmation email that never got translated at all. Each individual gap looks minor. Together, they tell a Chinese-speaking customer that the business wasn't really built for them—it just added a language switcher.
A complete journey means every step a customer takes to actually buy—not just the marketing pages—exists fully in their language: navigation, forms, error states, confirmation, and follow-up. A Chinese homepage backed by a Thai checkout page isn't a Chinese experience. It's a preview of one.
Give every language its own URL
Use a stable structure such as /th/, /en/, and /zh-hans/. Avoid changing the same URL based only on browser language or cookies. Google recommends different URLs for language versions and warns that automatic locale redirects can prevent users and crawlers from seeing every version. Google Search Central: Multilingual sites
Add visible links so customers can choose language at any time. Preserve the equivalent page when switching instead of sending everyone back to the homepage.
Use hreflang for genuine equivalents
Add reciprocal hreflang annotations only when pages are meaningfully equivalent. A Thai service page and an English blog summary are not alternatives simply because the topics sound related.
Use language codes carefully and add region codes only when the content differs by country. Include an x-default option for a neutral selector or default page when appropriate.
Localize the buying journey
Translate meaning, not word order. A complete localized page includes:
- The customer's problem and vocabulary.
- Currency, dates, and units.
- Local proof and contact details.
- Relevant payment and messaging channels.
- Policies and regulatory context.
- Forms, errors, confirmation messages, and follow-up.
Chinese content for travelers may require different questions and proof from Chinese content for a local business buyer. Define audience before translation—Chinese tourists booking a service and Chinese-speaking distributors sourcing a product are not the same reader.
Picture this: Siam Gems Atelier translates the marketing, not the sale
Picture a hypothetical jewelry business called Siam Gems Atelier, based in Bangkok and selling to both walk-in tourists and overseas buyers. Its team translated the homepage, product gallery, and About page into Chinese well before the 2026 tourism rebound, and traffic from Chinese-speaking visitors grew steadily. Enquiries didn't.
The gap turned out to be everything past the gallery: the certificate-of-authenticity page, the shipping and customs FAQ, and the enquiry form were still Thai-only, with English fallback for the labels. A visitor could browse a full catalogue in Chinese and then hit a wall of unfamiliar text the moment they tried to ask a real question about international shipping. Siam Gems Atelier hadn't built a Chinese experience—it had built a Chinese preview of an experience that stayed Thai and English underneath. Translating the remaining pages, including the ones that felt "too operational to bother with," was what actually moved enquiries.
Keep each page linguistically clear
Google says it uses visible page content to determine language and recommends avoiding side-by-side translations. Keep navigation and primary content in one language per page. Google multilingual guidance
Names, trademarks, and necessary industry terms can remain unchanged, but excessive language mixing makes pages harder for readers and search systems alike.
Build a controlled publishing workflow
Choose a source language, translation owner, and reviewer. Record when regulated or product information was last checked. Do not publish a machine translation directly for legal, safety, pricing, or high-value sales content.
Create a glossary for brand terms, industry language, Thai regulatory terms, and calls to action. Translation memory can improve consistency; it cannot decide whether an example makes sense for a customer in Chengdu or Chiang Mai. The same human-review principle applies to AI-drafted content generally—see what an AI-powered website can and cannot do for a Thai business before automating translation or content drafting.
Protect technical SEO
- Use self-referencing canonical tags on localized pages.
- Include all important locale URLs in sitemaps.
- Keep metadata and structured data in the page language.
- Avoid blocking translated routes from crawling.
- Monitor indexing and broken
hreflangpairs. - Keep mobile performance consistent across languages.
Start with the languages you can maintain. Ten excellent Thai and English pages are more useful than 200 abandoned translations announcing last year's promotion. AI systems answering questions in the searcher's own language make this discipline matter even more—see our comparison of SEO and generative engine optimization for Google, ChatGPT and AI search in Thailand.
The Multilingual Playbook
- One URL Per Language — every language gets its own stable, indexable address; nothing switches on cookies or browser settings alone.
- Genuine Equivalents Only — link two pages with hreflang only when a customer could complete the same task on either one. A Thai spa brand can apply this to its own Chinese-language page: a full-service page translated for Chinese medical-tourism visitors, not a thin summary standing in for it.
- Owned Glossary — one person owns the approved terms for brand names, regulated language, and calls to action, so three translators don't invent three different phrases for the same offer.
- Locale-by-Locale Measurement — track indexed pages, qualified enquiries, and CTA completion separately by language. Low traffic in one language may mean limited demand, weak indexing, or the wrong message—diagnose before translating more pages.
Completeness: what it all comes down to
If there's one word for what actually protects both SEO and customer trust across languages, it's Completeness—not the number of languages offered, just whether the ones you do offer go all the way to checkout.
So here's the question worth sitting with: pick your Chinese or English page right now and actually try to buy something on it, end to end. Does the language hold all the way through, or does it quietly give up somewhere past the homepage?
FAQ
Do I need a Chinese-language site if most of my customers are Thai?
It depends on whether Chinese-speaking customers are a real, growing segment for you. With China as Thailand's top source market for foreign arrivals in 2026, tourism-facing and export businesses in particular should treat it as a real audience, not an afterthought.
Is machine translation good enough for a multilingual website?
For low-stakes content, sometimes. For legal, safety, pricing, or high-value sales content, no—have a human reviewer confirm meaning and context before publishing.
Should I use subdomains or subfolders for different languages?
Either can work technically. What matters more is consistency—pick one structure, such as /th/, /en/, /zh-hans/, and keep it stable so links, sitemaps, and hreflang stay reliable.
What's the most common multilingual SEO mistake?
Auto-redirecting visitors based on guessed language or location, which can hide other language versions from both users and search engines.
How do I know if my Chinese pages are actually working?
Measure enquiries and conversions from that language segment specifically, not just traffic. A page that gets visits but no completed enquiries usually has a gap further down the journey.
If you're not sure whether your multilingual site holds together past the homepage, request a multilingual website architecture review from NAWA—tell us which languages your customers actually use and we'll help you fix URL structure and content ownership before it gets harder to untangle. NAWA's AI Websites work builds the structured, multi-language foundation—clear pages, consistent metadata, and internal links—that keeps every language equally complete.