You write. Your agent handles the rest.
Your agent works inside your blog. Only you can publish.
Roami is the CMS where Claude, Cursor, or Gemini does the SEO, linking, and drafting from your real archive and Search Console — and every draft waits for your approval.
Free during beta. No card. Agents cannot publish, and that is permanent.
hesaraghatta lake
A real query from Wandering Bong, 28 days to 17 Oct 2026
- Impressions
- 10,422
- Click rate
- 0.1%
- Position
- 8.8
Hesaraghatta Lake from Bangalore: distance, route and best time
Choose who is acting, then press Publish.
Not a chat window. The place your blog lives.
Search performance, drafts, media, and the fix list sit in one dashboard. Your agent reads the same screen you do.
Find the pages that are almost ranking
Roami syncs Search Console and lists the queries sitting at positions 5 to 20, sorted by how much is on the table. The top one on Wandering Bong shows over ten thousand impressions at a 0.1% click rate.
How striking distance works
Turn searches into a writing list
Queries group into themes. Roami tells you which themes you already cover, so the next idea is a new angle and not a fifth post on the same temple.
From idea to reviewed draft
Fix what is broken before you publish
An audit finds orphan pages, thin descriptions, and missing alt text. The agent proposes fixes as a dry run. You approve, it applies, it checks again.
Read the hygiene playbook
Plan the posts that spread it
Each article gets a cluster of drafts for the channels you use, scheduled on a calendar. The same approval rule applies.
See the social calendarOne rule, enforced twice
Roami’s agents can do real work. They cannot put anything live. The API and the agent connection each reject a publish request from an agent on their own, so one failing does not open the gate.
The agent can
- Audit your archive into a fix list that persists
- Draft and update posts in your project only
- Fix alt text and metadata
- Surface ideas from gaps in what you have covered
The agent cannot
- Publish or schedule a post
- Touch another project’s content
- Keep working after you revoke its key
This is not a beta limit. It is how Roami is built. How the gate works
Running on a real blog: Wandering Bong
Wandering Bong is a travel blog with 88 published posts (of 95 total), and it is the reference implementation: every screenshot on this site is its live data.
Search Console, synced 18 October 2026. Dashboard counts.
Your archive already knows what to write next
Enter your blog’s domain and Roami shows what a crawl finds: coverage, thin pages, and gaps. No signup.
How it starts
Connect your agent
Paste Roami’s link into Claude, Cursor, or Gemini and sign in. No terminal required for Claude.
It files a draft
The agent works from your archive and Search Console and leaves the draft in Roami, not in a chat thread.
You review and publish
Read it, edit what needs it, and press Publish yourself.
Questions
Why not use a tool that publishes for me?+
Those tools optimize for volume, and you find out what went live afterwards. Roami is for blogs you care about: the agent does the slow work, and nothing reaches your readers without you.
Will the drafts sound like me?+
The agent works from your existing posts, not a blank prompt. You still edit every draft before it goes out.
What happens if I revoke my agent’s key?+
Access stops. Drafts it already filed stay in Roami for you to keep or delete.
Do I need to already use an AI agent?+
Yes, for now. Roami connects to Claude, Cursor, and Gemini. The blog audit works without one.
Is Wandering Bong a real site?+
Yes. It is a live travel blog on Roami, and it is the reference implementation, not a customer case study.
What does it cost?+
Free during beta.