GDPR-compliant organization

ISO 27001 certified organization

SOC II compliant organization

Translate Experience Cloud content for your customer and partner audiences

Give multilingual audiences clearer portal guidance with AI translation and review. Smartcat’s website approach targets accessible page text; Salesforce permissions, records, and application behavior stay under your existing controls.

Smartcat editor showing translated segments with a translation memory match and reviewer assignments

More than 80 of the world’s largest companies have chosen Smartcat

A partner portal needs precise role and process language

Translate the guidance that helps a partner understand onboarding, certification, or deal-registration steps. Keep terms such as “submit,” “approve,” and “return for changes” distinct. A translated instruction should match the action the portal actually permits.

Public marketing pages and authenticated portal pages are different scopes. Do not assume a public website crawler can access signed-in content, or that a language selector changes a user’s access rights.

How to set up website translation on Salesforce Experience Cloud

Select the portal content and audience for translation with your Salesforce implementation team.

Prepare the Smartcat website project and review accessible source pages.

In Experience Builder, open Settings → Advanced → Edit Head Markup. The site’s Aura or LWR runtime and security configuration determine how custom scripts can run.

Validate the integration in a sandbox before a production release. Publish the approved site configuration and translations through their respective workflows.

How this differs from native multilingual content

Experience Cloud’s multilingual site features and Translation Workbench manage Salesforce-specific language resources. A website translation script is a separate layer over rendered content. It is not a Salesforce record translator or a replacement for native label, metadata, and permission configuration.

Frequently asked questions

Does this translate Salesforce records?

No record synchronization is claimed by the website-script method.

Does one installation work identically on Aura and LWR?

Do not assume that. Their runtimes and security behavior differ, so the implementation must match the site type.

Where is head markup configured?

Experience Builder → Settings → Advanced → Edit Head Markup.

Should I disable CSP to make it work?

No. Apply the narrowly required, approved script configuration for your site. A generic instruction to weaken all security would be inappropriate.

Can it translate authenticated portal pages?

That requires a validated access and content scope. Public-site translation does not establish coverage of signed-in content.

What should we bring to a demo?

Your site type, representative pages, language requirements, and the public-versus-authenticated scope. These define the actual implementation.

Bring your next audience to the content

Translate a representative page, review the wording in context, and publish your selected languages.