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 destination
- Add the website in Brand settings -> Websites if it is not already listed.
- Open Brand settings -> Destinations and add a destination.
- Choose WordPress or Contentful. Check and save the connection, or reuse an existing connection.
- Select the website. For Contentful, select the environment too.
- Continue to mapping, choose the article type and review the proposed fields and sample article.
- Confirm the mapping. This creates one test draft in your CMS. Open it to check the result, then delete the test draft in the CMS when finished.
A destination must be ready before you can send an article. If access or the content model changes, reconnect or review its mapping in Destinations.
For Contentful, set the destination's Website URL rule, such as https://example.com/guides/{slug}. Without a URL rule, Cleotic can observe CMS publication but cannot check the website page. WordPress supplies the page URL.
Send an article
Open a generated brief in Content Studio -> Pipeline and select Send to CMS. 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.
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.
Use Sources -> AI traffic to inspect activity for the page. 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. Mark Published records brief progress manually; it does not trigger CMS publication checks.