How can an AI marketing agent use Storyblok for marketing?
Storyblok is a headless content management system. It stores your website's content as stories, such as pages and blog articles, and each story is built from components like a hero, a feature list, or an FAQ block. Your site's code pulls those stories in to build each page. An AI marketing agent uses Storyblok the way a content marketer on your team would. It reads what your pages say today, decides which words should change, and makes the change in the story that holds them. Kite does that work on the Storyblok site you already run, from fixing an outdated headline to rewriting the answers buyers look for in AI search. It picks what to change first using your analytics, your search data, and how often AI assistants mention you.
Marketing jobs Kite can do with Storyblok
Kite's Storyblok work starts with reading your content and ends with a published change you can measure. The jobs below follow that order.
Read what your Storyblok content says today
Kite reads your Storyblok space before it proposes a change. It pulls stories by content type, such as every Page or every Article, and narrows them by folder, tag, language, or publish date. It can open a single story in a specific language and follow the links between stories, such as an article and the categories it belongs to. It also reads your navigation links and whether each one is published, the tags you use to organize content, and the datasource entries your components draw on, such as a list of product names or regions.
That reading is how Kite finds the work. Say you've moved upmarket and now sell to mid-size finance teams, but your blog still talks about freelancers. Kite pulls every story in your blog folder, finds the articles whose intros still describe the old audience, and brings you a short list of the pages worth rewriting first.
Change the copy on a live page
When your imported site gets its text from Storyblok, Kite can change the words on a specific page. Point Kite at the page and the text, or let it propose the change itself. Kite searches your space for that exact wording and finds the story and the field inside its components that hold it, such as the headline in the second block on your pricing page. Then it writes the new text and publishes the story. Finally, it reads the story back from Storyblok to confirm that the published version holds the new words.
Say your homepage still says "Built for agencies" a month after you repositioned for in-house teams. You mention it in Kite, and Kite changes that headline in Storyblok and tells you the new line is published. If the same words appear in more than one story, Kite shows you each match and asks which one you meant.
The change lands in Storyblok itself, so your editors see it in the story like any other edit. Your site shows the new copy the next time it rebuilds or its cache refreshes, which depends on how your site is set up.
Make your Storyblok pages easier for AI answers to quote
Kite connects your Storyblok content to how your brand shows up in AI answers. It runs the questions your buyers ask through ChatGPT, Gemini, Perplexity, and Claude and records whether you appear, which competitors appear, and which pages get cited. It can also scan your live site to see how easily AI agents can find and read it, with a score out of 100 and a ranked list of fixes.
When the problem is the copy itself, Kite fixes it in Storyblok. Say Perplexity keeps citing a competitor when buyers ask how long implementation takes, and your FAQ page buries the answer in its fourth paragraph. Kite rewrites that answer so it opens with the number of weeks, publishes it in Storyblok, and asks the same question again after the page has been recrawled.
Show your Storyblok content on another site
Your Storyblok connection belongs to your Kite team, so another site Kite works on can display the same content. Say you want a new event microsite to show the three most recent articles from your Storyblok blog. Kite gives that site the read access it needs and builds the section that displays the articles. Your writers keep publishing in Storyblok, and both sites stay current.
What Kite reads and changes in Storyblok
Kite reads much more of your Storyblok space than it changes. Its edits are focused on the text inside the stories your site already displays.
Information Kite can read
- StoriesKite reads your pages, articles, and other content types, in draft or published form, filtered by folder, tag, language, publish date, or slug.
- The components inside a storyKite reads each component's fields, which is how it finds the exact block and field that holds a sentence on your page.
- TranslationsKite reads a story in a specific language when your space uses field-level translations.
- Links between storiesKite follows the relationships a story points to, such as an article's categories or author.
- Navigation linksKite reads your site's links with their slugs, names, and published status.
- TagsKite reads the tags you use to organize and filter content.
- Datasource entriesKite reads the shared lists your components pull options from, with each entry's name and value.
Information Kite can create or change
- Text fields in a storyKite writes new text into the field that holds a specific sentence, heading, or paragraph on a page of your imported site.
- Publish state of that storyKite publishes the story as part of the same change, then confirms the published version holds the new text.
How Kite connects to Storyblok
Kite works with Storyblok through a website you've imported into Kite from GitHub. When you import a site whose content comes from Storyblok, Kite recognizes it from the site's code and asks you to connect. You give Kite three things from Storyblok:
- Your Space ID, which tells Kite which space your site reads from.
- A personal access token, which you create in your Storyblok account settings. Kite uses it to edit and publish stories. A token from the space's Access Tokens screen won't work here, because those tokens can only read.
- The space's preview or public token, which your site uses to display its content.
If your space is hosted in Storyblok's US region, you also tell Kite the region. Before it saves anything, Kite checks that the personal access token can manage the space you named, so a wrong token or Space ID shows up right away.
Once you're connected, you can start with a goal instead of a list of instructions, such as "Our pricing page doesn't explain the new Team plan." Kite uses what it knows about your business to find the story that needs to change, writes the new copy, and shows you the change before it publishes.
Playbooks using Storyblok
- How to make a Storyblok site easier for AI search engines to read and citeKite scans your live site for how well AI agents can read it, traces each copy problem back to the Storyblok story and field that produce it, rewrites and publishes the fix, and scans the site again to confirm the score went up.Coming soon
Where Storyblok fits in Kite's marketing work
Review and approval
Kite proposes work by default. You approve 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. For Storyblok, approval matters because a change publishes the moment Kite makes it. When Kite proposes a change, it shows you the story, the field, the current text, and the new text, and it writes the change once you confirm. When you ask for a specific edit and quote the words to replace, your request is the approval, and Kite makes the change as soon as it finds a single exact match.
Limits and product-specific details
- The website owner or a team admin makes the edits. Kite changes Storyblok content when the request comes from the person who owns the website in Kite or from an admin on your Kite team. Other team members can still ask Kite to research pages and draft new copy for an owner or admin to approve.
- Kite edits text that's already on the page. Kite rewrites the words in an existing field, one field per change. To add a new story, or a new card to a list of features on a page, use Storyblok's editor.
- Layout and design live in your code. The look of a page, its templates, and its components are defined in your site's code, not in Storyblok's text fields. Kite changes those through the imported GitHub repository instead.
Common questions
Do I need to move my site off Storyblok to work with Kite?
No. Kite works on your Storyblok content where it already lives, your editors keep using Storyblok's Visual Editor, and your site keeps reading from the same space. If you'd rather start fresh, Kite can also build and host a new site with its own content editor, but that's a separate choice.
Will my team see Kite's changes inside Storyblok?
Yes. Kite writes directly into the story, so the new text appears in Storyblok the same way an edit from a teammate would. Your editors can review or change it there at any time.