{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/cms.publish-and-verify/",
    "json": "https://www.anchorterminal.com/niches/cms.publish-and-verify/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/cms.publish-and-verify/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/cms.publish-and-verify/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 14 | 17 | 11 | 5 |\n\n## What counts as done\n\nEach 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.\n\nMeasured, for our own tests: the public URL shows the new content within 60 seconds, and the rollback takes at most two calls.\n\nHow agents ask for it: publish it; is it live yet; put the old version back; schedule this for Monday 9am\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n- **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.\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **Strapi (Strapi, Inc.)**: publish_\u003cslug\u003e publishes and discard_\u003cslug\u003e_draft reverts unpublished changes, but no tool restores an earlier published version.\n- **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.\n\n- 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.\n\n## What stops agents finishing\n\n- publish saves but cache revalidation never runs, with no error\n- no API route to restore a revision (WordPress, Ghost, ButterCMS, Hygraph)\n- revision history shorter than a day on the free plan (Storyblok Starter) or absent (Hygraph Hobby)\n- site publish limited to one a minute (Webflow)\n\n## Around it\n\nBefore: cms.draft-post, cms.edit-in-place, cms.bulk-audit-fix. After: web-scrapers.page-to-markdown, notifications.send.\n\n## Where this comes from\n\nWeight 11 of 100 in CMS \u0026 website publishing: 5 of 39 accounts, raised by 1 because every Building benchmark check reads the finished live site\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Publish a change and confirm it is live, or roll it back",
        "url": ""
      }
    ],
    "description": "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 \u0026 website publishing with the reason and a source.",
    "facts": null,
    "h1": "Publish a change and confirm it is live, or roll it back",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/cms.publish-and-verify/",
    "published": "",
    "section": "agents",
    "title": "Publish a change and confirm it is live, or roll it back | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/cms.publish-and-verify/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
