Be ready for visitors in any language
Before the season starts, make your business answer AI assistants in your visitors’ languages, translations included, facts untouched.
Outcome: a tourist’s assistant asks about you in German, French, or Swedish, and gets your real services and hours, in that language, from translations you never had to write. In place before the season, not during it.
You need: a Pro plan (translation is the headline Pro feature) and a published profile you’re happy with in your own language.
Step 1 — Get the original right first
Translations inherit their quality from the source. Before enabling anything, tighten your profile in your own language: services named plainly, descriptions concrete, policies filled in. The inquiries playbook steps 1–3 double as the checklist here.
Step 2 — Pick languages like a local, not a linguist
Enable the languages your actual visitors think in. A Helsinki business might pick English, German, and Swedish before anything else; a coastal one might add French and Italian. You can enable more later; each is a switch, not a project. CoreLoop translates your name, tagline, descriptions, category, policies, and every service, and regenerates them automatically whenever you edit the original.
Step 3 — Trust the guardrails, but know them
Three things you don’t have to manage, listed so you know they’re handled:
- Facts (phone, email, hours, prices) are never translated, no mangled numbers.
- A language is served only when its translation is complete, no half-translated business, ever.
- An asker in a language you didn’t enable gets your original language, no errors, no gaps.
Step 4 — See it as an agent sees it
Once translations are generated, every channel serves them: agent queries in an enabled language get that language, the directory shows you in the searcher’s language, and your page carries the annotations search engines expect. Ask a colleague (or an AI assistant, in an incognito moment) about your business in an enabled language and read what comes back.
Step 5 — Keep editing in your own language
That’s the whole maintenance plan. Edit the original when things change; regeneration cascades to every enabled language on its own. There is no “retranslate” chore to remember.
Done when
An agent query in each enabled language returns your translated content, and your season’s first foreign-language inquiry lands in the inbox.
Deeper detail: the Languages doc, and the story version in One profile, eighteen languages.