Bilingual SEO for Thai Ecommerce: How to Rank in Thai and English Without Competing With Yourself

A store that sells in both Thai and English is, from Google's point of view, running two websites that happen to share a product catalogue — and most of the SEO advice written for single-language stores quietly assumes that problem away. The result is a specific, recurring failure mode: a bilingual store that ranks fine in one language and barely exists in the other, not because the content is worse, but because the technical and strategic setup never actually treated the second language as its own audience.

Translating your English keywords is not Thai keyword research

The most common mistake isn't technical — it's assuming that whatever ranks well in English will rank well in Thai if you just translate it. Thai shoppers frequently search in patterns that don't map cleanly onto an English query at all: mixed Thai-English phrases ("รองเท้า running"), brand names spelled multiple different ways in Thai script, and category terms that a literal translation gets technically right but that no one actually types into Google. A product page optimised around a translated version of the English keyword can be fluent, accurate Thai, and still be invisible — because it's answering a query nobody is asking.

Real Thai keyword research means researching Thai search behaviour directly, in Thai, rather than starting from an English keyword list and translating it. That's slower than running a translation pass, and it's the difference between the Thai version of a page actually ranking versus just existing.

hreflang is the single easiest thing to get wrong

When a site runs Thai and English versions of the same page, hreflang tags tell Google which version to serve to which searcher. Get this wrong and one of two things happens: Google indexes the wrong language version for a market, or — more commonly — it treats the two versions as competing duplicate content instead of two audience-specific versions, and neither ranks as well as it should. This is a quiet failure mode: nothing breaks visibly, no error appears in Search Console by default, the site just underperforms in one language indefinitely while everything else looks fine.

The setup that actually works reliably:

• Every page needs a self-referencing hreflang tag, not just a tag pointing to the other language — a page that only declares its counterpart but not itself is a common and easy mistake to make.
• The URL structure has to be consistent — a stable locale pattern (a prefix like /en/, or a subdomain) that Google can rely on, not a structure that changes page to page.
• hreflang pairs have to be reciprocal. If the Thai page points to the English version, the English version has to point back. A one-way link is treated as invalid by Google and effectively ignored.
• Use x-default for a fallback version when neither language tag clearly matches the searcher's locale.

Two versions of the same page are not automatically duplicate content — but they can become it

Google is generally capable of understanding that a Thai and English version of the same product page serve different audiences and shouldn't be penalised as duplicates. Where this breaks down is when the setup gives Google reason to doubt that: missing or broken hreflang, a URL structure that looks accidental rather than intentional, or — a subtler version of the same problem — a Thai page that's mostly untranslated boilerplate around a handful of translated words, which reads to a crawler as thin, near-duplicate content rather than a genuinely separate page worth ranking on its own.

Machine-translated pages rank worse, and shoppers notice first

A page translated by machine translation and left unedited tends to be long enough and technically correct enough to pass a casual glance, while still reading as slightly off to a native speaker — word order borrowed from English, formal register in places where natural Thai copy would be more direct, vocabulary that's accurate but not what a Thai shopper would actually say. This costs conversion before it costs ranking, but it costs ranking too: thinner engagement, higher bounce, less time on page — signals that feed back into how Google evaluates the page over time. A shorter page written by someone who actually writes Thai outperforms a longer, mechanically translated one on both fronts.

Content strategy has to fork, not just translate

The two languages often aren't even competing for the same intent. An English-language product page on a Thai store is frequently serving a different kind of searcher than the Thai version — an expat, a regional buyer, someone comparing options before deciding whether to buy locally at all — while the Thai version is serving someone already deep in a specific, local purchase decision. Treating both as the same content with a language swap misses the chance to write each version for the searcher actually reading it: different comparison points, different trust signals, sometimes different products entirely if regional availability differs.

Where this shows up in Search Console

A handful of Search Console signals reliably point at a bilingual SEO problem rather than a general one:

• One language's pages show far more impressions than clicks, disproportionate to the other language — often a sign Google is serving the wrong version to a chunk of searchers.
• Both language versions show up for very similar queries in the Performance report, competing with each other instead of splitting distinct search intent.
• The International Targeting report (or hreflang errors in third-party crawl tools) flags a non-reciprocal or missing tag — this is worth checking specifically, not just assumed correct because nothing looks obviously broken on the page.

A practical setup order

1. Get the hreflang implementation correct and reciprocal first — before anything else, since a broken foundation undermines every other fix layered on top of it.
2. Do keyword research separately in each language, starting from actual Thai search behaviour, not a translated English list.
3. Write Thai content for a Thai reader, not as a translation pass over finished English copy — ideally by someone who writes Thai natively, reviewing for register and phrasing, not just accuracy.
4. Check Search Console's International Targeting and Performance reports periodically for the specific signals above, since bilingual SEO problems rarely announce themselves any other way.
5. Treat the two languages as two audiences with overlapping but distinct intent, not one piece of content wearing two languages.

None of this replaces doing SEO well in either language individually — it's the layer that decides whether doing it well in both languages actually compounds, or quietly cancels itself out.