Translate Website to Thai: Line Breaking & Typography

If your brief says “translate the website to Thai,” stop treating Thai as a string swap into a Latin-first theme. Thai on the web is a line-breaking and typography problem: there are no spaces between words, tone marks sit above and below consonants, and English-style truncation will split syllables in the worst visual sense.

This article is a launch guide for a Thai (th) website version: locale choice, script and wrapping, crawlable URLs, checkout QA, MTPE vs human review, SEO pitfalls, and a checklist you can actually run.

What does it take to translate a website to Thai beyond swapping strings?

Beyond CMS fields, you need a pipeline that wraps Thai with word-boundary-aware line breaking; fonts and line-height that leave room for tone marks and vowel glyphs; a politeness-particle policy for customer-facing copy; a glossary for English tech loanwords; a crawlable th URL whose body is actually Thai script; and keyword research in Thai—not Latin transliteration pretending to be a Thai SEO strategy.

Questions this guide answers

• What does it take to translate a website to Thai beyond swapping strings?
• Which Thai locale or regional variants should you choose?
• What script, typography, and layout issues are unique to Thai?
• How should URLs, hreflang, and indexing work for a Thai site version?
• What onboarding and checkout nuances matter in Thai?
• Should you use AI translation, MTPE, or human review for Thai?
• What SEO mistakes specifically hurt Thai pages?
• How do you launch and measure a Thai website version?

Quick answer: translate your website to Thai the right way

A durable Thai launch looks like this:

1. Treat line breaking as a product feature. Latin-first CSS that wraps mid-cluster or refuses to wrap is a quality failure, not a CSS footnote.
2. Ship th (often th-TH) as its own crawlable URL—not a cookie-only switch.
3. Prototype heroes, pricing cards, tables, and emails with real Thai copy so clipped tone marks and bad wraps show up before you translate the help center.
4. Never truncate by raw character count the way you might for English; it splits Thai unpredictably.
5. Research Thai-script queries, then write titles and H1s in Thai script—not romanization alone.
6. Add reciprocal hreflang, same-language canonicals, and sitemaps before you scale.

CSA Research’s survey of 8,709 consumers in 29 countries found 76% prefer buying with information in their own language and 40% will never buy from websites in other languages. That still holds when some Thai speakers also read English: checkout, invoices, and support are where an English-only journey loses the sale. Google’s helpful-content guidance favors people-first pages; a Thai nav around English body copy is a weak locale. For market-versus-language strategy, read how international SEO differs from multilingual SEO.

Choose the right Thai locale

Most teams should ship th with a Thailand-oriented th-TH URL if that is the first commercial market. That is a reasonable first release. It is not a license to mix highly royal-formal particles, chat-casual particles, and leftover English UI in one file and call it “the Thai locale.”

Thai for websites is one written standard for most product UI. Regional spoken variation exists, but your first decision is register: polite particles that fit customer-facing product and support, without sliding into bureaucratic or overly intimate tone. Put audience and particle policy in the brief before anyone opens a file.

Overseas Thai readers exist, but baht, address formats, and legal pages still follow the market you sell in. Do not treat romanized tourist-Thai or bilingual Bangkok-office English as the source of truth for a Thailand storefront.

Also decide names, addresses, and phone numbers. Forms that reject Thai script or force ASCII-only names will fail after the strings look “translated.” Document which fields must accept Thai script.

English loanwords appear constantly in tech. Glossary whether you keep English feature names, transliterate them, or use Thai renderings. If you do not, every vendor will mix three spellings of the same button.

Thai script, typography, and layout nuances

Thai does not put spaces between words. Word boundaries are linguistic, not a space character. That single fact reshapes line breaking, truncation, search highlighting, and headline design.

Tone marks and vowel glyphs sit above and below consonants. Tight line-height clips them. A font stack that only tested English will fall back to a face that makes marks collide or disappear at small sizes.

