GDPR-compliant organization

ISO 27001 certified organization

SOC II compliant organization

Translate your Docusaurus site with AI

Add the Smartcat website snippet to your Docusaurus project once, deploy it through your normal pipeline, and review translations in Smartcat before you publish a language.

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

How to add Smartcat to Docusaurus

Create a Smartcat website project from your published Docusaurus URL and choose the target languages.

Install the generated Smartcat snippet through scripts or headTags in docusaurus.config.js, then rebuild and deploy.

Deploy the change and open the published site to confirm the snippet is present.

Review the translations in Smartcat’s visual editor and publish the languages that are ready.

Translate Docusaurus guidance while preserving technical examples

Configure the integration through docusaurus.config.js using the supported scripts or headTags mechanism appropriate to the generated snippet. Rebuild and deploy through the normal documentation pipeline. Keep the customization in source control rather than editing the generated build directory.

Review conceptual explanations, navigation, and procedure text. Preserve code identifiers, CLI flags, and API paths unless the underlying product actually localizes them. Docusaurus’s own i18n creates language-specific documentation sources and routes; the Smartcat website script is a different model for translated display.

What changes for visitors, and what stays in Docusaurus

Website translation changes the published reading experience. It does not create translated source files, message catalogs, or locale builds in your Docusaurus repository.

Review before a language goes live

Machine translation gives you a fast first draft. In Smartcat’s visual editor you see each translated string on the page, shorten headings that run long on mobile, and keep product and brand names consistent with a glossary. Assign a reviewer when a page needs approval, and publish only the languages that are ready.

Frequently asked questions

Does the script create Docusaurus i18n files?

No. It does not generate translated Markdown trees or configure Docusaurus locale builds. Use a software/content localization workflow when those repository artifacts are required.

Can I edit translations before publishing?

Yes. Refine and confirm the wording in Smartcat’s visual editor, then publish the languages that are ready.

What happens when I add a new page in Docusaurus?

New text follows the Smartcat project’s selected translation mode. Choose reviewed translations when every new page requires approval; automatic modes can translate newly encountered text. Neither mode changes your source content in Docusaurus.

Publish your Docusaurus site in more languages

Install the snippet once, review the translations in context, and publish the languages your audience needs. See all website integrations or read how the Website Translator works.