Everything you need to edit safely.
Eight features that turn your site into something you can actually change yourself. Connect a repo, define what’s safe, and chat. The big stuff still routes to your developer.
Describe the change. Watch it ship.
Type the change you want in plain language. CMS Chat finds the right file, writes the edit, and commits it. No dashboards. No CMS lock-in. No training.
- Plain-language edits — “change the price to $99”
- Works on text, images, links, prices, copy
- Streaming responses with live diffs
Stops you before you tank a ranking
CMS Chat connects to Google Search Console and checks every headline, title tag, and meta description against live ranking data. If you’re about to edit a winner, you see exactly what’s at stake.
- Real keyword + position data shown inline
- Click and impression counts at risk
- “Edit anyway” is always an option
SEO Warning
This H1 ranks #3 for “family dentist Brooklyn”
Position
#3
Clicks/mo
1,247
Impressions
42K
You decide what gets edited
Mark editable regions in your repo. Text and images stay open. Layout, code, and SEO-critical elements stay locked or escalate to your team. Configure once and forget it.
- Editable, warn, escalate, locked — four levels
- Per-file or per-component overrides
- Lives in your repo as plain config
Zone configuration
- AaHero textEditable
- IMGHero imageEditable
- TELPhone numberEditable
- SEOPage titleWarn
- $Pricing layoutEscalate
- {}Footer codeLocked
Big changes route to your developer
When someone asks for a layout change or a new section, CMS Chat doesn’t guess. It opens a pull request with the proposed change and notifies your team. Reviewed and merged on your schedule.
- Auto-classified as commit, warn, or escalate
- Escalations become real GitHub PRs
- Built-in queue for your dev team
Escalation queue
Sarah, 2h ago
Layout changeMike, 1d ago
PR #41Lisa, 3h ago
StructureWorks with any framework, any repo
Next.js, Astro, Hugo, Nuxt, Eleventy, plain HTML — anything in a Git repo. CMS Chat auto-detects the stack on connect and maps editable content without any plugins or migration.
- Auto-detects framework on connect
- No plugins, no custom build step
- Headless or static — both work
Auto-detected on connect
Granular permissions. Your repo, your rules.
CMS Chat installs as a GitHub App on the specific repos you choose — nothing more. Every change is a real Git commit in your repository. Cancel anytime and your site keeps running.
- Per-repo install — never sees other code
- Every edit is a Git commit + diff
- Branch protection and PR reviews respected
GitHub App permissions
Upload an image. Get a fast page.
Drop a 4MB PNG and CMS Chat resizes, converts to WebP, compresses, and writes alt text — automatically. Your client never has to think about image weight or accessibility again.
- Auto resize to display dimensions
- WebP conversion + 90%+ size reduction
- AI-generated alt text for SEO + a11y
Image pipeline
Original
4.2 MB
Optimized
180 KB
- Resized to display dimensions
- Converted to WebP
- AI-generated alt text
- Compressed 96%
A clean editor scoped to their sites
Invite a client and they get a login that shows their sites and nothing else — no agency dashboard, no other clients, no settings they can break. Just “the editor”.
- Client accounts separate from your team’s
- Scoped to the sites you assign them
- Invite by email, revoke any time
Custom client portal
DNS records
Every edit lands in your Git history.
Each change is a real commit in the repo you own, attributed to the person who asked for it. Nothing lives in a database only we can read — the trail is yours.
- Every edit is a commit in your repo
- Attributed to the client who requested it
- Reviewable with the Git tools you already use
Change history
- 2 min ago · Lisa
Updated phone number on /contact
committed - 1 hour ago · Sarah
Replaced hero image on /home
committed - 3 hours ago · Lisa
Reworded Pricing section copy
warned - Yesterday · Mike
Requested footer redesign
escalated
The little things that matter
Mock mode
Demo CMS Chat without connecting a real repo. Great for client pitches.
Team roles
Owner, editor, viewer — fine-grained access per site or per client.
Multi-site management
One dashboard for every site you run. Group by client or studio.
Framework auto-detect
We scan the repo on connect and work out how the site is built before you configure anything.
Escalation queue
Anything outside the safe zones becomes a briefed ticket for your team instead of a broken page.
Localization-ready
Edits respect i18n — chat in one language, edit content in another.
Stop taking tickets for typos.
Tell us about the first client site you’d hand over. We onboard agencies in small batches, and your team keeps the real work, plus the final say on everything else.