Loading...
Haven detects the language of your property the first time you import it (whether by URL or via a connected PMS like Hospitable) and stores it as the property's canonical language. That is the base language of your site: every Haven AI writing assistant — the per-field assistants in your editor, the edit-property AI chat, and the background enrichment that fills in missing details — writes in it, and guest translations start from it.
The setting is per property and per multi-unit site.
Haven supports five languages:
Properties whose language can't be confidently detected — usually because there isn't enough text yet — default to English. You can change this any time from the editor.
Guests see a language picker on your site and can read it in any of the five languages. Haven translates your copy automatically — descriptions, FAQs, site tabs, story and article cards, photo captions, blog posts, offers, the hero headline and eyebrow, the header button, the guest-stories title, each page's search title and description (the listing's, the site's, every page's and every article's), your custom amenities and guide contacts, the guidebook's arrival and departure text (check-in instructions, directions, during-your-stay notes, checkout steps, pet rules), its custom pages, polls and guest forms, and the names of any further guidebooks — and keeps the translations current: when you edit copy, the translations are refreshed, and Haven re-checks every site regularly in case a translation was missed or fell behind.
Translations you correct by hand in a specific language are kept; Haven never overwrites them.
Each language is indexed as a page of its own, so a guest searching in Spanish finds your Spanish page. Your site's own language lives at its plain address; every published translation lives under its own prefix on the same address (/es, /fr, /pt, /de). Each page names all of its versions with hreflang links (plus x-default on the plain address), the sitemap lists every version with the same links, and each version declares its language in the page's lang attribute, its share tags (og:locale) and its structured data (inLanguage). The site's llms.txt ends with a Languages section naming each version and its address, the robots.txt header says which languages the site is published in, and the daily IndexNow ping sends every language version of a page edited recently, not just the original. AI assistants read the same pages as Google, so an answer in French quotes your French copy.
Everything above is shown under Sites → SEO → Languages: which languages are live and at what address, which are still translating, the exact tags the pages emit for each version, and where else each language shows up. Pick any page under Site map to see its address in every language. Translation is on by default; Language settings on the panel opens the switch. With it off, the site is served and indexed in its own language only.
A listing on its multi-unit site's domain is indexed there in the languages the site publishes; a language the site has not published stays at the listing's Haven address, and the Languages panel says so beside it.
Sometimes imported copy arrives in a mix of languages — for example, your description in English but the site tabs imported from your old website in Swedish — or entirely in a language Haven doesn't support yet.
Names (your property name, host names, place names), links, prices and addresses are kept as they are. Copy that a connected PMS keeps in sync is not rewritten, because the next sync would bring the original back; to change it, use the connection's Listing content language setting (see below). Haven support can restore the original text of anything that was rewritten.
Edit listing > Settings > Language
You'll see a single-select list of the five supported languages. The currently selected option is the language your AI writing assistants and enrichment tasks use for this property.
The same section has a Re-detect from property content button that runs language detection over your title, tagline, description, and details markdown and updates the setting accordingly. Use this if you've rewritten major sections of the property in a different language and want Haven AI to follow.
Multi-unit site editor > Settings > Language
Multi-unit sites have their own language setting that controls the AI assistants for the page name, tagline, description, the SEO meta description, and the smart property cluster names you see when grouping properties.
When a multi-unit site is created from a set of attached properties, Haven infers its language from the most common language across those member properties. If the properties are split, the most common one wins; ties resolve to the first property in member order. We deliberately do not recompute this whenever you add or remove a member property — that would surprise you mid-edit. The Settings panel includes a Re-infer from properties button if you want to refresh it explicitly.
If a listing is connected to Hospitable, Guesty, Lodgify, Hostfully, or Airbnb, a separate Listing content language control lives under that connection on the Integrations tab and starts collapsed. That setting decides whether incoming PMS copy is mirrored verbatim or translated on the way in. It does not change this AI-generation language setting, and your site is still translated into all five languages for guests either way. A Request another language link under it files a request for a new guest language on the Feature Board.
Setting a non-English language conditions every AI prompt Haven sends on this property's behalf. That includes:
Switching the language yourself does not translate your existing copy on the spot, and it does not change guest-visible reservation emails (those follow the guest's locale, not the property's). Guest translations are regenerated from your copy in the background. If you want your existing copy in the new language, edit the fields directly or use an AI assistant in the editor.
When you switch the property or multi-unit site language, Haven shows a confirmation modal before saving. You can cancel from the modal. Keep this setting on the language you actually write your property in.
New to Haven?
Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.
Free to build · No credit card · Private until you publish