CMS delivery and publication
Send generated content 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
- Open Brand settings → Site and check the brand's website address.
- On the Drafts row, select Connect a CMS, then WordPress or Contentful.
- For WordPress, select Approve in WordPress and approve access. One approval also turns on AI visits; see WordPress.
- 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 an article
Open a drafted page in Content Studio and select Publish, then the send, after the checks. Choose the destination, review mapped fields and any author, category or image choices it supports, then send the draft.
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 publication status
| Status | What Cleotic observed |
|---|---|
| Draft in WordPress or Contentful | The draft is delivered and waiting for publication in the CMS. |
| Published in the CMS | The CMS reports publication. The website page is not confirmed yet. |
| Live | The CMS reports publication and the website URL returns a successful response. |
| Unpublished | An article previously observed as published is no longer published in the CMS. |
| Removed | The article no longer exists in the CMS. Automatic checks stop. |
The delivery shows the latest check, current page address and previous addresses when available. If a check fails, review the message and connection rather than treating it as proof the page was removed.
Checks run more frequently at first, then reduce to hourly and daily. Automatic checks stop after 30 days from delivery or the latest observed CMS publication. Check now remains available. Live confirms page availability, not indexing, citation or a visibility improvement.
The first time an article is seen Live, Cleotic marks its page published. 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: its question is asked again on your tracked engines, with mentions and citations of the page counted separately. 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 AI crawler fetches, and each engine's first mention and citation. 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. This moves a linked opportunity to Watching in the same way, but it does not trigger CMS publication checks.
Updated