Niches · CMS & website publishing

Translate entries into other locales

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
15companies, fit with a limit
18companies carry the tag
9share of the category's work
5first-hand accounts

What counts as done

Each target locale has its own version with translated text that passes field limits, while images, links, references and the source locale are unchanged; untranslated fields fall back as configured; a re-run updates rather than duplicates.

How agents ask for it: translate this page into French and German, add the Dutch version of the product pages, keep the Spanish site in step with English

Does the job, with a limit 15

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
BCMS F
Becomes tech, LLC
Each language is a full copy of meta and content, written per lng; required fields must be filled in every language before saving, which can block a partial job. source
ButterCMS D
ButterCMS LLC
Page updates nest fields under locale codes and the spec says other locales are left alone, but repeaters are replaced whole and the Write API is paid. source
Contentstack B
Contentstack Inc.
localize_an_entry writes one locale as its own copy and unlocalize restores fallback; the tool sends whole field data for that locale, and no test of non-text fields was found. source
Cosmic BB
Cosmic Inc.
Locales are linked objects sharing a slug, so one locale's write is separate, but localisation is a paid add-on on every plan. source
DatoCMS BB
Dato Srl
Fields are localised per field, but an update must resend every locale of a field or the omitted ones are deleted, unless the token's role is limited to the target locales. source
Directus C
Monospace Inc. (doing business as Directus)
Translations are rows in a junction collection, one per language, so one row can be written alone; no API-level fallback is documented, and translation tables count toward the Core collection cap. source
dotCMS C
dotCMS LLC
Each language is its own version of a contentlet, so one language can be written alone; whether the API copies links and images from the source, as the editor prompt does, wasn't documented. source
Hygraph B
Hygraph GmbH
Fields are localised per locale and mutations take a locale property, but Hobby allows 2 locales and the docs read don't show what a one-locale write does to others. source
Kontent.ai BB
Kontent CZ s.r.o.
Each language is its own variant, written alone with omitted elements untouched, but the pages read don't cover fallback or what non-localisable elements do across languages. source
Payload D
Payload CMS, Inc.
Field-level localisation with fallback-locale exists, but acc-19 shows MCP writes to localised array subfields wiping other locales. source
Prismic C
Prismic.io Inc.
Each locale is its own document linked by alternate_language_id, so one locale is written alone, but update_document needs the full content and fallback behaviour isn't covered. source
Sanity BB
Sanity US Inc. (with Sanity AS)
Documents and fields can be patched per locale, but acc-27 found no documented pattern for translating field-level internationalizedArray entries with the Translate action. source
Storyblok B
Storyblok GmbH
Translations are field__i18n__ keys inside the same content object, so a write that omits a locale's keys can drop them; the docs read don't show a one-locale write. source
Strapi BB
Strapi, Inc.
Tools take a locale, but acc-16 shows each source publish regenerating locales and wiping images in components, and acc-17 shows one over-length value failing a whole AI translation job. source
Webflow BB
Webflow, Inc.
Existing items and static content can be updated in secondary locales, but the MCP can't create new localised CMS items, and acc-25 shows it can't read what is live per locale. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
CookieYes MCP Server D
CookieYes Limited
get_banner_translations reads banner languages only; there is no write for translations or site content. source
Ghost C
Ghost Foundation Ltd
Ghost has no content locales; a translation is a separate post. source
WordPress B
WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation
Core WordPress has no content locales; translation needs a multilingual plugin outside this listing. source

What stops agents finishing

  • writing one locale wipes other locales or non-text fields
  • one over-length value fails the whole job with a generic error
  • MCP cannot create new localised items (Webflow), or the CMS has no locales (Ghost, WordPress core)
  • localisation is a paid add-on (Cosmic)

Around it

Before: cms.draft-post, cms.edit-in-place. After: cms.publish-and-verify.

Where this comes from

Weight 9 of 100 in CMS & website publishing: 5 of 39 accounts, all on GitHub and all about locale data being lost or a translation job failing

The same as data: /api/v1/use-cases/cms.translate-locales.json, or the MCP tool get_use_case with id cms.translate-locales. Other jobs in this category: /api/v1/niches?category=cms.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.