Layout rules that prevent launch-week screenshots:

• Use Thai-aware line-breaking strategies. Latin-first CSS often wraps mid-syllable cluster awkwardly or refuses to wrap at all.
• Prototype key screens with real Thai copy—especially marketing heroes, pricing cards, comparison tables, and support macros. These are design-heavy templates; wrapping risk is highest here.
• Increase line-height versus a Latin-first theme so marks have vertical room.
• Allow buttons to wrap; do not shrink type to keep a one-line English CTA.
• Ship production fonts with Thai coverage in UI, email, and PDFs.
• Never truncate by raw character count designed for English. Ellipsis at N characters will cut inside a word with no space to hint that you did.
• Headline stress test: take your three longest English H1s, translate them to Thai, and drop them into the production hero. If marks clip or lines refuse to wrap cleanly, fix the design system before you translate the help center.

Dates and numbers are part of the layout contract. Thailand typically expects day-month-year in running text (Buddhist Era dates appear in some official and legal contexts—decide per page type), number grouping that matches the market, and baht formatting when you actually sell in Thailand. Sorting Thai lists as if they were English ASCII is not a collation policy.

Cadence matters. Politeness particles shape customer-facing tone more than vocabulary lists. English CTAs are often abrupt; Thai marketing copy can be warmer without becoming bureaucratic—while payment and error copy stay plain.

Because wrapping risk is high, localize design-heavy templates first, then expand into long-form help once the system survives Thai headlines.

Crawlable URLs, hreflang, and indexing

Google recommends different crawlable URLs for each language or region version rather than cookies or browser language alone. Google determines page language primarily from visible content—so a translated nav around English body copy is a weak Thai version. Give Thai its own folder or host pattern (/th/, /th-th/) and keep that pattern consistent across templates, analytics, and internal links.

Hreflang annotations must be reciprocal across the alternate set you declare. Each locale URL should carry a clear canonical that prefers the same-language preferred URL when duplicates exist. Do not canonical a Thai page to its English equivalent.

Bing Webmaster Guidelines emphasize crawlable, useful content and clear site structure across markets. Google advises against automatically redirecting users based on assumed language or location; offer a visible selector that links to the Thai URL instead. IP-guessing “Thailand → /th” traps travelers, VPNs, and crawlers.

URL policy and on-page policy can differ: you may keep ASCII slugs for operational reasons, but titles, H1s, and body copy should be Thai script. Latin transliteration on the page is not a Thai language version. If you percent-encode Thai slugs, redirect consistently; do not publish two competing Thai URLs without a canonical.

Research Thai-script queries. Romanization and English head terms are not enough for a serious Thai market page set. That is research, not a ranking promise.

Onboarding, trust, and checkout in the target language

Thai trust pages do more work than a translated feature list. Sites that sell to Thailand typically need privacy, terms, and (where relevant) payment and after-sales copy that read as real pages, not leftover English templates. That is not a ranking tactic; it is what users look for when they decide whether a checkout is legitimate. Treat those pages as first-class localization.

Practical Thai conversion checks:

• Homepage, ads, and product UI use the same particle register.
• Forms accept Thai script for names and addresses, or they explain why a Latin field is required.
• Cookie and consent strings are reviewed in the actual banner—these run long and wrap badly without Thai-aware breaking.
• Pricing, invoices, and baht language match the market you claim to serve.
• Support macros and transactional email keep Thai script and particles; a “safe ASCII” email template is a leak.
• Error messages name the fix rather than a polite empty apology.
• Mobile: people may search or fill some fields in Thai script or Latin depending on the keyboard—QA both, but do not ship romanized UI as the official voice.
• Truncation QA on checkout line items and address previews—character caps that “worked” in English will mangle Thai.

You do not need every blog post on day one. You do need homepage and product explanation, authentication, pricing, checkout/billing, privacy basics, support entry points, and the legal pages your market expects.

