Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

Developer terminal with Claude Code AI assistant automating SEO content pipeline, showing code and workflow panels
Open SourceScore: 70

DispatchSEO: Run an Overnight SEO Content Pipeline That Ships PRs from

DispatchSEO (MCP + Claude Code) automates SEO: keyword research, approvals, and overnight PR generation. Self-hosted at $0, it turns your agent into a content pipeline—approve ideas, wake up to shipping PRs.

·1d ago·3 min read··4 views·AI-Generated·Report error
Share:
Source: github.comvia hn_claude_codeSingle Source
How do I use DispatchSEO to automate SEO content creation with Claude Code?

DispatchSEO is an open-source (AGPL-3.0) SEO manager that connects to Claude Code via MCP. It mines keywords from Search Console, lets you approve ideas in a dashboard, and runs scheduled jobs that build content into pull requests against your git repo. Self-host with Docker.

TL;DR

DispatchSEO gives Claude Code keyword research, approval queues, and an overnight builder that ships SEO content as pull requests—all self-hosted at $0.

What Changed

DispatchSEO (AGPL-3.0, GitHub) is an open-source SEO manager that hands the thinking to Claude Code. Instead of crawling your homepage like Semrush or SEObot, it connects to your agent over MCP and gives it the missing half: keyword research, content workflows, and rank tracking.

The core loop: your agent mines keywords from Google Search Console data, Google Autocomplete, and its own knowledge of your product. Ideas land in a dashboard queue with reasoning attached. You approve, reject, or reorder—or flip on auto mode. Then a scheduled job (Docker cron) picks the oldest approved idea and builds it into a pull request against your site's repo: a guide or small free tool, checked against the live SERP and run through a sameness reviewer.

Tech stack: NextJS 16, TypeScript, Tailwind v4, PostgreSQL (bundled container or Supabase), MCP server, Claude Code as the headless builder, Docker Compose, GitHub Actions, Google Search Console API + DataForSEO + SerpApi, Resend for email alerts.

What It Means For You

If you run a git-based site (Astro, Next.js, Hugo—anything in a GitHub repo), DispatchSEO turns Claude Code into an always-on SEO content engine. The overnight builder runs unattended: a scheduled job spins up Claude Code in a container, reads the playbook, and ships a PR by morning. You wake up to a diff, not a blank page.

This fits the broader MCP trend. We covered how Claude MCP turns SEO audits into a chat, undercutting $10K agencies; DispatchSEO extends that idea from audit to production. It also aligns with the community shift to MCP minimalism—one server that does a lot, not twenty that bloat context.

Cost is the differentiator. Claude Code runs on your existing subscription; Codex is metered per run. Self-hosting means zero feature limits—everything the paid cloud does, you get for $0 in your own accounts.

Try It Now

  1. Clone the repo: git clone https://github.com/NeoZi12/dispatchseo
  2. Run docker compose up — app, DB, cron, and builder all spin up. Needs ~1 GB RAM.
  3. Connect Claude Code via MCP: one paste gets you research, queue, approvals, backlinks, reports, and guide building.
  4. Point it at your GitHub repo (git-based only—WordPress won't work).
  5. Approve a keyword idea, then let the overnight job build the PR. Check the dashboard for rank tracking and Search Console snapshots.

Enable auto mode to skip the queue entirely. When a scheduled job breaks, you get a red banner and an email—no silent failures.

Docs in docs/AGENTS.md cover support tiers and how to add agents. Both Claude Code and Codex are first-class; switching agents takes effect on the next scheduled run with no repo change.

The Honest Tradeoff

DispatchSEO doesn't replace your SEO judgment—it automates the grind. The backend is deliberately boring: state, scheduling, approval gate. The thinking lives in your agent, where your product knowledge already resides. That's the point: you're not teaching a crawler what you do; you're pointing your own brain at the SERP.


Source: github.com

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from multiple verified sources, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

Claude Code users should treat DispatchSEO as a template for agent-driven, scheduled content pipelines. The overnight builder pattern—cron job → containerized Claude Code → PR—is directly reusable for any recurring content task, not just SEO. Connect it to your existing Search Console and GitHub, and you've got a self-healing content operation that runs on your subscription. Adopt the approval-gate workflow: agent proposes, human disposes. This prevents the 'page twelve reads like page three' problem by forcing a sameness check, and it keeps you in control of brand voice. For teams already using MCP servers, DispatchSEO is a single server that replaces multiple point tools—keyword research, rank tracking, content generation—reducing context bloat. Finally, note the cost asymmetry: Claude Code's flat subscription makes overnight automation free, while Codex metering would rack up charges. If you're evaluating agents for unattended work, this is a concrete argument for Claude Code. Try the auto mode on a low-stakes blog first, measure the PR quality, then scale.
Compare side-by-side
Claude Code vs DispatchSEO
Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in Open Source

View all