What Sanity is and how Kite works with it
Sanity is a headless content management system. It stores your site's content as documents in a dataset, and your website's code fetches those documents and turns them into pages. Your blog posts, landing-page sections, FAQs, and author bios each live as a document with fields your developers defined in code.
Kite works with that content the way a marketer on your team would. It reads your documents to understand what every page says, decides what should change based on its research, and then makes the change in Sanity. Reading works with the Sanity connection alone. Editing published text also needs your site's code imported into Kite, so Kite knows which document and field produce each page.
Marketing jobs Kite can do with Sanity
Sanity's model shapes how Kite works with it. There's no screen of pages to click through, just documents and fields, so Kite starts by reading those documents and finishes by changing the one field that produces the words a visitor sees. The jobs below follow that order.
Audit what your Sanity content actually says
Kite reads your Sanity content directly, so a content audit covers every document instead of the handful of pages someone remembered to check. It queries your dataset for the documents it needs, such as every document of your post type, along with their titles, slugs, summaries, SEO fields, and update dates. It can read the published version that visitors see or the drafts still waiting in your Studio.
Say you changed your pricing in the spring. Kite can pull every post and page that still quotes the old plan names, list them with the field each mention sits in, and propose the replacement wording for each. The same read finds posts with an empty meta description, landing pages whose headline no longer matches your positioning, and FAQ answers that contradict each other.
Change the wording behind a page
This is the job that turns a recommendation into a shipped change. When Kite's research says a page should say something different, Kite finds the Sanity document and field that produce that text on the page and replaces it with the new copy.
Here's what that looks like in practice. Kite runs your buyer questions through ChatGPT and sees that the answers quote a competitor's pricing FAQ and skip yours, because your answer opens with a paragraph of history. Kite rewrites that answer so the first sentence carries the point. It shows you the current text and the new text, and once you approve, it writes the new answer into the FAQ document's field.
Editing a published document in Sanity publishes it, because the change lands on the live version rather than a draft. So after the write, Kite reads the document back to confirm the new wording is there and gives you the page's address. Your site shows the change as soon as it fetches content again, which for many sites is the next rebuild or the next time its cache refreshes.
Retire content you no longer want live
Some pages should go away rather than get rewritten. A webinar landing page from two years ago or a post about a discontinued feature can confuse visitors and the AI answers that cite it. When you decide a page should go, Kite deletes its Sanity document. By default Sanity keeps a deleted document in its history, so it can be recovered later.
Hand a task to Sanity's Content Agent
Sanity has its own AI assistant, the Content Agent, that works inside your Sanity organization. Kite can send it a single prompt and read the reply. That's useful when your team has already set the Content Agent up for a job inside Sanity and you want Kite to use its answer in its own work.
What Kite reads and changes in Sanity
Information Kite can read
- Documents of any typeKite queries your dataset for posts, pages, FAQs, authors, or any other document type your schema defines, with all their fields. This is the raw material for an audit.
- A single document by its IDKite reads one document in full when it needs every field on a specific page.
- Published versions and draftsKite can read what's live or what's still waiting in your Studio, so it knows whether someone on your team is already reworking a page.
- Project detailsKite reads the project's name and Studio address so it works in the right place.
Information Kite can create or change
- The text of a field on a published documentOn an imported site, Kite replaces the wording of one field at a time, such as a headline, a summary, a call to action, or an FAQ answer, then reads it back to confirm it's live.
- Documents you're retiringKite deletes a document you've decided to take down.
How Kite connects to Sanity
Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers.
Add an API key for your Sanity project. Kite uses the access granted to that key. You give Kite your project ID and an API token you create in Sanity's management console. A token with Viewer permissions lets Kite read your content. To let Kite change content, create the token with Editor permissions instead.
You can connect Sanity from Kite's Integrations page. If you import your site's GitHub repository and Kite sees that the site gets its content from Sanity, it asks you to connect Sanity right there. Importing the site is what lets Kite match each page on your site to the documents behind it, and it's required for editing published text. Then start with a goal, such as asking why the AI answers about your category quote your competitors and not you. Kite proposes which pages to change and what each one should say before it touches anything in Sanity.
Playbooks using Sanity
- How to make a Sanity site easier for AI search engines to read and citeKite scans your live site for the checks that decide whether AI agents can find and use it, traces each fix back to the Sanity field that controls it, rewrites the copy, and scans again to measure the gain.Coming soon
- How to publish a blog post to SanityKite reads your published posts to learn how they're built, writes a new post to fit every field in your post type, and checks it on your site once your editor publishes it in the Studio.Coming soon
Where Sanity fits in Kite's marketing work
Sanity is where the fix ships. Kite measures how often ChatGPT, Gemini, Perplexity, and Claude mention you for your buyers' questions and reads the pages they cite instead of yours. When the gap comes down to what one of your pages says, Kite rewrites the field in Sanity that holds that copy. Then it runs the same questions again to see whether your standing changed.
Kite's readiness scan scores how well AI agents can find and use your site and ranks each fix by the points it would recover. Where a fix is a matter of wording, such as a page that never says plainly what your product does, Kite makes it in Sanity and re-runs the scan.
Review and approval
Kite proposes work by default. A team approves it with the Approve button on a proposed plan or with a reply in the conversation, in the Kite web app or in Slack. Teams that want Kite to act first can turn that on. With Sanity this matters more than usual, because an edit to a published document goes live the moment it's saved. So before an edit, Kite shows you the current text and the new text, and when the match in Sanity isn't exact, it also names the document and the field and asks you to confirm. When the same wording appears in more than one place, Kite lists each match and asks which one you mean.
Limits and product-specific details
- Kite edits existing content. Kite changes the wording of documents that already exist and deletes documents you're retiring. Your editor creates new documents, such as a new blog post, in Sanity Studio, and Kite can write every field of that post ahead of time.
- One field per edit. A change that touches a headline and a summary is two edits, and Kite proposes them together so you can approve both.
- Layout and design live in your code. Sanity holds your words, while your site's code decides how they look. On an imported site, Kite changes layout, styling, and copy that's written into the code through your GitHub repository instead of through Sanity.
Common questions
How is Kite different from Sanity's own AI features?
Sanity's AI features, such as AI Assist and the Content Agent, work inside Sanity on the instructions your team writes for them. Kite starts from your marketing goals instead. It researches your buyers, your competitors, and how AI answers describe your category, decides which pages need to change, writes the new copy in your brand voice, makes the edit in Sanity, and measures whether it worked.
Can Kite tell me whether a piece of copy lives in Sanity or in my site's code?
Yes. On an imported site, Kite knows which pages draw their content from Sanity and which copy is written into the code, so it can tell you where a headline lives before anyone goes looking. That also decides the route: Kite changes Sanity copy in Sanity and code copy through your repository.
Will Kite overwrite a draft my editor is working on?
No. Kite writes to the published version of a document and leaves drafts alone, so your editor's work stays exactly as they left it. Kite can read that draft before it proposes a change, which tells it someone is already reworking the page. That's worth settling together, because when your editor publishes the draft later, its text replaces the published version, including Kite's edit.