Multilingual content

Reynt is multilingual end to end. You pick the languages your business supports, then every text you author — listings, catalog labels, website content, blog posts, and email templates — can be written once per language. The storefront serves each visitor their language, and guest emails and documents go out in the language the guest chose.

Choose your languages

Open Settings → Languages to set the language set for your account.

• Supported languages — the languages operators can translate content into. Common presets (English, German, French, Italian, Spanish, Dutch, Hungarian, and others) appear in the dropdown, and you can type any BCP-47 tag (for example pt, pl, cs, sv).
• Default language — the fallback used for outgoing emails, invoice and booking PDFs, AI-generated content, number formatting, and any field that hasn’t been translated yet. It must be one of your supported languages.

If a translation is ever missing for a language, the storefront falls back to the default language rather than showing a blank — so the default language should always be your most complete one.

Formal vs informal German

German has two register variants: de (informal) and de-formal (formal). Pick one — both render under the same /de/ storefront URL, so you can’t enable both at once. The same formal/informal option is available for other languages that need it.

Guardrails when you change languages

Two changes are confirmed before saving because they affect existing content:

• Changing the default language — content is keyed by the current default, so after switching, any field missing a value in the new default may render blank until you translate it.
• Removing a supported language — content already translated into that language is hidden from the storefront, but nothing is deleted. Re-add the language later to restore it.

You may also see non-blocking warnings when a supported language has no email template (booking emails fall back to the default language) or no storefront route (visitors picking it see the English storefront until support is added).

What is translatable

Nearly every operator-authored, customer-facing text carries a value per language:

• Listings — title, excerpt, description, amenities/prices/discount text, customer info, SEO title and description, and image labels.
• Catalog — amenity, attribute, distance, tag, and property-type labels, plus place names and descriptions.
• Website content — CMS page titles, slugs, content sections, menu labels, and blog posts.
• Notifications — per-language email and notification template texts (see Settings → Notifications).
• Settings — storefront SEO title and description, contact address, booking-page messages, referrer options, and partner-logo alt texts.

Editing per language

Wherever a field is translatable, the editor shows a language tab per supported language — fill in each tab, or leave a language empty to fall back to the default. Fields also carry a small AI button that can generate or translate the text across your languages; see Content generation and translation.

To find everything still untranslated in one place, use the Translations page.

Storefront behavior

Once you support more than one language, the storefront becomes fully localized:

• Language-prefixed URLs — every page lives under a language prefix (/en/…, /de/…), and a language switcher in the header lets visitors change language.
• Automatic first-visit language — a new visitor is matched to their browser language (falling back to your default), and their choice is remembered for return visits.
• SEO — each page emits hreflang alternates, a canonical URL, and appears in a per-language sitemap, so search engines index every language correctly.

Customer communication language

Each booking records a communication language, so the guest’s confirmation emails, invoices, and booking PDFs are sent in the language they used. You can change it on the booking (or booking request) under Communication language, and each customer record carries a Language field used for operator-created bookings. Owner and internal operator emails always use your default language.