CMS delivery and publication

Updated 11 November 2026 · 3 min read
On this page

Send Content Studio pages to WordPress or Contentful as a new draft. Your team reviews, edits and publishes in the CMS. Cleotic then checks the publication state and whether the website serves the page.

Connect a CMS

  1. Open Brand settings → Site and check the brand's website address.
  2. On the Drafts row, select Connect a CMS. Choose WordPress or Contentful, then Continue.
  3. For WordPress, select Approve in WordPress and approve access. One approval also turns on AI visits; see WordPress.
  4. For Contentful, paste a management token from Settings → CMA tokens in Contentful, choose the space for your site if asked, and select Connect Contentful. Cleotic checks sign-in, access and that it can save drafts.

Drafts are saved for review, never published. If the Drafts row shows Needs attention, for example when the content model changed, follow its prompt to review where drafts go or reconnect.

Send a page

Open a page in Content Studio and select Send to CMS, or ask the page agent to send it. Choose the destination, review mapped fields and any author, category or image choices it supports, then send the draft. The page's first heading becomes the article title. The agent can send only when the brand has one ready destination.

Each send creates a new draft. Sending again does not update the previous article. Open the delivered draft in the CMS for final edits and publication.

If delivery needs attention, follow the action shown. When Cleotic cannot confirm whether a draft was created, check the CMS before sending again to avoid a duplicate.

Read the status

Each send is listed under the page's status bar with its delivery state and any action it needs. The page shows Sent to CMS once a draft is delivered.

Cleotic then checks the CMS and your website: more often at first, then hourly and daily, for up to 30 days. The first time the article is published in the CMS and its address answers on your site, the page becomes Live at that address and locks. Live confirms the page is available, not that it's indexed or cited.

If the page came from an opportunity, the opportunity moves to Watching and its timeline records the live URL. The page's results start too. None of it proves the page caused a change.

Review what happens next

Connect website tracking to collect detected AI crawler requests and referrals. CMS delivery does not install traffic tracking, and traffic collection does not backfill earlier visits.

The page's results show which AI crawlers have read it. Use AI traffic for the page's full activity. Continue monitoring the original buyer questions in Answers and Performance, and review their citations. Keep these observations separate: a crawler request does not prove indexing, and a later mention does not prove the article caused it.

For an unsupported CMS, copy the Markdown and publish through your own workflow, then select Mark published with the page's address. This moves a linked opportunity to Watching in the same way, but it does not trigger CMS checks.