An SEO content agent in your Slack, deployed from one button.

The other pages here connect seodraft to an agent you already use. This one is the agent: an open-source template built on eve, Vercel's agent framework. Deploy it, @mention it in a channel, and it audits your site, builds the content map, plans your topic bank, writes the next scheduled article against seodraft's rules, and delivers it once someone in the thread approves.

Clones the template into your GitHub and provisions the Slack connector, the seodraft connector and a private Blob store.

Source on GitHub · Apache-2.0

A thread with the agent

  1. you@seodraft what's next on the calendar?
  2. seodraftNext scheduled: "How long does a Shopify migration take?" for Tuesday. Brief: intent, template, angle, three accepted evidence pieces, outline. Write it?
  3. yougo
  4. seodraftBrief saved, then the body. The rules check passed. Here's the article.
  5. youship it
  6. seodraft[Approve] [Deny] approve_post — approved and delivered as a draft to your-org/your-site. Want a LinkedIn post from it?

What the template gives you

A Slack bot that answers @mentions and DMs and keeps each thread as one shared session. A live card shows what it is doing, and every approval is a button only the right person can press. Behind it, two skills drive seodraft: one for the profile, markets, evidence bank, site audit, content map, topic bank and calendar, one for the article itself, from next_write to the brief, the body, the rules check, approval and translations.

seodraft stays the system of record. The agent reads the editorial standard from seodraft when it runs, so a change to your profile reaches the bot without a redeploy. Approved articles can then be turned into LinkedIn posts, X posts and newsletter sections, each with its own style skill, a style check and a reviewer that reads the post with fresh context.

What changed with eve 1.0

eve 1.0
The template moved from eve 0.31 to 1.0.2, the first general-availability release. Sessions survive restarts, and every session, model call, tool call and approval shows up under Agent Runs in your Vercel dashboard.
Site audit and content map
The agent now runs seodraft's site audit, proposes the content map from what the audit observed, grows an approved map with the searches a cluster misses, and hands you the internal links each cluster lacks. It also works with several markets and links an article to its translations.
More approval buttons
Approving the content map, adding topics to it, and starting a site audit now stop for a button too. The audit's dry run states the cost and who pays before anyone presses it.
Private memory per writer
Standing preferences for social posts ("always end my LinkedIn posts with a question") live in eve's memory, one document per person, in a private Blob store. Earlier versions kept them in a public store.
A sharper style check
Social posts go through a banned-words list, then a decision model that judges plain English, AI phrasing, format and best practices, and the reviewer when a rule is too close to call. The researcher and the reviewer each run in their own session with only the tools they need.
A cheaper default model
The agent runs on Claude Sonnet 5.5 through your AI Gateway, with Opus 5.5 kept for deep research. Every model id sits in one file, agent/lib/models.ts.

The seodraft tools it calls

The agent reaches seodraft through its MCP server, as the person who wrote in the thread. It finds the tool it needs when it needs it, so the full catalog never sits in the model's context.

Workspace and status
Which workspace the thread is about, the profile, and where every article stands. approve_profile stops for a button.
list_workspacesget_profileupdate_profileapprove_profilepipeline_statusdataforseo_statusdelivery_status
Evidence
First-hand material an article cites: at least three accepted pieces per article.
add_evidencelist_evidence
Site audit and content map
What the site and its competitors show, and the clusters built from it. start_site_audit with confirm, approve_content_map and add_cluster_topics stop for a button.
import_sitemapcheck_ai_accessstart_site_auditsite_audit_statusget_audit_findingssubmit_content_mapapprove_content_mapget_content_mapget_cluster_ideasadd_cluster_topicsget_link_suggestions
Topic bank
The questions to write about and their measured volumes. Every call that can spend your DataForSEO balance stops for a button, and so does archive_topic; merge_topics only when it confirms.
list_topicsadd_topicspropose_topicssuggest_topicsrefresh_metricsresearch_topicsubmit_topic_analysiscomplete_onboardingmerge_topicsarchive_topic
Calendar
What gets written and when. None of these stop for a button.
plan_topicsnext_writecalendar_viewlist_calendarschedule_entryreschedule_postunschedule_post
Writing, approval and delivery
The brief, the body, the rules check and the hand-off. approve_post and deliver_draft stop for a button, and archive_post only when it confirms.
get_skillget_postlist_postsget_linkgraphupsert_postrun_gateapprove_postdeliver_draftarchive_postlink_translationunlink_translation

