Translations let you offer your ThinkWeb website and your booking flow in additional languages, so a guest can find you, read about your property, and book a stay without ever landing on a page they can't read.

It's included at no additional cost. Ready to set it up? See Setting Up Translations.

For ThinkWeb clients with the integrated online booking engine, Translations covers the whole guest journey: your website pages and the booking flow. A Japanese-speaking traveler can browse your site in Japanese and complete their reservation in Japanese.

Any text field that can appear on your website or in your booking engine is translatable. In the Translations module, that content is grouped into Area, Hotel, Items, Packages, Pages, Rate Types, Room Types, Rooms, and ThinkWeb Configuration. If a field shows up in the module, you can translate it.

Automatic translation is the starting point. Every translatable field gets an automatic translation as soon as you add a language. You don't have to write anything to go live in a new language.

You can override any individual string. Overrides work one field at a time, so you can rewrite a policy or a room description and leave the rest automatic.

Your original content is the source of truth. Translation flows in one direction only. Editing a translation never changes your original text.

Publishing is required. Translations appear on your live site once you publish from the ThinkWeb module.

Automatic translations stay current. Manual overrides get flagged. When you edit your original text, automatic translations update on their own. Anything you rewrote by hand is marked stale, so you know to revisit it.

Two ways:

Every language you translate into is indexed, so a Spanish-speaking traveler searching in Spanish can find your Spanish pages and book direct. For properties drawing international guests, that's a real discoverability advantage, not just an accessibility one!

Twelve languages are available, and there's no limit on how many you add:

Note the regional pairs. Wording and idiom differ between Spanish and Spanish (Mexico), or French and French (Canada), so choose the variant that matches your guests, or add both.

Your property name. It's your brand. It should be recognizable to guests when they arrive and when they see the charge on their credit card statement.

Your physical address. An address needs to work for mapping apps, drivers, and postal service in the country your property is actually in. Translating it would make it harder to use, not easier.

Guest emails and text messages. Confirmations, pre-arrival messages, and all other guest correspondence send in whatever language your templates are written in. This one surprises people, so it's worth knowing up front: a guest who books in Japanese will still receive your confirmation email in the language your template uses.

Internal-only fields. Fields like "Notes for Staff" never appear guest-facing, so they aren't offered for translation.

Automatic translation is designed to be good enough to publish for most content, and that's the point of the feature. It isn't a replacement for professional translation. For your policies, terms, and anything a guest could dispute later, we recommend a native speaker review before you publish. Where you want different wording, the manual override is there for you.