Planning a bilingual website

A bilingual website needs more than a language switch. Decide which pages need Thai and English versions, what information should be adapted for each audience, and who approves it. Page counts depend on the agreed counting method: six topics translated into both languages can mean twelve pages when each language version counts separately. This article offers a planning method, not a claim about the page allowance in every Exploera plan.

Separate topics, language pages and layouts

These describe different parts of the workload. A topic is what the business wants to explain. A language page is the version someone visits. A layout is the presentation structure that may be reused. Sharing a layout does not remove the work of translating, reviewing and publishing each version.

Content topic: one garden-design service
Language pages: one Thai version and one English version
Layout: a service presentation that may support several records
Custom work: assess the design and interaction required, rather than translation length alone

A sample sitemap and a total across both languages

The fictional service business below has six topics: six Thai pages and six English pages, twelve in total. If an example agreement sets a limit of twenty pages across both languages, eight pages remain under this counting method. That does not mean twenty per language. The agreement must also explain how lists, details and system-generated pages count.

Home: 1 Thai + 1 English = 2 pages
About: 1 Thai + 1 English = 2 pages
Two core services: 2 Thai + 2 English = 4 pages
Frequently asked questions: 1 Thai + 1 English = 2 pages
Contact: 1 Thai + 1 English = 2 pages
Total: 6 Thai + 6 English = 12 pages; a planning example, not a plan entitlement

Adapt context, not just individual words

Keep a shared set of business facts such as service names, scope, prices and contact details. Then adapt the explanation to what each audience knows and asks. English-speaking visitors may need more context about service areas or enquiries. Agree consistent spellings for brand and service names.

Create a glossary for approved brand names, services and terminology
Make currencies, measurements, dates and time references clear
Confirm any market-specific price, term or service-area differences before translating
Include menus, buttons, form errors, captions and contact instructions
Decide what language links should do when a translation is not ready

Pair URLs and assign ongoing ownership

Google recommends separate URLs for language versions and a way for visitors to choose their language. Pairing pages helps a team check that the language switch leads to equivalent content instead of always returning to the homepage. This is an organisational approach, not a search-ranking guarantee.

Example URL pair: /services/garden-design and /en/services/garden-design
Track each version as draft, in review or ready for publication
Name the source-content owner, translator and final approver
When prices, scope or contact information change, review the other language too

Agree the scope and check the real pages

Record page counts by language, reusable layouts, custom work and translation responsibilities before committing to delivery. For Exploera, confirm the actual scope against the selected modules, content and presentation. A planning example does not replace a proposal.

Explain how news, articles, products and individual detail pages count
Distinguish system fees, custom design, translation and media production in the proposal
Check actual mobile and desktop output with Thai marks and longer English copy
Test navigation, language links, forms and message recipients
Review each language title, description and URL; do not publish placeholder translations

Plan the next step

Source and editorial note

Google Search Central: multilingual websites

Prepared by Exploera with AI-assisted drafting and source checks. Page counts and the business example are illustrative; service scope follows the agreed proposal. Illustration generated with AI.