Deploy it

You need a seodraft account with one workspace, a Vercel account with AI Gateway access, and a Slack workspace where you can install an app.

  1. 1

    Press Deploy. Vercel clones the repo and opens the connectors it needs: Slack, with its event trigger at /eve/v1/slack, and a private Blob store for files and per-writer memory.

    Deploy to Vercel
  2. 2

    Add the seodraft connector. seodraft is not in the Vercel Connect catalog yet. In the seodraft.app row choose Add, then OAuth, then Managed, and enter the server URL. Connect discovers the endpoints and registers the client with seodraft on its own.

    https://seodraft.app
  3. 3

    @mention the bot in Slack. The first time it needs seodraft it sends you a private sign-in link. Authorize your own seodraft account and the thread continues where it was.

Who approves what

Each person in Slack signs in to seodraft as themselves through Vercel Connect, and sees only the workspaces their account can open. There is no shared API key: Slack and seodraft go through Connect, and Blob and the model use the project's OIDC token.

Approving an article, the profile or the content map, adding topics to the map, delivering a draft, retiring or merging, starting a site audit, and every call that can spend your DataForSEO balance stop for an approve/deny button in the thread. Reads, drafting and the rules check run without one. The list lives in one file, agent/lib/seodraft-approval.ts, and a test in the template fails when it changes by accident.

Approval delivers the article as a draft: a file in your git repository or a draft document in Sanity, whichever the workspace is set up for. Publishing stays in your CMS.

Limits

  • No scheduled runs yet. seodraft issues user tokens only. eve 1.0 lets a schedule run with a person's sign-in, which would allow a weekly digest, but the template doesn't ship one: writing starts from a message in Slack.
  • The Slack surface runs only on a deployment. Locally, pnpm dev opens a terminal chat that reaches seodraft but not Slack.
  • The model runs through Vercel AI Gateway on your Vercel account, so model usage is billed by Vercel, apart from the seodraft plan.

Questions about seodraft for Slack

What is eve?
eve is Vercel's open-source framework for building agents. It finds an agent's channels, connections, tools, skills and memory from the files under agent/, and runs the same way locally and on Vercel. This template is forked from Vercel Labs' eve Content Agent Template and follows its eve 1.0 version.
Do I need a seodraft account?
Yes. The agent works in your seodraft workspace: profile, evidence, site audit, content map, topics, calendar, rules and delivery all live there. seodraft is $9/month for up to 3 people, with 7 days free and no card.
Which model does it use, and who pays for it?
Claude Sonnet 5.5 by default, with Opus 5.5 for deep research and GPT-6.1 Sol for the reviewer, all through the AI Gateway of your own Vercel team. You pay Vercel for model usage; seodraft never sees that bill. Change any of them in agent/lib/models.ts.
I deployed an earlier version. How do I update?
The Deploy button copied the template into a repository of your own, so it doesn't update itself. Copy the new template over your repository, create a private Blob store and connect it to the project in place of the public one, and deploy. Saved writer preferences don't carry over from the public store: each person states them again.
Can everyone in my Slack use it?
Anyone in a channel the bot is in can @mention it. Each person signs in to seodraft with their own account, so the bot only reaches the workspaces that person can open.
Can I change how it writes or what it asks before acting?
Article voice and structure come from your seodraft profile. The order of work lives in the seo-planning and seo-article skills, social voice in the style skills, and approvals in agent/lib/seodraft-approval.ts. It is your repository; edit any of them.
Is it free?
The template is open source under Apache-2.0. Running it uses your Vercel account for hosting and model calls, and your seodraft plan for the workspace.

Other agents

  • Claude · A skill for the workflow, an MCP connection for the data behind it.
  • ChatGPT · Connect seodraft as a ChatGPT app through developer mode.
  • Cursor · One deeplink or an mcp.json entry, plus a plugin that brings the skills and the rule into your editor.
  • Grok Bot · A ready-made template that carries seodraft's two skills, then walks you through connecting the server.
  • Agents · Other MCP clients

Related

  • Agents hub · Every client seodraft runs in, and how each one connects.
  • MCP server · The tools the agent calls behind each Slack message.
  • Delivery to your CMS · Where an approved article lands, and why it lands as a draft.
  • Pricing · One plan, $9/month for up to 3 people, 7 days free with no card.

Create your seodraft account.

7 days free, no card needed. Then $9/month if you subscribe.