Architecture options

Three approaches we evaluated

The community sprint compared native Salesforce translation, browser overlays, and Salesforce-native translation platforms across thirteen evaluation dimensions.

Dimension	Native Salesforce TranslationTranslation Workbench, translated Knowledge versions, custom labels.	Browser Translation OverlaysClient-side scripts that translate the rendered page after load.	Salesforce-Native Translation PlatformsAppExchange-installed platforms (e.g. Translation Studio) governing memory, glossaries, AI, and human review.
Strengths	• Built into the platform — no new vendor • Covers metadata, custom labels, picklist values • Knowledge supports translated article versions • Predictable Salesforce licensing	• Fast to deploy for marketing pages • Low up-front cost • Covers visual page text without touching the platform	• Covers Experience Cloud, Knowledge, CRM data, Agentforce, Mobile Publisher, and messaging • Shared translation memory and glossaries across teams • AI translation engines with human review queues • Governance, audit trail, and quality metrics • Produces real translated HTML for SEO and AI answer engines
Limitations	• Does not translate CRM data or runtime content • No translation memory or glossary enforcement • No AI translation or human review workflows • Agentforce, messaging, and Mobile Publisher mostly uncovered	• Breaks Lightning Web Runtime and authenticated journeys • Does not translate Knowledge, CRM data, Agentforce, or messaging • No glossary or memory reuse • Produces no indexable HTML — hurts SEO and AI answer engines • Hides translation problems from analytics	• Higher platform investment • Requires operating model — reviewers, glossary owners, governance forum • Longer initial setup than overlays
Best fit	• Small orgs with one or two languages • Metadata-only translation needs • Internal user UI localization	• Static marketing pages only • Prototyping or short-term workarounds	• Nonprofits operating across multiple languages • Orgs deploying Agentforce in multilingual communities • Organizations where language access is a mission requirement

Deep dive on each approach

Native Salesforce Translation

Translation Workbench, translated Knowledge versions, custom labels.

Strengths

• Built into the platform — no new vendor
• Covers metadata, custom labels, picklist values
• Knowledge supports translated article versions
• Predictable Salesforce licensing

Limitations

• Does not translate CRM data or runtime content
• No translation memory or glossary enforcement
• No AI translation or human review workflows
• Agentforce, messaging, and Mobile Publisher mostly uncovered

Best fit

• Small orgs with one or two languages
• Metadata-only translation needs
• Internal user UI localization

Browser Translation Overlays

Client-side scripts that translate the rendered page after load.

Strengths

• Fast to deploy for marketing pages
• Low up-front cost
• Covers visual page text without touching the platform

Limitations

• Breaks Lightning Web Runtime and authenticated journeys
• Does not translate Knowledge, CRM data, Agentforce, or messaging
• No glossary or memory reuse
• Produces no indexable HTML — hurts SEO and AI answer engines
• Hides translation problems from analytics

Best fit

• Static marketing pages only
• Prototyping or short-term workarounds

Salesforce-Native Translation Platforms

AppExchange-installed platforms (e.g. Translation Studio) governing memory, glossaries, AI, and human review.

Strengths

• Covers Experience Cloud, Knowledge, CRM data, Agentforce, Mobile Publisher, and messaging
• Shared translation memory and glossaries across teams
• AI translation engines with human review queues
• Governance, audit trail, and quality metrics
• Produces real translated HTML for SEO and AI answer engines

Limitations

• Higher platform investment
• Requires operating model — reviewers, glossary owners, governance forum
• Longer initial setup than overlays

Best fit

• Nonprofits operating across multiple languages
• Orgs deploying Agentforce in multilingual communities
• Organizations where language access is a mission requirement

Multilingual person engagement

Build a multilingual Salesforce experience that serves every person

Learn from Hyde Housing's journey and accelerate your own multilingual transformation across Experience Cloud, Agentforce, Mobile Publisher, Knowledge, and messaging channels.

Schedule a community discussion Download the findings