Chat With Your Site — Update Content, in Multiple Languages, in One Sentence
You open a box. It says "Chat with your site." You type what you want done. The site does it.
That's not a metaphor or a future vision — it's the screen that greets you every time you log into a broberg.ai-powered website. No menus to learn, no forms to hunt through for the right field. You say what you want, in plain language, and the CMS figures out the rest.
What can it actually do?
The chat has access to over 60 tools under the hood — not 60 buttons you need to learn, but 60 concrete actions the CMS picks between on its own, depending on what you ask for:
- Content — create, edit, publish, unpublish, clone a page, restore from trash, browse the full revision history.
- Write in multiple languages — ask the CMS to translate a single page, or the entire site at once. It creates the translation as a draft for review, or publishes it directly if you ask it to.
- Search and overview — "show me all drafts," "what's the homepage about," "search for anything tagged GDPR" — the chat knows your whole content structure.
- Media — find, search, and insert images without leaving the conversation.
- AI generation — ask it to write a first draft, rewrite a field, or build an interactive component.
- Quality and operations — run a Lighthouse check, view performance history, check for broken links, take a backup.
- Agents — kick off autonomous content agents, and approve their suggestions afterward through the curation queue.
All of it happens in plain language. "Create a campaign page about our summer sale, in Danish and English, and publish it" is one sentence — not a ten-click workflow.
Same tools, outside the chat
The same actions are also available via MCP (Model Context Protocol) — the open standard AI tools use to talk to each other. That means an external AI client (Claude Desktop, or a fully bespoke internal tool) can drive the CMS directly, without going through the admin surface at all.
That points at something bigger: the CMS doesn't require its own admin interface. Everything runs through a real REST API with full CRUD and a publishing workflow — creation, editing, translation, revision history, publishing, all available outside the UI. In practice, that means the CMS can work purely as a headless CMS: a customer can build — or we can build for them — a fully custom admin experience, while the CMS is just the engine underneath, invisible to whoever's actually working in it.
A completely different chat: the one your visitors meet
There's an important distinction to keep straight. The "Chat with your site" above is your own toolbox — the one you, as the owner, use to run the site. But a website can also have its own chat, one that meets visitors, and answers from your knowledge, not from the internet at large.
Where that knowledge lives is a deliberate choice, not a fixed template. Sometimes the answer is a deep, curated knowledge base like Trail — a "second brain" trained on all your expertise over time, citing its sources, and honestly saying so when it doesn't know something. Other times it's simpler: a regular RAG setup, or just flat, static text or markdown files as context. The solution matches the job — not the other way around.
The proof: two chats, one customer
Sanne Andersen's platform is the best example of both running at once.
Externally, her visitors meet Eir — an AI chat on sanneandersen.dk, grounded in her own Trail knowledge base. Eir answers in Sanne's own professional language, with sources for every answer, because it's trained on her actual expertise — not a generic chatbot guessing.
Internally, Sanne uses the same "Chat with your site" feature every other broberg.ai customer gets, to run her CMS: fixing copy, adding products, following up on drafts — the same toolbox described above.
One platform. Two chats. Each with its own purpose.
Read Sanne's full case → Four businesses, one platform.
Want to chat your own website into shape? → Let's talk.