GDPR-compliant organization

ISO 27001 certified organization

SOC II compliant organization

Help Scout Docs translation for multilingual self-service

Translate your public Docs guidance with AI and review the language where customers read it. Smartcat helps your support content use consistent product terminology across articles and navigation.

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

Keep instructions aligned with the product

A customer following a setup article should recognize the control named in each step. Review menu labels, permission names, and error-message explanations alongside the actual product terminology. A billing article needs equally careful distinctions between cancellation, refund, and account deletion.

Translate an entire answer path: the collection title, the article, and the next article it links to. Text in screenshots and downloadable attachments needs its own localization work.

How to set up website translation on Help Scout Docs

Create a Smartcat website project for the published Docs site.

Review an article, its collection page, and the navigation.

In Help Scout, open Settings → Docs Sites → the site → Custom Code. Add the generated snippet to Insert head code and save.

Validate the installation in Smartcat and publish reviewed languages.

How this differs from native multilingual content

Maintaining separate Docs sites for different languages gives each site its own authored content. Smartcat’s script is a translated display layer for the published site; it does not create separate Help Scout articles or sites. It also does not translate support conversations in the Help Scout inbox.

Frequently asked questions

Does this translate Help Scout inbox messages?

No. The scope here is the published Docs website.

Where is the script installed?

Use the selected Docs site’s Custom Code settings and its Insert head code field.

Should I add jQuery with the snippet?

Do not add a second library merely to install translation. Docs already includes jQuery; use only the required generated integration code.

Can I review an article before it goes live?

Review the translated wording in Smartcat, then publish the language when ready.

Does the script make a separate Docs site per language?

No. It translates the visitor-facing display without creating those native sites.

Will screenshots be translated?

The script does not rewrite text embedded in screenshots. Localize those images separately when customers need translated interface labels.

Bring your next audience to the content

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