Skip to main content
Obvlo translates your published content into the languages configured for your organisation. Two settings decide what gets translated: your translation scope — which destinations are included — and the target languages attached to each destination in that scope.
Translation scope and target languages are configured by Obvlo. Ask your account manager to change them. You can see the result at any time in Organization > Dashboard > Translation Health.

​
Translation scope

Every organisation starts on All destinations. Nothing changes for you unless you ask for a narrower scope. Under Selected destinations, content that belongs only to a destination outside the scope is not translated, creates no translation work, and uses no credits.

​
Target languages per destination

When your organisation uses Selected destinations, each destination carries its own list of target languages. A destination is translated into its own languages and no others — there is no fallback to the organisation-wide list. With that configuration:
  • A guide that belongs only to Barcelona is translated into Spanish and German, and not into French.
  • A guide that belongs only to Lyon is translated into French, and not into Spanish or German.
  • A listing that belongs to both Barcelona and Lyon is translated into all three — shared content receives the union of its destinations’ languages, never the smaller set.
Your organisation’s default language is the source language and is never a translation target.

​
A destination with no target languages

A destination can be in scope with no target languages selected. That destination is not translated at all — no translation work is created and no credits are used. This is a valid configuration, but it is indistinguishable from a forgotten step, so it is flagged when the configuration is saved and Translation Health reports the destination as configured-but-untranslated rather than as thousands of individual gaps.

​
Your organisation-wide language list

Whatever the per-destination configuration, your organisation’s language list is maintained as the union of every in-scope destination’s languages plus your default language. That list is what the Organisation Languages endpoint, the Embeddable Widget, and your Microsite read, so integrations continue to work against one authoritative list. To get the languages for a single destination rather than the union, pass hostId to the Organisation Languages endpoint.

​
What happens when the configuration changes

Because adding a language or a destination can translate content that was never translated before, these changes are billable, and that is stated at the point the change is saved.

​
Excluding site pages

Site pages and sections can be excluded from translation while every other content type stays in scope — guides, listings, locations, host profiles, host information, and promos are all unaffected. This suits organisations that publish their site in one language but need translated content everywhere else. Turning the exclusion on creates no translation work, deletes nothing, and continues to serve translations that already exist. Turning it back off triggers a catch-up run so the pages that were skipped are translated, rather than leaving them permanently untranslated.

​
Translation Health

Translation Health is a weekly report on your translation coverage, at Organization > Dashboard > Translation Health. It is scoped to your translation configuration — a destination limited to French is assessed against French only, so a deliberately narrow scope does not show up as missing translations. Every portal role can read the report. Re-running it on demand and re-syncing the search index are Obvlo-side actions — ask support if you need either. The report groups findings by what they mean for what visitors see: