
Our last post showed the good part: you describe a page, give Claude notes until it's right, and it builds the page on your real website. This is the set-up behind it. If your site runs on Sanity, all of it happens in Claude's settings and on Sanity's sign-in screen. Nobody opens a terminal, and nothing on your live site changes until someone on your team decides it should.
What do you need before you start?
Check these four things
- Claude on the web or the desktop app. Connectors can't be added from the phone apps, though they work there once added.
- A Sanity login that's a member of your website's project. If you've never opened Sanity Studio, ask whoever built your site to invite you.
- On a Claude Team or Enterprise plan, an owner may need to switch the Sanity connector on for the organisation first.
- One test post you won't mind deleting.
Step 1: Add the Sanity connector
A connector is a secure link between Claude and another app. Sanity publishes an official one and it's listed in Claude's connector directory, so there's nothing to install and no web address to paste.
In Claude, open Customize, then Connectors, and browse the directory. Or click + in any chat, hover over Connectors and choose Manage connectors. Search for Sanity, open it and click Connect.
- Search
- Connect
- Sign in
- Connected
Step 2: Sign in with the right Sanity account
Connect sends you to Sanity to sign in and approve access. Use the exact login you use for Studio. Sanity treats a Google login and an email login as two separate accounts, even with the same address, so the wrong one connects perfectly and then can't see a single project.
Approve the request and you're back in Claude with Sanity marked as connected.
Step 3: Take the publish button away from Claude
Do this before you ask Claude for anything. The connector acts as you, so it can do whatever your Sanity login can do, and for most people that includes publishing.
Open the Sanity connector in Customize, then Connectors. Claude lists every tool the connector has and lets you set each one to Always allow, Needs approval or Blocked. Ours are set like this:
- Reading content and the content model: Always allow. Claude looks things up constantly, and approving every lookup gets old in about a minute.
- Creating and editing drafts: Always allow. Drafts don't touch the live site. Choose Needs approval instead if you'd like to watch every write for the first few weeks.
- Publish, unpublish and discard: Blocked. These are the only tools that change what visitors see or throw work away.
Claude writes the drafts. A person presses publish.
On Sanity's Growth plan or above you can add a second lock. Connect Claude through a separate Sanity login with the Contributor role, which can write drafts but can't publish. Your own login keeps its publish rights in Studio, and a setting changed by mistake still can't put anything live.
Step 4: Check Claude can see your website
Start a new chat, click +, hover over Connectors and make sure Sanity is switched on. Then ask:
Which Sanity projects can you see? For our website, list the types of content it holds and the latest blog posts.
I can see one project, intersect-ai, with live content in the production dataset.
Content types: blog posts, case studies, service pages, industry pages, categories, authors.
- AI Meeting Note-Takers Your Team Will Actually Trust
- 10 things Claude Design can do that most teams miss
- The AI Project Lifecycle: Six Stages, Six Ways to Stall
If Claude says it can't see any projects, you signed in with the wrong login in step 2. Disconnect and connect again. If it finds the project but no posts, it's probably looking in the wrong dataset. Most sites keep live content in one called production, and you'll write that into the next step so Claude never has to guess.
Step 5: Write the house rules once
Claude is only as consistent as its instructions. Rather than repeat them in every chat, make a Claude Project for website work and put the rules in its instructions. Every chat in that project starts with them. Here's a trimmed version of ours:
- Our website runs on Sanity: project your project ID, dataset production.
- Save everything as a draft. Never publish, unpublish or discard anything.
- Every blog post needs a title under 60 characters, a slug, an excerpt, a search description under 155 characters, a category from our list and a featured image.
- Before editing an existing post, check whether someone has an unpublished draft open. If they do, stop and tell me.
- Show me a preview that looks like our live site before you save anything to Sanity.
- Write in Australian English.
Rule four earned its place. When Claude was adding categories to our older posts, it found one with a colleague's half-finished edit in it, left it alone and told us, instead of pushing the unfinished version live with the rest.
Load your brand while you're here, so previews look like your site from the first draft. We wrote up how in How to get your brand into Claude.
Step 6: Make your first draft
Ask for something small and real. A 600-word answer to a question customers keep asking is ideal.
Write a 600-word post for our blog on [topic]. Show me a preview first.
Give notes on the preview the way you would a writer: cut the intro, swap the example, shorter headline. When it's right, say so.
Good. Save it to Sanity as a draft in the [category] category.
Claude fills in every field your site has, from the title and body to images, search description and category, and saves the lot as a draft. Open Studio and it's sitting at the top of your posts with a Draft badge. Your live site hasn't changed.
Saved as a draft with every field filled in. Nothing is live yet.
Step 7: Publish it yourself
Read it in Studio, fix anything you like by hand and press Publish. That's the whole loop. From here on it's steps 6 and 7, as often as you like.
If something slips through anyway, Sanity keeps every version of every document. Open the post's history in Studio and restore the one before.
Claude gets every key to the site except one. The publish button stays with a person.
How do we use it at Intersect?
This blog runs on exactly this set-up. This post started as a conversation, went through a few rounds of notes on a designed preview, and went into Sanity as a draft with its category, search fields and images filled in. Someone on our team pressed publish.
The animations in it show what the connection makes easy. They aren't video files. They're plain HTML and CSS that Claude wrote and saved into Sanity alongside the words, so they load fast, stay sharp on any screen, and anyone can change the wording later in Studio.
What if something goes wrong?
| If you see this | Do this |
|---|---|
| Claude can't see any Sanity projects | Disconnect and reconnect using the login you use for Studio. |
| It worked last week and now wants you to sign in again | Normal. Sanity's sign-ins for connected tools can expire after about a week. Reconnect and carry on. |
| A field comes back empty in Studio | Your site may not have that field. Claude can only fill fields that exist, and adding one is a one-off job for your developer. |
| Claude says it isn't allowed to publish | That's step 3 working. |
| You can't find connectors on your phone | Add them on the web or desktop. They work on your phone after that. |
Want it set up properly the first time?
We'll connect Claude to your Sanity site, set the permissions, write your house rules and check your site has the fields Claude needs to fill. Then we'll run your first posts with your team. If you'd rather do it yourselves, the seven steps above are all of it. Book a call
FAQs
Does the Sanity connector cost anything?
No. It's free to add on every Claude plan, Free included. Almost everything it does counts as ordinary Sanity use. The exceptions are its two image-generation tools, which use Sanity's AI credits, so block those in step 3 if you'd rather they didn't.
Can Claude see things outside our website?
It sees whatever your Sanity login can see, which is every project you're a member of. If you have more than one, name the right one in your house rules.
Do I need a developer?
Not for these seven steps. You need one when Claude needs something your site doesn't have yet, like a new type of page or a missing field.
What if our site isn't on Sanity?
Other content systems, Webflow among them, have their own Claude connectors, and the same pattern applies: connect, block publishing, test, write the rules. If your site has no content system at all, that's the place to start.
Related reading
- Prompt It in Claude, Then Publish It on Your Website
- How to get your brand into Claude so it designs on-brand
- 10 things Claude Design can do that most teams miss
Sources
- Sanity: Sanity MCP server, accessed 29 October 2026
- Sanity: Roles, accessed 29 October 2026
- Claude Help Center: Use the Connectors Directory to extend Claude's capabilities, accessed 29 October 2026
- Claude: Connectors directory, accessed 29 October 2026