DispatchSEO

             

Website  ·  Discord  ·  Discussions  ·  Hosted version

Self-hosted has zero feature limitations. Everything the paid
cloud does, this repo does today, in your own accounts, at $0.

_{▶ Watch the preview}

⚡ How it works

1. Your AI researches. The Claude app at claude.ai, or a coding agent (Claude Code, Codex, Cursor), connects to DispatchSEO over MCP, reads the served playbook, and mines keywords from your Search Console data, Google Autocomplete, and what it already knows about your product. Ideas land in a queue with the reasoning attached.
2. You approve, or don't. Each idea is a card on the dashboard: the keyword, why it's winnable, the angle. Approve, reject, or reorder. Prefer full autopilot? Flip on auto mode and skip the queue entirely.
3. The pipeline builds. Every morning a scheduled job picks the oldest approved idea and builds it into a real pull request against your site's repo: a guide or a small free tool, checked against the live SERP and run through a sameness reviewer so page twelve doesn't read like page three.
4. It tracks what happened. Daily rank checks, hourly Search Console snapshots, index verification, and a journey view that tells you which SEO stage you're actually in. When a scheduled job breaks, you get a red banner and an email instead of silence.

The backend is deliberately boring: state, scheduling, and an approval gate. The thinking happens in your agent, where your product knowledge already lives.

🤖 Which coding agent

DispatchSEO talks to your agent over MCP, so "which agent" is a real question with a real answer — including the parts that aren't finished yet.

Connecting is one paste and gets you the whole tool set: research, the queue, approvals, backlinks, reports, and building a guide when you ask for one. The overnight builder is the separate thing — scheduled jobs that run an agent with nobody watching — and all three do that. Every workflow carries every agent and asks the dashboard which to run, so switching agent takes effect on the next scheduled run with no repo change.

The honest difference is who pays: Claude Code runs on a subscription you already have, Cursor runs on your Cursor plan's API key, and Codex is metered by OpenAI per run.

You can also skip coding agents entirely. Add DispatchSEO to the ordinary Claude app at claude.ai as a custom connector and your Claude does the research and the writing on the subscription you already have, then hands the article back for the backend to check, finish and publish. It won't build interactive tools or run the overnight builder, and claude.ai has to be able to reach your install, so that path wants a public URL rather than a laptop. ChatGPT can't connect yet.

docs/AGENTS.md has the details, the support tiers, and how to add an agent.

✅ What you need before you start

• Somewhere to publish. Either WordPress you host yourself, connected once from Settings with an application password and posted to directly, or your site's source in a GitHub repo, where content arrives as pull requests. Wix, Squarespace, Shopify, Webflow and Ghost have neither door and won't work.
• An AI to drive it. Your AI is the engine, and it can be the ordinary Claude app at claude.ai or a coding agent. Claude Code runs on the Claude subscription you already pay for; Codex and Cursor do everything Claude Code does here, including the overnight builder. Codex is metered by OpenAI per run, and Cursor builds draw on your Cursor plan's included usage. See the table above.
• A machine with Docker (~1 GB RAM). A laptop works for a test drive, but a machine that stays on is much better for daily use - a $5 VPS, a Raspberry Pi, a desktop that never sleeps. Schedules only run while the machine is awake.
• Google Search Console access to your site.

That's the whole list. No API keys to buy, and no account on our side.

📖 Documentation

Everything is at dispatchseo.com/docs - every page, every setting, every tool.