dispatchseo.com valid
DispatchSEO
Open-source SEO manager driven by the AI you already pay for: the ordinary
For agents: Open-source SEO manager driven by Claude or a coding agent: research, content shipped to your repo, and rank tracking on self-hosted or cloud infrastructure.</b
seoopen-sourcerank-trackingai-agentclaudeself-hosted
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T13:04:00.134Z. Cached copy · Source on dispatchseo.com
# DispatchSEO
> Open-source SEO manager driven by the AI you already pay for: the ordinary
> Claude app at claude.ai, a coding agent (Claude Code, Codex, Cursor), or any
> other MCP client. Your AI already knows your product, so DispatchSEO gives
> it the missing half: keyword research it can act on, articles that ship as
> pull requests to your own repo or straight into self-hosted WordPress, rank
> tracking, and a human approval dashboard. Self-hosted with one Docker
> command, AGPL-3.0. A hosted version exists at dispatchseo.com, but
> self-hosting has zero feature limitations.
## What it is, in one paragraph
DispatchSEO is a backend, not a writer. It stores state (a suggestions queue,
keywords, published pages, rankings, Search Console stats, backlink
prospects), runs schedules (daily rank checks, hourly GSC snapshots, a nightly
content builder), and gates everything behind a human approval step. The
thinking - research, judgement, writing - happens in your own AI: the Claude
app at claude.ai, or a coding agent (Claude Code, Codex, Cursor), which talks
to DispatchSEO over MCP. That split is deliberate: your AI already has your
product knowledge, so it does not need to crawl your homepage to guess at it.
## Key facts
- The MCP server is at /api/mcp (streamable HTTP, bearer token per project).
The bearer token IS the tenant selector - one deployment manages many sites.
- The MCP exposes state only: reads and writes against the queue, keywords,
pages, rankings, GSC stats, prospects, plus a get_instructions tool that
serves the agent playbook. Keyword research and content generation happen in
the agent, not on the server.
- Anything the dashboard can do, the agent can do over MCP. Parity between the
two is a hard rule in the codebase.
- Two ways to connect an AI. A coding agent (Claude Code, Codex, Cursor)
connects over MCP from a terminal, or the ordinary Claude app at claude.ai
is pointed at the same server as a custom connector on any paid Claude plan,
writes on the owner's own subscription, and hands the finished article back.
ChatGPT is not supported yet; the Gemini app cannot connect outside tools at
all.
- Content reaches your site one of two ways. For a self-hosted WordPress site,
articles are posted through its own API, with cover image, internal links and
schema already in place. For a code-built site, they arrive as pull requests
to your GitHub repo, opened by the coding agent or by DispatchSEO itself when
the article came from the Claude app; human approval is the default and
automatic merge is opt-in.
- So you need either a self-hosted WordPress site or a site whose source lives
in a Git repo. Hosted site builders (Wix, Squarespace, Shopify, Webflow) have
neither, and are not supported. A coding agent is not required for either
one.
- Data tiers stack: Google Search Console only (free), + a free SerpApi key
(live SERP checks), + DataForSEO (volume and difficulty, pay per call).
- You bring y
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| openseo.so | OpenSEO | interface AI and machine learning Marketing +1 | — | 50 | ✓ | ||
| coder.com | Coder | documentation AI agents and MCP Developer tools +1 | US | 64 | ✓ | ✓ | |
| squidex.io | Squidex | interface Developer tools APIs and SDKs +1 | — | 50 | ✓ | ||
| sequel.sh | Sequel | documentation AI and machine learning AI agents and MCP +1 | US | 45 | ✓ | ✓ | |
| grandranker.com | GrandRanker | documentation Marketing AI agents and MCP | — | 54 | ✓ | ✓ | |
| omnara.com | Omnara | interface AI and machine learning AI agents and MCP +1 | — | 55 | ✓ | ||
| seocontentmachine.com | SEO Content Machine | interface Marketing AI and machine learning | — | 51 | ✓ | ||
| ctrify.com | CTRify | interface Marketing AI and machine learning +2 | US | 50 | ✓ |
Machine-readable: GET /v1/resolve?q=dispatchseo.com · GET /v1/domain/dispatchseo.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage dispatchseo.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for dispatchseo.com:
1. POST https://agentwebmap.com/v1/sites/dispatchseo.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://dispatchseo.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/dispatchseo.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dispatchseo.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.