Smoobu guide
Multilingual websites for European portfolios
hreflang, localised pricing and why translation widgets do not work. The unglamorous detail that decides cross-border performance.
The widget problem
A translation widget renders text in the browser after the page loads. Search engines index what the server sends, which means the translated version usually does not exist as a crawlable page at all. You get no ranking benefit in the target market whatsoever.
Guests notice too. Machine translation reads as machine translation, and it reads that way at precisely the moment someone is deciding whether to send money to a stranger in another country.
What a proper multilingual build involves
One indexable URL per language per page, hreflang annotations across every pair including x-default, locale-correct currency and date formatting, and content written for the market rather than translated at it.
It is more work than a widget and it is the difference between competing in Germany and merely being visible there. Smoobu itself supports multilingual guest communication well, so the operational side is already handled.
- Directory-based locales (/de/, /fr/) with consistent structure
- hreflang in the head or the sitemap, applied to every page
- Currency display matching the locale, not just the browser
- Native-speaker review of anything a guest reads before paying
Which languages are worth it
Fewer than people think. Each locale doubles the content maintenance burden, and a half-maintained locale is worse than none.
Start with the one market your booking data says is already trying to reach you. Add the second only once the first is earning. For most UK operators with Smoobu that is German; for Alpine operators it is frequently English.
Questions people actually ask
Straight answers.
Do I need separate pages for each language?
Yes. A translation widget produces no indexable page, so it earns no rankings in the target market.
Directory-based locales with hreflang are the standard approach and the one we build.
How many languages should I support?
Start with one beyond English, chosen from your actual booking and traffic data.
Each additional locale is an ongoing maintenance commitment, not a one-off translation cost.
Does Smoobu handle the multilingual side?
It handles guest communication in multiple languages well. The multilingual website is a separate build decision.
That split is worth understanding early, because it is where operators often assume the platform has done more than it has.
Back to the main page
Smoobu website design
The full picture on building a direct booking website around Smoobu — integration routes, what changes, and what it costs you not to.
