Web Design30.09.2026

Multilingual Hotel Websites: Setting Up English, German and Russian Correctly

International guests want to book in their own language, but installing a translation widget does not make a site multilingual. This guide explains how to set up English, German and Russian versions the way Google recommends, and how to make each language actually bring in bookings.

Our guide to what a hotel website should look like gave multilingual setup a single paragraph; this article is the detailed version. English, German and Russian are in the title because they are the trio hotel owners ask us about most often. But your own guest data, not general assumptions, should decide which languages your site needs.

1. Choose languages from guest data, not guesses

Every new language means translation, maintenance, guest messaging and measurement. Build your list from the data you already have, not from what the hotel next door offers:

Two traps: a country is not a language; a visitor from Germany may browse in Turkish, one from Switzerland in French. And if you have no page in a language, you will not see direct bookings in it either. Read the sources together and start small; three languages done well beat eight done halfway.

2. Give every language its own URL

Google is clear: language versions should not switch on the same address via cookies or browser settings; each language needs its own URL. The four structures Google compares:

For a hotel, subdirectories usually make the most sense: /en/, /de/, /ru/. You are targeting a language, not a country; a German-speaking guest may just as well come from Austria or Switzerland. Google also recommends words in your audience's language in URLs, transliterated where needed. Cyrillic URLs need percent-encoding, so a slug like /ru/nomera/ is more practical for Russian pages.

3. Set up hreflang correctly

hreflang tells search engines which pages are the other-language versions of a page, so Google can show guests the one in their language. But Google detects a page's language from its visible content, not from hreflang or the lang attribute: hreflang is a routing signal and will not rescue a poor translation. Google's rules for hreflang on a hotel website:

  1. Self-reference: each version lists itself as well as all the others.
  2. Reciprocity: in Google's words, if two pages don't both point to each other, the tags are ignored. Missing return links are one of the most common mistakes.
  3. Fully qualified URLs: include https://; relative paths such as /de/rooms don't count.
  4. Correct codes: ISO 639-1 for language (en, de, ru), ISO 3166-1 Alpha 2 for region. A region alone is invalid, and the United Kingdom is en-GB, not en-UK. If content doesn't change by country, just use de; it covers Germany, Austria and Switzerland together.
  5. x-default: the fallback when a visitor's browser language matches no version; for hotels usually the English version or a language selection page.
  6. Canonical in the same language: with hreflang, Google asks for a canonical page in the same language. Don't point the German page's canonical at the Turkish homepage.

For Yandex, the sitemap is not enough

For Google, putting the annotations in the head, in HTTP headers or in the sitemap is equivalent. But some Russian-speaking guests use Yandex, which supports hreflang yet states that it no longer supports sitemaps for language versions and recommends on-page markup. The safest route is to put the tags in the head of every page.

4. Why an auto-translate widget is not enough

Most widgets that swap text in the browser don't create a separate URL; the “German version” is really a script running on top of the Turkish page. Google wants a crawlable URL for each language, and without one hreflang is impossible.

On machine translation, Google's position targets quality, not the method. The scaled content abuse definition in its spam policies covers generating many pages through automated transformations such as translating when they add little value for users. In June 2025 Google removed a section from its documentation about blocking automatically translated pages with robots.txt. What works in practice: machine translation as a first draft, a native speaker reading the text, and a glossary for room names, cancellation terms and payment steps. Don't translate only the menu; Google recommends a single language for content and navigation on each page.

Guests don't count how many languages your site speaks; they judge how much trust the page in their own language gives them.

5. Localise the booking flow, room names and policies

Everything a guest reads before paying should be in their language:

6. Language switcher: offer, don't redirect

Redirecting everyone from Russia to /ru/ by IP may look clever, but Google advises against redirecting on a guessed language and against IP location analysis. Googlebot's default IPs also appear to be US-based and it sends no Accept-Language header, so automatic redirects can hide your other versions from Google. Instead:

7. Local signals: contact and payment

Google lists currency, addresses and phone numbers alongside language as signals of who a site is for. For guests, these details answer “will this hotel understand me?”:

The goal is for international guests, too, to finish booking on your site rather than an OTA; we covered channel mix in our article on direct bookings.

8. Measure each language separately

Common mistakes on multilingual hotel websites

Turning a multilingual site into a sales channel

A well-built multilingual hotel site has clear parts: languages chosen from data, subdirectories, reciprocal hreflang, text checked by a native speaker, a booking engine in the guest's language, and per-language measurement. Next comes search visibility in each language, including researching keywords per language rather than translating them; see our hotel SEO guide. At our Studio we build these pieces together for hotel websites; examples are on our Work page.

Sources

Ready to grow your brand?

Let's bring strategy, design, performance and content together — under one roof.

Get a Free Quote →