Connect Any website to cmo.so

Any that can make an HTTPS request on a schedule: Next.js, Astro, Nuxt, SvelteKit, Laravel, Rails, Django, a headless CMS or a static site with a build step.

What matters is that the call runs on your server, not in the browser, because the key is secret. A cron job, a scheduled function or a build hook all work. If your host sleeps between visits, call the fetch from a build hook or a free cron service instead.

Browser builders such as Lovable, Bolt, v0 and Replit can do it too: their prompt stores the key as a secret and adds a server function that runs every hour. The API reference at https://api.cmo.so/docs has the details for any stack.

GET /posts returns the oldest written article that hasn't been delivered yet: title, excerpt, category, keywords, featured picture with alt text, HTML and Markdown. If the queue is empty nothing is charged, and delivered posts can be read again from /history for 90 days.

Save each article as soon as it arrives, in your database, CMS or content files, then show it at /blog/<slug> with its title, meta description, canonical address and picture. If an article has no slug, make one from the title. Calling once an hour suits most sites.

Each delivered article uses one post from your monthly allowance, shared with posts pushed to other platforms. If your site misses one, read it again from /history or /latest. Other endpoints, such as /quota and /whoami, are listed in the API reference.

Not if you use Vibe Coding: Claude Code, Codex, Cursor or another tool reads the prompt from the app, builds your /blog pages and connects them for you.

In the app, go to Posts → Show me how → Vibe Coding and pick your tool; the prompt comes with your website filled in. Your tool installs cmo.so, asks you to approve a sign-in, adds your website key to .env without printing it and shows you /blog running before anything goes live. It takes about 15 minutes.

If you do have a developer, the API route takes about an hour: create a key, call the endpoint on a schedule and render what comes back. Either way, read the code changes before you deploy, as you would for any pull request.

Improved versions of older articles come from GET /updates. Sitemap matching links articles that are already on your site, so Maggie can rewrite them too.

Have your job read GET /updates on the same schedule as /posts and replace the older version in place, so the address, links and search history carry over. How many rewrites you get depends on Refresh older articles in Publishing settings, and with Search Console connected the data steers which articles need it most. The /sitemap/match endpoint is in the API reference.

New connections start at one article a day. You choose Posts per day in Publishing settings, up to your plan's limit: 1 before a plan, then 2 (Air), 12 (Pro), 24 (Max), 48 (Ultra) or 96 (Elite).

Each delivered article uses one post from your monthly allowance, and the app shows what's left. Turn Publishing off and written articles simply wait in order.

Yes. Open it in Posts → Ready: switch between Preview and Edit, change any words and Save. Rewrite asks Maggie for a new version with your note, Fix Markdown tidies the formatting, and Publish now sends it straight away on connections that support it.

Ideas for future articles sit in Posts → Ideas, where you can add your own, reorder the plan or delete any you don't want.

If you want her to. In Publishing settings, Refresh older articles can be Off, When I ask or Automatic. Automatic uses a share of each day's posts (10 to 50%) for rewrites of articles older than 30, 60, 90 or 180 days.

Rewrites keep the same address, so links and search history stay; the Rewrite queue in Me shows what's suggested and what has been rewritten, and Search Console data steers which articles need it most.

When it's on, the content guard reads each post before it goes out and checks it against your industry's rules (financial, medical, insurance, legal or education) and any rule you write yourself, such as never naming a competitor.

A post that may break a rule is held, as a draft on your website or in Review for social, with the reason and a suggested rewrite, even if posts normally go out on their own. You can see what it held and why in Publishing settings.

Yes, and that's how it starts. New posts wait in the app (Posts → Ready for articles, Social → Review for social posts) until you approve them. You can edit any post, ask Maggie to change it in your own words, or delete it.

When you trust the results, switch the channel to go out on its own; the content guard keeps checking each post first and holds anything it isn't sure about. You can switch back, or pause, at any time.

Your brand profile and the first drafts are ready within minutes of entering your website, and the first posts can go out the same day once you approve them.

Search traffic builds over weeks to months as Google and AI assistants find and trust your pages; social reach grows with regular posting. Connect Search Console to see which posts bring clicks, and Maggie uses it to choose what to improve.

Verifying proves the website is yours. It unlocks your 30 free posts and, for some connections, publishing itself. You can verify with a work email at your domain, a DNS TXT record (one tap if your domain is on Cloudflare), the WordPress plugin, or by asking us to check by hand, usually within one working day.

Free email addresses such as Gmail or Outlook can't be used for the email check.

Yes. Everything on this page works in the cmo.so app on iPhone and on the web at app.cmo.so: connecting, approving, editing and pausing.

You can also ask Maggie from ChatGPT or Claude through the cmo.so connector, for example to see what's waiting for you or to change a post, and she shows a card before she changes anything.