WordPress: Publish
Publish and manage content on your WordPress site.
Integrations
Connect what you
already run.
CLEO reads from the accounts that hold your real numbers, and writes back into the site and the channels your audience sees. 22 connections across 7 categories, each one opened by you.
WordPress
Shopify
Wix
Sanity
GitHub
GitLab
Vercel
Google Docs
Google Search Console
Google Analytics 4
Bing Webmaster Tools
Google Business Profile
YouTube
X
LinkedIn
Bluesky
Mastodon
HubSpot
Zoho CRM
Gmail
Outlook
AI Assistant
22 connections · 7 categoriesSee the directory ↓The two ends
Measurement comes in.
Work goes out.
A dashboard only needs the first half. It reads your numbers and stops there. CLEO needs both, because the fixes it finds have to land somewhere, and the next reading is how it knows they worked.
Reads in
Writes out
Reads in
Rankings, impressions and clicks, from Search Console.
Writes out
Canonical tags, schema and meta, written into the CMS.
Reads in
Traffic and engagement, from GA4.
Writes out
Articles published to WordPress, Wix or Sanity.
Reads in
Channel performance, from YouTube.
Writes out
Remediation pull requests, opened on GitHub or GitLab.
4 connections read, 15 write and 3 run both ways.
Write targets in full: WordPress, Shopify, Wix, Sanity, GitHub, GitLab, Vercel, Google Docs, Google Business Profile, X, LinkedIn, Bluesky, Mastodon, HubSpot, Zoho CRM, Gmail, Outlook and AI Assistant.
Read-only is a report. Both ends is an engine.
The directory
Everything CLEO
plugs into.
The tag on each connection names the surface it feeds.
Website & CMS
Server-side, into the source an engine actually reads. No overlay, no developer ticket.
Shopify: Publish
Publish and manage content on your Shopify store.
Wix: Publish
Publish and manage content on your Wix site.
Sanity: Push
Push generated content straight into your Sanity dataset.
GitHub: Pull requests
Open remediation pull requests directly against your GitHub repository.
GitLab: Merge requests
Open remediation merge requests directly against your GitLab repository.
Vercel: Deploy
Deploy approved fixes and content to your site on Vercel.
Google Docs: Export
Export your Quill blog articles into Google Docs in your Google Drive.
Analytics & Search
Your own performance data, read into the loop rather than estimated around it.
Local
The listing your nearest customers judge you on, kept accurate and kept active.
Google Business Profile: Manage
Manage your listing, posts and reviews on Google Business Profile.
CRM
The names CLEO surfaces land in the system your sales team already works in.
HubSpot: Sync
Sync leads and contacts with your HubSpot CRM.
Leads
Zoho CRM: Sync
Sync leads and contacts with your Zoho CRM.
Leads
Email
Sent from your own address, in your own thread. Not a platform relay.
Gmail: Send
Send emails to your leads from your own Gmail address.
Leads
Outlook: Send
Send emails to your leads from your own Outlook address.
Leads
Account
One open protocol, so the assistant you already use can read the engine directly.
AI Assistant: Connect
Connect CLEO to your AI assistant via MCP.
Account
On access
A connection is only ever
as open as you make it.
CLEO never asks for the keys to an account it has no work in. Every connection opens in that service's own consent screen, and every one of them closes the same way it opened.
Yours to open, yours to close
You connect it
Each one is authorised by you, in that service's own consent screen.
You scope it
It reaches the single account or property it needs, and nothing beside it.
You can cut it
Disconnect from the screen you connected on. Access ends there.
FAQ
Frequently asked questions
22 services. Website and CMS: WordPress, Shopify, Wix, Sanity, GitHub, GitLab, Vercel and Google Docs. Analytics and search: Google Search Console, Google Analytics 4 and Bing Webmaster Tools. Local: Google Business Profile. Social: YouTube, X, LinkedIn, Bluesky and Mastodon. CRM: HubSpot and Zoho CRM. Email: Gmail and Outlook. And your own AI assistant, over MCP.
Into the site you already run. CLEO publishes server-side into WordPress, Wix and Sanity, and opens remediation pull requests against GitHub or merge requests against GitLab for teams whose site lives in a repository, and deploys approved fixes to sites hosted on Vercel. The fix lands in the source an engine reads, not in a client-side overlay most AI crawlers never execute.
No. You connect each integration yourself, scoped to the one account or property it needs. CLEO reads and writes only what that integration is for: content on your CMS, performance data from Search Console and GA4, posts on the social accounts you connect. You can disconnect any of them from the screen you connected them on.
The integration follows the surface it feeds. Website, CMS, analytics and search come with SEO + GEO. The social channels come with Social. CRM and email serve the leads CLEO surfaces. The AI assistant connection is available on every plan.
It schedules and publishes to X, LinkedIn, Bluesky and Mastodon from the accounts you connect, and reads your YouTube channel performance back into the engine. Drafting happens automatically in your brand voice. What goes out is still yours to approve.
CLEO exposes the engine over MCP, the Model Context Protocol, so the assistant you already use can query your presence data, scores and pending work. It is the one connection that points the other way: you ask your assistant, and it reads CLEO.
Connect the stack you have.
The loop closes from there.
See where your brand stands before you connect anything. The Presence Scan is free and needs no login.
Scan your presence
Drafted in your voice. Published to the accounts you own, on your say-so.
YouTube: Connect
Connect your YouTube channel to bring its performance into CLEO.
X: Schedule
Schedule and publish posts to your X account.
LinkedIn: Schedule
Schedule and publish posts to your LinkedIn profile.
Bluesky: Schedule
Schedule and publish posts to your Bluesky account.
Mastodon: Schedule
Schedule and publish posts to your Mastodon account, on any server.