# Change content that is already on the site

> Change content that is already on the site: 2 companies fully do it, 15 with a limit, 17 carry the tag. Every listing in CMS & website publishing with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/cms.edit-in-place/
- Markdown: https://www.anchorterminal.com/niches/cms.edit-in-place/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/cms.edit-in-place/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/cms.edit-in-place/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 15 | 17 | 13 | 7 |

## What counts as done

Only the requested field or item changes, every other field, locale, block and list row is byte-identical after the write, the editor UI still opens the entry normally, and a stale read is refused rather than overwriting someone else's change.

How agents ask for it: our prices have gone up, change them on the services page; take Dave off the committee page; fix the typo on the about page; update the footer address

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **DatoCMS (Dato Srl)**: Updates leave omitted fields untouched, blocks are edited by id, and meta.current_version makes a stale write fail with 422 STALE_ITEM_VERSION.
- **Ghost (Ghost Foundation Ltd)**: Reads return the stored Lexical JSON by default, and PUT requires updated_at for collision detection, so a stale write is refused; tags and authors are replaced only if sent.

## Does the job, with a limit

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.

- **BCMS (Becomes tech, LLC)**: update-entries changes one language's meta and content, but the docs show no version or updated-at check, so a stale write is not refused.
- **ButterCMS (ButterCMS LLC)**: Page PATCH and PUT are partial and per locale, but repeaters must be resent whole and no version or updated-at check refuses a stale write.
- **Contentstack (Contentstack Inc.)**: update_an_entry is a PUT that replaces the locale's field data; no patch operation or version precondition is in the tool definition, so a stale read overwrites.
- **Cosmic (Cosmic Inc.)**: PATCH updates named metadata keys and leaves others, but no version or modified-at precondition is documented, so a stale write is not refused.
- **Directus (Monospace Inc. (doing business as Directus))**: update takes partial data and relational deltas with create, update and delete per row id, but no version or If-Match check refuses a stale write.
- **dotCMS (dotCMS LLC)**: PATCH on the default fire route merges fields before firing an action, but no stale-write check was found in the workflow reference.
- **Hygraph (Hygraph GmbH)**: update_entry sets only the fields sent and relations take connect and disconnect per item, but no version precondition is documented, so a stale write isn't refused.
- **Kontent.ai (Kontent CZ s.r.o.)**: update-content-item-variant leaves omitted elements untouched, but rich text with components must be resent whole, and no version precondition refuses a stale write.
- **Payload (Payload CMS, Inc.)**: Updates send only changed fields, but acc-19 shows the MCP plugin stripping array row ids so a one-locale write deletes other locales' subfields, and no stale-write check is documented.
- **Prismic (Prismic.io Inc.)**: update_document branches a new version from a base version but takes the document's full content, so every slice must be resent; whether a changed base is refused isn't documented.
- **Sanity (Sanity US Inc. (with Sanity AS))**: patch_documents sets one path and insert addresses array items, edits land in the draft, but no revision precondition appears in the MCP or patch docs read, so a stale write isn't refused.
- **Storyblok (Storyblok GmbH)**: Any Management API write is reachable, but the pages read show no patch operation or version precondition, so a change means resending the story's content object.
- **Strapi (Strapi, Inc.)**: update_<slug> works, but acc-15 shows it replacing a whole dynamic zone, deleting rows another editor added since the read while reporting isError false.
- **Webflow (Webflow, Inc.)**: update_collection_items edits items by id as drafts, but no version precondition refuses a stale write, and acc-24 shows API-inserted rich-text images vanishing in the Designer.
- **WordPress (WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation)**: context=edit returns raw block markup for a safe write-back, but acc-12 shows an MCP server reading rendered HTML and storing it without blocks, and core has no stale-write check.

- not this job: CookieYes MCP Server (CookieYes Limited): Cannot edit site content. Banner text is read-only and legal copy changes are blocked, per the tool table.

## What stops agents finishing

- update tool replaces whole lists, deleting concurrent additions, and reports success
- read returns rendered HTML so a write back destroys block structure
- schema validation rejects edits on documents the native editor saves

## Around it

Before: cms.find-entry. After: cms.publish-and-verify.

## Where this comes from

Weight 13 of 100 in CMS & website publishing: 7 of 39 accounts, several of them data-loss bugs found in 2026 (Strapi, Payload, WordPress block markup)

As data: https://www.anchorterminal.com/api/v1/use-cases/cms.edit-in-place.json, or the MCP tool get_use_case with id cms.edit-in-place. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
