How should a hotel handle multilingual SEO?
Short answer
A multilingual hotel website should give each language version its own URL (for example /es/ and /de/ folders), link the versions together with hreflang annotations that list every version including itself, and let visitors switch language rather than redirecting them automatically. Translate properly — reviewed by fluent speakers — and keep facts such as prices, policies, and amenities identical across languages. Each language page should canonicalize to itself, not to the English page. Done well, travellers searching in their own language find a page written for them.
By Lodging Engine Editorial Team· Reviewed by Eric Zwanenburg· Last reviewed
Choose a URL structure
Google describes the options:
| Structure | Example | Notes |
|---|---|---|
| Subdirectories | example.com/es/ | Easy to set up and maintain on one domain |
| Subdomains | es.example.com | Easy separation; users may not read "es" as a language signal |
| Country domains | example.es | Clear country targeting; more cost and infrastructure |
For most hotels, subdirectories are the simplest choice. Avoid passing language only in parameters (?lang=es) or switching language without changing the URL.
Set up hreflang correctly
Google's rules:
- Each language version lists itself and all other versions.
- URLs must be fully qualified (
https://…). - Versions should link to each other in both directions.
- Consider an `x-default` for a language selector or fallback page.
<link rel="alternate" hreflang="en" href="https://www.yourhotel.com/rooms/deluxe" />
<link rel="alternate" hreflang="es" href="https://www.yourhotel.com/es/habitaciones/deluxe" />
<link rel="alternate" hreflang="x-default" href="https://www.yourhotel.com/rooms/deluxe" />Don't force language by location
Google advises against automatically redirecting users based on assumed language, and against adapting content by IP address — crawlers may not see all versions. Offer a visible language switcher instead.
Translate for travellers, not just words
- Use fluent reviewers; machine translation alone often misses tone and local terms.
- Adapt practical details: how guests from that market search and what they ask.
- Keep facts identical across languages — check-in times, fees, and amenities.
Canonicals and languages
Translated pages aren't duplicates. Each language page should have a self-referencing canonical plus hreflang. Pointing all languages' canonicals to English can remove them from search. See canonical URLs for hotels.
Common mistakes
- Half-translated pages mixing languages.
- hreflang pointing to redirected or 404 URLs.
- Booking engine only in one language.
- Different prices or policies in different languages.
Checklist
- One URL per language version
- hreflang lists every version, both directions, absolute URLs
- Self-referencing canonical on each language page
- Visible language switcher; no forced redirects
- Translations reviewed by fluent speakers
- Facts identical across languages
Sources
- Tell Google about localized versions of your page — Google Search Central
- Managing multi-regional and multilingual sites — Google Search Central
- How to specify a canonical URL with rel="canonical" and other methods — Google Search Central