Edit your website by chat, one message at a time.
Edit your website by chat: you send a message, an agent that knows your content model writes the change and returns a preview before anything goes live.
A message replaces the login
If you can send a voice message, you can maintain your website. Nothing more is needed on your side.
The schema is the guardrail
An agent can only fill fields that exist, in formats that validate during the build.
Every edit is a commit
History, before and after, and rollback exist because they are part of the development flow.
See what we build.
Mini Marvin is our own progressive web app, designed, built and running live in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
Why this route holds up technically.
-
The schema is the guardrail
Astro content lives in content collections whose fields a Zod schema describes. The agent reads it rather than guessing.
More on this
Astro validates every file in a collection against its schema. A missing required field, a date that is no date, a category outside the allowed list: the build breaks and the previous version stays online. On the model see Astro CMS; with a headless CMS the same flow runs through its API.
-
Anything with a field works by message
Texts, numbers, dates, new entries, images with their alt text, metadata and the ordering.
More on this
The reach equals the model: whatever sits as body text inside a component becomes reachable by chat once it gets a field. Images run through the built-in image optimisation and the alt text is a required field, see accessible websites. Whatever else slows your visibility is found by an SEO audit.
-
Preview first, publish second
Every commit produces a preview URL, built the way production builds it. The link arrives in the chat.
More on this
Then the approval level applies, set per collection: straight live, a confirmation in the chat after the preview, or a pull request your editors read. For prices, legal texts and career pages we suggest the stricter level. The schema checks the form, never the truth: 149 in place of 194 validates perfectly.
-
Structure stays development work
New page types, extra fields, navigation and layout are changes to code, never to content.
More on this
They run as ordinary development work in the project or under support and maintenance. Anyone who wants to assemble pages freely from blocks is better served by Webflow. And once the website turns into an application with logins and roles, that is custom software development.
Does that match your day?
Describe in three sentences who edits content today and where it breaks down. You get an assessment back.
What the setup looks like for whom.
| Who edits | What the setup looks like | What approval looks like |
|---|---|---|
| Enterprise with an editorial team | The editorial system stays the place for campaigns and translations. The chat channel covers named collections. | Never straight live. Every chat edit becomes a pull request inside the existing approval process. |
| SME marketing, one to three people | Chat is the main route, the repository the fallback. The agent knows every editorial collection. | Confirmation in the chat: look at the preview, reply briefly, published. |
| Sole traders, trades, practices | No CMS login, because none is needed. A photo and a voice message from site carry a new reference. | Usually one short word in the chat, and the reference page is current the same evening. |
How an edit actually flows.
The message
Text or voice message, an image attached. Everyday wording is enough, the agent knows the structure.
Read the schema
Which collection is meant, which fields it has, which are required, which values are allowed.
Draft and validation
The change is written and checked in the build. Anything ambiguous returns as a question.
Commit and preview
Timestamp, author, a line-by-line before and after, plus a preview URL for you.
Approval and deploy
Straight live, confirmation in the chat, or a pull request. Then the usual pipeline runs.
Common questions on editing a website by chat.
How does editing a website by chat work in practice?
You send a message to a bot. The agent works out which content is meant, reads the schema of the collection, writes the change and records it as a commit. That produces a preview URL, which arrives in the chat.
Can an AI agent wreck my website?
The protection comes from the schema. A field that does not exist cannot be filled. An invalid value breaks the build and the previous version stays online. Every change is a commit, so reverting takes minutes.
Does it have to be a CMS Telegram bot, or does WhatsApp work?
Telegram is the usual starting point because a bot is quick to set up and carries voice messages and images. WhatsApp runs through the business interface and takes more setup. The mechanics behind it stay the same.
Who may trigger changes and how does approval work?
Write access goes to named people, never a shared account. Approval has three levels: straight live, confirmation in the chat after the preview, or a pull request. Where several departments are involved we take on the project management.
What does AI content editing cost and how long does setup take?
On a new build it adds one to two weeks, retrofitting an existing Astro site two to four, with pull-request approval three to six. The chat channel belongs to your website setup and carries no list price. The drivers are under Astro development cost.
What about data protection and the model provider?
The messenger and the language model are third-party systems in the path. We name both so your data protection officer can put the processing agreements in place, see GDPR-compliant websites. Only content meant for publication belongs in the chat.
Keep reading in the Astro cluster.
The foundation, the system choice and the route there:
A website you simply message.
Tell us which content on your site goes stale most often. You get an assessment of scope, approval and effort.
Request website editing by chat.
Briefly describe who edits content in your organisation and where it breaks down today.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related services.
WhatsApp AI Agent
The proof: a chat agent we built for our own sales process and ran with live customers.
Learn moreAI Automation
Chat agents, process automation and AI in day-to-day operations, beyond the website.
Learn moreAstro CMS
Content collections, Git-based systems or a headless CMS: which model fits your editors.
Learn more