A bilingual website for international guests: more than translation●

A family in Manchester is looking for a hotel in Bodrum for July. They open your website. The home page is in English, but the rooms page switches back to Turkish. Half the labels on the booking form are translated, and the cancellation policy exists only in Turkish. They close the tab and find the same hotel on an OTA, where you pay the commission. Or they book somewhere else entirely.

Every season, Bodrum welcomes a great many guests who do not speak Turkish. Whether you run a hotel, a restaurant, a charter boat or a clinic, a website that reads properly in at least two languages is no longer a nice extra. But bilingual does not mean running your Turkish text through a translation tool. Here is how to get both the content and the technical side right.

Adapt, don't just translate

Translate Turkish copy word for word and you usually get English that is correct but cold. "We are at your service with our unique view and smiling staff" reads like a brochure from another decade. International guests want specifics. Can I see the sea from the room? How long is the walk to the beach? When does breakfast finish? How do I get here from the airport?

Good adaptation starts from what the reader expects. Something that matters to a Turkish guest, such as live fasıl music on Saturday night, may be secondary for a British family, who care more about a children's menu or quiet hours by the pool. The structure can stay the same across languages while the emphasis shifts. That is why the final read should always come from a native speaker.

Currency, dates and distances are part of the job too. Showing prices in euros or pounds alongside lira, writing "14 July" rather than "14.07", and saying "a ten-minute drive from Bodrum town" instead of a bare kilometre figure all make a guest feel looked after.

One address per language

The biggest technical decision is how the language versions are structured. Some sites switch language with a button on the same URL. Others read the visitor's browser language and redirect them automatically. Both cause trouble.

Google's guidance on multi-regional and multilingual sites recommends a separate URL for each language version and advises against automatically redirecting users based on their perceived language, because it can stop both people and search engines from seeing all of your versions. A Turkish guest living in Germany should not be locked out of the Turkish pages just because their browser is set to German.

In practice that means paths such as yourdomain.com/tr and yourdomain.com/en, with a clearly visible language switcher on every page that takes the visitor to the same page in the other language, not back to the home page.

Telling search engines about your versions

Once each language has its own address, search engines need to know which pages belong together. That is the job of hreflang annotations. Google's documentation on localized versions explains how they help it identify the language variants of the same content, and suggests a default page for visitors whose language does not match any of your versions.

You do not need to write this markup yourself, but it is a fair question to ask whoever builds your site: "Do my English pages show up separately in Google?"

Translate the small things, too

The most common failure on bilingual sites is that the main copy gets translated and the small pieces are forgotten. Those small pieces are exactly where guests get stuck:

• Navigation and footer links
• Form labels, error messages and the submit button
• Booking confirmation emails and automatic WhatsApp replies
• Cancellation, refund and privacy terms
• Image captions and page titles
• The Google Maps link and directions text

A guest who fills in an English form and receives a Turkish confirmation email cannot be sure the booking went through. So they message you on WhatsApp, and the front desk loses ten minutes.

The same goes for everything outside the website. Write your Google Business Profile description in plain English, reply to English and German reviews in English and German, and make sure that when someone taps "Message us on WhatsApp", they are greeted in a language they understand. Saved replies in both languages for location, parking, transfers and cancellations save real time on a busy August night.

How many languages?

Adding a language is easy. Keeping it current is not. A half-finished Russian or German version can do more harm than having none. For most Bodrum businesses, Turkish and English are the right place to start. If you are considering a third language, look at last season first: the languages your bookings and Google reviews arrived in tell you what you actually need. Then ask honestly whether someone can keep that language up to date.

The bilingual site checklist

Test your site as a guest would:

1. Each language version has its own URL.
2. The site does not redirect visitors based on browser language.
3. A language switcher is visible on every page and links to the matching page.
4. Page titles and descriptions are written separately for each language.
5. Forms, error messages and confirmation emails follow the chosen language.
6. Cancellation and privacy terms exist in both languages.
7. A native speaker has read the English copy.
8. Prices, dates and distances are written the way international guests expect.
9. WhatsApp saved replies exist in Turkish and English.
10. New content is always published in both languages at the same time.

The last point may matter most. A bilingual site is not a one-off project; it is a habit you keep.

If you would like to see how your site looks to an international guest, we can go through your pages together on a free discovery call. Winter is a good time to work out what should come first.