Definition
What is an agentic CMS?
An agentic CMS is a content management system where AI agents can do the work a person does in the admin. They open a live post, change it, check it, and publish it, inside guardrails you control.
A traditional CMS stores content and waits for someone to log in. An agentic CMS lets agents act on that content directly, so refreshing a slipping post or fixing an outdated stat happens in minutes, with you approving the result.
Guardrails built in
Traditional, headless, and agentic.
Traditional CMS
- Who does the editing
- A person in the admin panel
- Who writes the content
- You, or whoever you pay
- Keeping old posts fresh
- Manual, when someone notices
- Where it runs
- Its own themes and plugins
- Working from Claude
- Depends on the plugins
Headless CMS
- Who does the editing
- A person in the studio, on a model a developer set up
- Who writes the content
- You, or whoever you pay
- Keeping old posts fresh
- Manual, when someone notices
- Where it runs
- Any front end, through an API
- Working from Claude
- Possible, with your own MCP build
Agentic CMS
- Who does the editing
- Agents edit, you approve
- Who writes the content
- Agents that read your knowledge base and hard rules
- Keeping old posts fresh
- Search Console flags the slip, an agent refreshes at the same URL
- Where it runs
- On top of WordPress, Shopify, Webflow, or a custom site
- Working from Claude
- Built in, through the Claude connector
| Traditional CMS | Headless CMS | Agentic CMS | |
|---|---|---|---|
| Who does the editing | A person in the admin panel | A person in the studio, on a model a developer set up | Agents edit, you approve |
| Who writes the content | You, or whoever you pay | You, or whoever you pay | Agents that read your knowledge base and hard rules |
| Keeping old posts fresh | Manual, when someone notices | Manual, when someone notices | Search Console flags the slip, an agent refreshes at the same URL |
| Where it runs | Its own themes and plugins | Any front end, through an API | On top of WordPress, Shopify, Webflow, or a custom site |
| Working from Claude | Depends on the plugins | Possible, with your own MCP build | Built in, through the Claude connector |
What the agent can do on your site.
Reads what is live
Lists every post on your connected site, with what is live, what is a draft, and which posts have changes waiting to go out.
Writes in your voice
The SEO agent researches the keyword, reads your knowledge base and hard rules, and drafts. Four slop filters run before you see it.
Publishes when you say so
Push a post live from the library or the CMS in a couple of clicks, with the SEO title, meta description, and featured image set.
Edits one section at a time
Ask it to tighten an intro or fix a stat and it changes only that part, checks the links, and shows a diff you can revert.
Republishes at the same URL
An edited or refreshed post goes back over the original. If the original cannot be found, the publish stops, so duplicates never appear.
Takes orders from your Claude
Through the Claude connector, your own Claude can open a live post, edit it, and leave it waiting for you to publish.
The CMS itself
A lightweight CMS for everything that is live.
The CMS lists every post on your connected site. Write a new one or paste a draft, set the slug, SEO title, meta description, and featured image, and publish. Character counts flag anything Google will cut off.
Rename a live post and Contengi checks the new slug against your other posts and your sitemap first, then reminds you to redirect the old address.
Refresh, don't rewrite
Posts that slip get fixed where they already rank.
Search Console shows which posts are losing clicks and which keywords sit just off page one. Point the refresh agent at a post and it reads the live version, updates the sections that need it, and republishes over the original URL, so the rankings you earned stay attached.
Works with the site you already have.
WordPress
Core REST API and an Application Password. No plugin to install.
Learn moreShopify
A private app on your own store with one scope: write_content.
Learn moreWebflow
Data API v2 with a site token, mapped to your own collection fields.
Learn moreClaude websites
One signed endpoint that Claude Code writes for you from a single prompt.
Learn morev0 websites
One route handler that v0 adds to your Next.js app from a single prompt.
Learn moreFrom your own Claude
A CMS your Claude can run.
Connect Contengi to Claude and every post in the CMS is one chat away. Ask Claude to find the post on retainer pricing, update the numbers, and add an FAQ, and the edit lands in Contengi waiting for your approval.
FAQ
Common questions
What is an agentic CMS?
A content management system where AI agents can do the work a person does in the admin: open a live post, change it, check it, and publish it, inside guardrails you control. Contengi is an agentic CMS that connects to WordPress, Shopify, Webflow, and custom sites.
Will the agent publish changes without asking?
No. Edits wait for you with a diff you can revert, and nothing goes live until you publish it. Deleting a post asks you to type it out first.
Do I have to move my content into Contengi?
No. Your posts stay on your site. Contengi reads them from WordPress, Shopify, or Webflow, and keeps a copy of everything it publishes to custom sites so edits start from exactly what went out.
Can it unpublish or delete posts?
On custom websites and pull feeds, yes, through a signed request your site confirms. WordPress and Shopify keep unpublishing and deleting in their own admin.
What stops it creating duplicate posts?
Every update republishes over the original post at the same URL. If Contengi cannot find the original, the publish stops instead of creating a second copy somewhere else.
Can I use the CMS from Claude?
Yes. Connect Contengi to Claude and every post in the CMS is reachable from a chat. Claude can read a live post, edit it section by section, and leave it for you to publish.
Keep exploring
Related features and reads
In the platform