This is about how you can use AI to update content on your website. Keeping content relevant and fresh matters a lot right now, because it's super important for AEO and SEO, and you want your content to be self-driving as well. I'll take you through four different ways of doing this. The right one depends on your use case, how big your team is, and how much risk you can take.
The first example is self-driving content using a Grok bot. It goes through our Sanity schema and knows our Sanity Studio. It knows the kind of blog posts we publish every day, so based on our existing content, it predicts the next blog post. You can use it for a number of things, and you can combine it with analytics. It's self-driving, the UI is good, and you just press a button and it puts the content in draft. Let me show you how it works. For this demo, I'll copy a blog post. I read recently that Prismic released something like "How to build a Prismic website with AI agent in 2026." We'll do the same thing with Sanity. I'll just copy that, I know, cheeky. Once it's completed, you press here, and this is our blog post. It's still a pretty good job. It has the stuff you'd need, and it knows how we write. Throw in an author and it's good to go.
For the second example, we'll use Claude. I'm in the Turbo start Sanity project, and you need to set up your project first. I'm going to use Href and the Sanity MCP for this, but you can use whatever you want. Always in draft, but you can go wild if you like. This looks done. You can open it in Studio with the link, which takes you directly there, or go to Structure and then Blocks. This is the one we just created, and it works like a charm. The Sanity MCP is very powerful with Claude, Codex, or whatever you prefer.
For my next example, I'll use our own software factory. This is ideal if you've vibe coded your website. I'll use Hot Rod, a super fast Astro-powered website. Say we edit the About section and add some feature cards. Before you do this, make sure your design.md file is intact, otherwise it will look really bad. Work on that with your designers first. Let's get started. This is a very basic example of creating a new component. You can make more rules around design and go wilder, but it just works. You can then view the code changes we've made so far, and press preview to see the result. This looks pretty good.
My last example uses v0, and I'll use Pointer. I want to change the content on the home page to say how good Roboto Studio is at building gigantic websites. Why not? I'll change the content, and here's how it looks. The entire home page now says Roboto is the best studio for building a gigantic website. That's pretty cool.
So, the verdict. If you're a large enterprise team with lots of members, especially non-technical ones, something like the Sanity MCP with Claude, or the Grok bot, is a good fit. You can still move quite fast, just at a more stable pace, with structured, safe content. If you have a Markdown website or a hardcoded site and want to move fast, changing a lot of UI and content, I'd recommend something like the software factory or v0. Both approaches work. It all depends on your use case, how big your team is, and how much risk you can take.