---
You don't open a new tool — you just ask, in plain English, inside **Claude** (or Cursor / Cline / Codex):
> **You** *"What should I write about next?"*
>
> **🦖 SEOMonster** Pulls your Search Console and surfaces three topics you're *almost* ranking for — positions 8–20 with real demand — ranked by opportunity. Say the word and it drafts the brief.
| You ask … | … SEOMonster does |
| :-- | :-- |
| *"What should I write about next?"* | Surfaces near-ranking topics from **your own** Search Console demand |
| *"Is this page ready to publish?"* | Runs the technical-SEO + structured-data checks before you ship |
| *"Get this indexed."* | Nudges Google (Indexing API) and Bing / Yandex (IndexNow) |
| *"Did my change actually move rankings?"* | Before/after attribution vs a matched control group — with a confidence interval, not a guess |
| *"Is ChatGPT recommending us, or our competitors?"* | Tracks your brand's **share of voice** across the AI answer engines |
**70 tools** across Search Console, GA4, PageSpeed, Cloudflare, AI-citation tracking, keyword discovery, and technical SEO — every one returning the same JSON result envelope, every one driven by your own credentials. No new dashboard to learn; you chat with the assistant you already use.
> [!NOTE]
> Published on PyPI as **`seo-monster`** (so the command is `uvx seo-monster`). The import package is `seo_mcp`; `seo-mcp` is a dev/local alias. The package ships **zero secrets** — every credential is resolved at runtime from your own environment or config file.
- **Your data, your machine.** User-credential-driven; nothing is sent to any third party.
- **Read-first, safe by default.** Reads always work; the two routine writes (sitemap submit, indexing request) are on by default; the Cloudflare write tools (cache purge, redirects, settings, managed robots.txt) are gated behind `SEO_MCP_ALLOW_DESTRUCTIVE`, and the riskier ones also need a per-call `confirm` token.
- **Lean.** Standard library + the `mcp` SDK + the Google client libraries; PageSpeed and Cloudflare ride on `urllib`, no extra HTTP dependency.
## Quickstart
> [!TIP]
> Fastest path: the **one-click install** buttons above. Or add it to any MCP client by hand:
```json
{
"mcpServers": {
"seomonster": { "command": "uvx", "args": ["seo-monster"] }
}
}
```
Run the one-time Google sign-in once — `uvx --from seo-monster seo-monster auth` — then ask your assistant to call **`system_status`** to confirm what's connected. Full per-client setup and credentials are in [Install](#install) and [Auth](#auth).
## How it works
```mermaid
flowchart LR
U["You — plain English"] --> H["Claude · Cursor · Cline · Codex"]
H -- "MCP · stdio" --> S["SEOMonster
