Strapi localization

Translate Strapi content without disrupting your editorial workflow.

Choose the fields that need translation, keep the page shape your editors recognize, and review important changes before publishing.

Content workflow from intake to review and publishing

For editorial teams

Keep translators, reviewers, and editors on the same page.

Keep your page structure

Translate the fields you choose while your components, block order, and editorial structure stay familiar.

Bring SEO along

Move titles, descriptions, social copy, and other localized fields through the same content path.

Review before publishing

Give launch pages, policy copy, and other important updates a clear approval step.

What to expect

Know what the workflow includes and what your team connects around it.

Supported by Babelnotch

Translation of the text fields your team selects, plus an optional review path before approved output is delivered.

Recommended pattern

Start with one familiar entry so editors can agree on fields, context, and the approval step.

Optional connection

Reading from Strapi and writing approved fields back are connections your team configures in the signed-in workspace or API integration.

Ready to connect

Start with one page your team already knows well.

Use a familiar page to decide which fields need translation, who reviews it, and where approved content goes next.

Explore integrationsRead API reference

Related workflows

Related translation workflows

FAQ

Questions teams ask before getting started.

Can Babelnotch translate Strapi dynamic zones?

Yes. Send structured document payloads that preserve component identity and translate only selected fields.

Does Strapi write-back happen on the public marketing site?

No. Live write-back belongs in the authenticated workspace where tenant keys, webhook secrets, and audit records are protected.

Can editors review before publishing?

Yes. Sensitive pages can route through review before a localized entry is written back.