# Publish a change and confirm it is live, or roll it back

> Publish a change and confirm it is live, or roll it back: 3 companies fully do it, 14 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.publish-and-verify/
- Markdown: https://www.anchorterminal.com/niches/cms.publish-and-verify/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/cms.publish-and-verify/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/cms.publish-and-verify/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 |
| --- | --- | --- | --- | --- |
| 3 | 14 | 17 | 11 | 5 |

## What counts as done

Each entry reads as published through the delivery API and the public URL shows the new content; a rollback restores the previous revision's content through the API; nothing outside the approved set goes live.

Measured, for our own tests: the public URL shows the new content within 60 seconds, and the rollback takes at most two calls.

How agents ask for it: publish it; is it live yet; put the old version back; schedule this for Monday 9am

## Does the job

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

- **Contentstack (Contentstack Inc.)**: publish_an_entry and deploy_a_release publish per environment and take a version, so an older version can be republished; whether front-end caches refresh is outside the docs read.
- **DatoCMS (Dato Srl)**: Publish is a separate call, the Delivery API serves published versions by default, and itemVersions.restore rolls back; how fast the owner's site refreshes isn't in the docs.
- **WordPress (WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation)**: status publish puts a post live on the site, and a rollback is a GET of the revision then a POST of its content, but caching plugins decide how fast the public URL changes.

## 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)**: Publishing means setting a status the front end filters on, plus a webhook for rebuilds; entry history is read-only over MCP with no restore tool.
- **ButterCMS (ButterCMS LLC)**: status=published publishes posts and pages, but collection items created as drafts must be published in the dashboard, and no revision or restore route exists.
- **Cosmic (Cosmic Inc.)**: Status update publishes and webhooks fire with trigger_webhook; rollback means reading a revision, posting it as a draft revision and publishing, three calls, and dashboard restore is a paid add-on.
- **Directus (Monospace Inc. (doing business as Directus))**: Publishing a version is POST /versions/{id}/promote over REST only, since the MCP refuses directus_versions; revisions are kept but no single restore route was found.
- **dotCMS (dotCMS LLC)**: The PUBLISH action and push-publishing bundles publish content; Bring Back restores versions in the editor, and no API route for it was found.
- **Ghost (Ghost Foundation Ltd)**: A PUT with status published puts the post live on Ghost's own site, and save_revision stores a revision, but no documented route restores one.
- **Hygraph (Hygraph GmbH)**: publish_entry publishes from DRAFT, but unpublish is rejected over MCP, no mutation restores a version, and Hobby has no version history.
- **Kontent.ai (Kontent CZ s.r.o.)**: publish-content-item-variant publishes or schedules and the published version can be read apart from the draft, but no tool restores an earlier version.
- **Payload (Payload CMS, Inc.)**: _status published publishes and restoreVersion rolls back, but acc-20 shows MCP publishes skipping cache revalidation, so the live page keeps old content with no error.
- **Prismic (Prismic.io Inc.)**: publish_release puts a whole release live, but it is irreversible through MCP, needs a Publisher role, and migration releases can't be published over MCP.
- **Sanity (Sanity US Inc. (with Sanity AS))**: publish_documents and releases publish precisely the approved set, but the MCP has no tool to restore an earlier revision.
- **Storyblok (Storyblok GmbH)**: The publish endpoint is reachable, but the MCP can't read the Content Delivery API to confirm what's live, and version history is 1 day on Starter.
- **Strapi (Strapi, Inc.)**: publish_<slug> publishes and discard_<slug>_draft reverts unpublished changes, but no tool restores an earlier published version.
- **Webflow (Webflow, Inc.)**: publish_collection_items and publish_site put changes live on Webflow hosting, but acc-25 shows the MCP can't read live items to confirm, and no tool restores an earlier version.

- not this job: CookieYes MCP Server (CookieYes Limited): Can check whether a banner is live (get_banner_status) but publishes no content and has no revisions.

## What stops agents finishing

- publish saves but cache revalidation never runs, with no error
- no API route to restore a revision (WordPress, Ghost, ButterCMS, Hygraph)
- revision history shorter than a day on the free plan (Storyblok Starter) or absent (Hygraph Hobby)
- site publish limited to one a minute (Webflow)

## Around it

Before: cms.draft-post, cms.edit-in-place, cms.bulk-audit-fix. After: web-scrapers.page-to-markdown, notifications.send.

## Where this comes from

Weight 11 of 100 in CMS & website publishing: 5 of 39 accounts, raised by 1 because every Building benchmark check reads the finished live site

As data: https://www.anchorterminal.com/api/v1/use-cases/cms.publish-and-verify.json, or the MCP tool get_use_case with id cms.publish-and-verify. 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