AI, MTPE, and human review for this language

Should you use AI translation, MTPE, or human review for Thai? Use risk to choose the workflow—not tool branding:

• Raw machine translation: fine for internal drafts only. Models mishandle particles, mix formal and chatty tone, and produce Thai that is grammatical and still wrong for a product voice.
• MTPE (machine translation + post-editing): a solid default for many product and support pages when the glossary locks product nouns and loanword policy and a native pass checks wrapping in the real UI—not only in a CAT tool.
• Human translation / brand editing: homepage, pricing, campaigns, cookie/consent, and any legal-adjacent page.

A practical review loop for Thai:

1. MTPE draft against the glossary (particles and loanwords locked).
2. Brand editor pass on homepage, pricing, and key landing pages.
3. Product linguist pass on errors, billing, and dynamic UI—especially truncation and button wraps.
4. Staging QA in Thai at mobile widths, including email and PDF renders and clipped tone marks.
5. Add a publishing check that flags leftover English body copy or romanized-only Thai on th URLs.

Low-quality machine-only Thai pages can look complete in a CMS while still failing users and people-first helpful-content expectations.

Thai-specific SEO pitfalls

Thai searchers look for language they can read. Translating English head terms word-by-word, or ranking Latin transliteration as the Thai title, misses how people actually search. Do Thai-script keyword research, then write titles and H1s that sound like Thai results pages.

Localize titles, meta descriptions, and headings per Thai URL. Do not reuse one English metadata set across locales.

Mistakes that specifically hurt Thai pages:

1. Latin transliteration treated as the Thai language version on titles or body copy.
2. Boilerplate-only translation — chrome Thai, body still English.
3. Clipped tone marks in production fonts, email, or PDFs.
4. English character-count truncation that splits Thai with no spaces.
5. Cookie-only language switches that hide the Thai URL from crawlers.
6. Broken hreflang (missing return links).
7. Automatic geo redirects that trap users and bots.
8. Thin MT-only locales that fail helpful-content expectations.
9. Uncontrolled English loanwords so the same feature has three names in search and UI.

Fix wrapping, fonts, and architecture before you scale content volume. Tooling should enforce the process—not invent ranking promises.

Launch checklist

Use this checklist when you are ready to ship Thai:

• Locale matrix approved (th / th-TH) with particle and loanword policy documented
• Crawlable Thai URL pattern chosen and shared with engineering
• Primary screens prototyped with real Thai copy (heroes, cookies, tables, checkout)
• Thai-aware line breaking verified (no mid-cluster wraps, no wrap refusal)
• Priority templates translated with reviewed main content—not chrome only
• Titles, descriptions, and Open Graph localized per Thai URL, in Thai script
• Font glyph coverage verified in UI, email, and PDFs (tone marks and vowels)
• Line-height and truncation checked on mobile cards and buttons (no character-count ellipsis)
• Dates, numbers, currency, and form field rules checked
• Privacy / terms pages reviewed as first-class content
• Language selector links to crawlable alternates (no forced redirect)
• Canonical policy verified per locale (same-language preferred URL)
• Reciprocal hreflang generated
• XML sitemaps list Thai URLs
• Glossary and review workflow live for ongoing English source updates
• Romanized-only / leftover-English detector enabled on th URLs
• Search Console / Bing coverage checks scheduled for the Thai URLs

Where GlotEO fits

Thai is a strong fit for translation memory: product nouns and loanword spellings recur, and they must not drift on the next English drop. Glossary and memory in the website localization platform keep particles, loanwords, and feature names stable while layout-tested copy ships. Pair that with multilingual SEO tooling so Thai URLs, hreflang, and metadata stay reviewable as you expand. Compare GlotEO pricing and plans when you scope the first th release, or start from a broader website translation workflow if you are still choosing languages.

Explore GlotEO website localization when Latin-first truncation and unmarked MT drafts are no longer a safe way to ship th.