Autotranslation Rules

Autotranslation Rules help your team keep localized content up to date without starting each translation run by hand.

A rule watches for entry activity, such as creating, updating, or publishing content in the default locale. When the rule matches, the Studio starts a translation run for the target locales you choose.

When to use rules

Use Autotranslation Rules when your team regularly translates the same kinds of content.

For example, a rule can:

translate new blog posts after they are published
refresh product page translations after the default-locale entry changes
create draft translations for editors to review before they go live
limit automatic translation to specific content models or field types

For one-time work, use Translate Content instead.

Create a rule

Open your project in the Studio.
Go to Autotranslation Rules.
Click Create Rule.
Add a name and optional description.
Choose when the rule should run.
Pick the target locales.
Choose the content models and field types to include.
Choose how translated content should be completed.
Click Save Rule.

New rules are enabled by default. You can turn a rule off at any time without deleting it.

Choose triggers

Triggers decide when a rule starts a translation run.

On Create runs when an entry is created.
On Update runs when an entry is updated.
On Publish runs when an entry is published.

You can choose more than one trigger for the same rule.

Choose targets

Target locales are the locales that should receive translated content.

Autotranslation uses the project default locale as the source. Add another locale before creating a rule.

You can also limit a rule to selected content models. Leave all content models unchecked to include every content model.

Choose field types

Rules can translate text, textarea, and rich text fields.

Select only the field types you want the rule to update. This is useful when some fields need manual translation or should stay untouched.

Choose a completion mode

Completion mode controls what happens after the rule creates translated content.

Review Before Saving creates a translation run for your team to review and commit later.
Save as Draft applies the translations to target locale entries as drafts.
Publish Automatically applies the translations and publishes the target locale entries.

Translation options

Each rule includes a few options for how translations are handled.

Skip Existing Translations leaves translated fields alone when they already have content.
Create Missing Locale Variants creates target locale entries when they do not already exist.
Remove Internal Links removes internal links from rich text translations.
Additional Instructions lets you add plain-language guidance, such as preferred tone, terms to keep unchanged, or regional spelling.

Manage rules

The Autotranslation Rules page shows each rule, its triggers, target locales, completion mode, and whether it is enabled.

From this page, you can:

open a rule by clicking its name
turn a rule on or off
delete a rule when it is no longer needed

Deleting a rule stops future automatic translation runs. It does not remove translations that were already created.