What does “maintaining a website with AI” mean?
It means direct access. Your AI, such as ChatGPT or Claude, connects to the content management system (CMS) your team uses. There it creates pages, changes text and enters prices. It uses the same fields your team would otherwise fill in by hand.
Until now, the AI’s work ended in the chat window. Someone had to copy its text, find the right field in the CMS and paste it there. With the connection, this step disappears. You phrase the request, and the AI enters the result in the right field.
Maintaining a website with AI means: an AI assistant is connected to the CMS and changes content on request. The request comes in plain language. Depending on its permissions, the AI creates drafts or publishes directly.
In practice, the copying work is what disappears. Responsibility for what goes live stays with you.
Why it works: the AI reads your structure
To you, a website consists of pages. To the CMS, it consists of content types with named fields. A product has an image, title, price and description. A person on the team page has a name, role and photo. Your team fills in exactly these fields when maintaining the site.
Through the connection, the AI sees the same structure. With Sanity, it retrieves the content types and their fields directly. With Payload and Strapi, it gets its own commands for reading and writing each content type. The fields are built into these commands. So in all three cases, the AI knows which fields a product has and where each value belongs.
That is why a request in plain language is enough. “Take this spreadsheet and create the new products” is no puzzle for the AI. It matches the spreadsheet columns to the fields it knows. Without this structure, it would have to guess where the price sits on a page.
The short film shows this with an example: a new collection from a spreadsheet and a photo folder.
When does it make sense?
The benefit grows with volume. If you change one sentence on the home page once a month, an AI connection saves hardly any time. The most work disappears where someone today types a spreadsheet into the CMS row by row.
The prime example is a new collection: items in an Excel spreadsheet, photos in a folder. The AI creates a product page for each item, assigns the photo and writes the description. The same pattern covers:
- Price changes across the whole range, straight from the supplier’s price list
- Translations of new pages into all languages of the website, including titles for Google
- Clean-up work, such as adding empty meta descriptions or finding outdated information
- Recurring work without a shop: new staff on the team page, course dates, events or open positions
A furniture shop with twelve employees launches a new collection of about 80 items twice a year. The supplier’s spreadsheet is ready, and the work lies in transferring it. The AI takes over exactly this part, and the team reviews the drafts.
An accounting and trust firm with 25 employees runs its website in German and French. Every new team member and every article is needed twice. The AI enters both in both languages, and a colleague from French-speaking Switzerland proofreads.
With products and photos, one question always comes up: how does the AI know which image belongs to which item? If the files are named like the items, such as “armchair-arno-sage.jpg”, it assigns them itself. If they carry camera or supplier names like “IMG_4821.jpg”, the spreadsheet needs a column with the file name for each item. The assignment then runs through that column.
Uploading the photos is currently the biggest limitation. Through the plain chat connection, it does not work reliably. Sanity only accepts images from a public web address. With Payload, uploading this way is still error-prone, and Strapi does not allow it at all. The reliable route today is Claude on your own computer, where the AI accesses the photo folder directly. The agency sets up this route once. Noevu has not tested ChatGPT and Copilot on the desktop for this.
On two client websites running Sanity and Payload, the AI uploads the photos, not the team. It works on the computer, through a route Noevu set up during the build.
When is it the wrong choice?
An AI connection requires a CMS that exposes its structure. Whether it pays off depends on your current system and on how much recurring work there is. If the website already runs on Sanity, Payload or Strapi, the connection is a small step. Otherwise, it is part of a bigger decision about the system.
It is usually the wrong choice when:
- the website is small and rarely changes – the setup is then out of proportion to the time saved
- the website runs on a site builder without such access and a switch is not planned anyway
- the content sits in the system as free text blocks instead of named fields – then the structure the AI should read is missing
- nobody has time to review the AI’s drafts
Sheer volume is a special case. If the AI changes 400 prices, nobody reviews 400 drafts one by one. Ask for a list with the old and new price instead, and review it as a table. Unusual jumps stand out there faster than across 400 product pages. With ChatGPT, you also confirm every write action individually by default.
You let the AI publish directly because the first runs were flawless. A misread spreadsheet value then appears on every affected page without anyone looking. Have the AI create drafts and approve them yourself, even after the tenth flawless run.
What to settle first
The AI works with the permissions of the account you connect. There is no separate switch just for the AI: if the account may publish, the AI may too. If publishing rebuilds the website automatically, there is no further step between publishing and the live website.
With Sanity, the connection also sees all projects of the signed-in account, including those outside the website. How the systems handle an approval specifically for AI changes is not documented today. Whether a draft stays a draft therefore depends on the account’s role.
Narrow permissions also protect against a new risk. Someone can smuggle instructions into content, for example into a supplier file or a form. If the AI reads this text, it may take it for an order. Experts call this prompt injection. For you, it means: the less the connected account may do, the less a planted sentence can cause.
Checklist before connecting
Record the answers in writing, together with the name of the connected account. If the system keeps a change history, you can later see at a glance what the AI changed.
Do not connect your own admin account. Give the AI its own account with a role that ideally may only create drafts. That keeps every change traceable, and publishing stays a deliberate click on your side.
What the AI does not touch: the design
An obvious worry is that the AI will spoil the website. But the design lives in the website code, and the connection does not reach that far. It reaches the content, and with Sanity also its structure, but never the code. The AI fills the fields and building blocks defined during the build.
So the AI cannot invent a new look. The website only shows what there is code for. If the AI writes something into a field the code does not know, it does not appear on the website. For design, maintenance and navigation, this means:
- New page types and layouts are still planned by whoever designs the website. The AI fills them with content.
- The code stays unchanged. Updates and maintenance stay as predictable as without AI, as long as the AI does not change the structure.
- Navigation and page structure follow the design, even if the AI creates a hundred new pages.
The design framework limits how the AI’s changes appear on the website. The more clearly the content types are cut during the build, the better the AI understands what a field means. A field “Short description, 160 characters maximum” tells it more than a field “Text 2”.
One limit applies: with Sanity, the connection can also change the structure and create new content types and fields. The documentation does not say whether roles can block this. Nothing of it appears on the website until someone writes the matching code.
What this means for SEO
Title, meta description, address and alt texts are also fields in the CMS. The meta description is the short text under the title in Google results. Alt texts describe images for search engines and screen readers. The AI maintains all of it. It fills empty meta descriptions in one pass, and translations get their own titles right away.
The biggest risk exists even with correctly set permissions. If the AI changes a page’s address, the old one leads nowhere, unless the setup creates a redirect. Links from other websites and current Google positions depend on the old address. And a change to the pattern of page titles affects all pages at once.
Three rules keep the risk small:
- Only allow address changes if the system creates a redirect
- Review new titles and descriptions as drafts
- Test bulk changes to SEO fields on a few pages first
An AI connection does not make a website easier to find on its own. It fills fields quickly and completely. Which search terms matter and what each page stands for is still decided by someone who knows your customers.
Which systems can do this
Behind the connections stands a shared standard called MCP (Model Context Protocol). It defines how an AI assistant docks onto an external system. For you, this means: the CMS side stays the same, whether you connect ChatGPT or Claude. Sanity, Payload and Strapi offer such access today, each in its own way.
| Sanity | Payload | Strapi | |
|---|---|---|---|
| Access | Run by Sanity, nothing to install | Official plugin, the agency builds it in | Built in from version 5.47, off at first |
| Sign-in | Sanity login, ideally with a separate account for the AI | Key of a user account | Key with its own role |
| How the AI sees the structure | Retrieves content types and fields directly | Commands per enabled content type | Commands per content type |
| Upload photos via chat | Only from a public web address | Still error-prone | Not possible |
As of September 2026. The vendors keep expanding their access.
There is no objectively best system – only a fitting or an unfitting one. If you want to compare the systems yourself, you will find the basics in the articles on Sanity and Payload.
On the AI side, there are two documented routes today. Claude accepts personal connections as a “connector”, even on the free plan, where you get exactly one. In Team and Enterprise plans, the person with the owner role approves the connection for everyone first. ChatGPT needs developer mode for this, available from the Plus plan and only in the browser.
Setup runs in four steps for all three systems:
- Choose an account. The AI gets its own account instead of your admin access. With Payload and Strapi, the agency enables access first and issues a key for it.
- Enter the connection. The address of the access goes into Claude or ChatGPT. With Sanity you then sign in, and again after about seven days.
- Set permissions. Decide what the account may do: drafts yes, publishing your choice. With Sanity, you also check which projects the account sees.
- Test. Start with a harmless task, such as adding missing meta descriptions as a draft, then check the result in the CMS.
If the website already runs on Sanity, the connection takes a few minutes to enter. With Payload and Strapi, the agency first changes the code, and older Strapi versions need an update. Ongoing costs are the AI subscription and, with Sanity, possibly credit for AI features such as image generation. How smoothly sign-in works with a specific combination only a test shows.
How Noevu approaches it
It starts with the question of which work on your website really recurs. If there is such work, Noevu first checks the content types. If the fields are clearly named and described, the AI understands them without detours. Often the bigger lever lies there rather than in the connection itself.
Noevu sets up the connection with a separate account for the AI and starts with drafts. New tasks are added once the first runs work well. Publishing stays with you. The AI uploads photos from the computer until the systems can do this reliably through chat.
Whether an AI connection pays off for your website is settled in a short call. The Sanity agency page shows how Noevu builds Sanity websites. The AI automation page covers more AI workflows.
Conclusion
An AI with access to the CMS mainly takes over transfer work: spreadsheets, translations, clean-up. It works because it knows the fields of your website and so knows where each value belongs. The design stays untouched, and approval stays with you.
Which tasks you hand to the AI can be decided step by step. Start with drafts and one small task, and keep approving changes yourself later on. This caution pays off, because the access options are young and keep changing.
In a short call, Noevu reviews your CMS and routine work. You see what an AI connection takes off your plate.
Frequently Asked Questions
Can AI really change a website on its own?
Yes, within the permissions of the connected account. If the account can only create drafts, the AI only creates drafts, and you approve them. If it may publish, the AI can push changes live directly. It does not change the design, because the design lives in the website code and not in the CMS.
Which AI subscription do you need for this?
With Claude, the free plan is enough for a personal connection. For Pro and Max, the documentation names no upper limit. In Team and Enterprise plans, the person with the owner role approves the connection first. ChatGPT needs developer mode, available from the Plus plan and only in the browser. There, you confirm every write action individually by default.
Does it work without an AI subscription?
Yes, in two ways. Claude allows one personal connection on the free plan, which is enough for a first test. Sanity also offers AI features directly in the CMS: Content Agent and AI Assist. They need no external AI, and Content Agent respects the account’s permissions. More in the article on Sanity and its AI features.
Do you still need a CMS at all?
Yes. The CMS gives the AI the fields it works with. Without this structure, it would not know where a value belongs. Your team still needs it to review and approve drafts. The AI mainly takes over filling in the fields.
Which systems support this?
Sanity, Payload and Strapi, the three CMSs Noevu builds such connections with. Sanity runs the access itself, and for Payload it comes as an official plugin. In Strapi it is built in from version 5.47, and the agency switches it on. A growing number of other systems now offer such access too.
