One profile, eighteen languages
Here’s a small scene that happens more every season. A visitor lands in your city, opens their phone, and asks their assistant, in German, or French, or Polish, to find a good place for exactly what you do. The assistant goes looking. The question is not just whether it finds you. It’s whether, having found you, it can read you.
Most local businesses exist online in one language. Fair enough: nobody has time to maintain a website in five. But an AI assistant serving a German speaker will prefer a business it can present in German, accurately, over one it has to machine-mangle on the fly and hope.
What CoreLoop does about it
On Pro, you enable the languages you want, and CoreLoop translates your profile content into each: your name and tagline, your descriptions, your category, your cancellation policy, your accessibility notes, and every service’s name and description. You wrote it once, in your own language. The rest is generated, and regenerated automatically whenever you edit.
Then, and this is the part that matters, every channel serves the right language to the right asker. An assistant asking in French gets your French content. The cross-business directory shows you in the searcher’s language. Agent-to-agent callers see which languages you speak on your agent card and pick one. Your public page carries the language annotations search engines want.
The details that keep it honest
Three design choices worth knowing, because they’re the difference between translation as a checkbox and translation that works:
Facts are never translated. Your phone number, email, hours, and prices pass through untouched in every language. Translating a price is how errors are born.
Half-translated is never shown. A language is served only when its translation completed. If something is mid-generation or failed, askers in that language get your original content, not a patchwork.
Fallback is graceful. An asker requesting a language you haven’t enabled simply gets your original language. No errors, no gaps, no empty fields.
And if plans change
Translations survive a downgrade. Drop below Pro and the extra languages stop being served, but nothing is deleted; upgrade again and they’re back as they were. Data outlives plan changes on principle around here.
The dashboard itself, by the way, speaks all eighteen languages on every plan, that part was never gated. The Pro feature is your content speaking them.
One profile, edited in the language you think in, answering in the language your customer thinks in. Setup is a few switches; the Languages doc has the detail, and there’s a seasonal playbook if you want the checklist version before the tourists land.
