Skip to content
SEO Navigator Docs

What is SEO Navigator MCP?

SEO Navigator MCP is a Cloudflare Worker that exposes a Model Context Protocol endpoint. You point Claude — Desktop or Code — at the worker, hand it a token, and Claude can manage content across many websites at once.

The MCP is the engine, but these docs cover the whole job: the per-platform workflows for getting content and layout in, and the SOPs for testing it and measuring how much time the automation saves. See Beyond the tools below.

What you get

Section titled “What you get”

Tools Claude can call (74 built-in):

  • List sites and verify connectivity — list_sites, ping_site, diagnose_site, list_wp_users
  • Blog posts — create/update draft, schedule, unschedule
  • Pages — Gutenberg, Elementor template duplicate, Duda Pages v2, code-first
  • GitHub markdown sync — content team writes, design team deploys
  • Astro routes — vibe-code in chat, push to a Cloudflare Pages repo
  • Reporting & analytics — Google Analytics 4, Search Console, Google Sheets, Microsoft Clarity, GoHighLevel CRM metrics, and a one-shot generate_seo_report
  • Audit log — every call is recorded by user

Every write tool passes a confirm gate, and tokens carry a risk-tier cap, so a leaked or mis-scoped token can be contained — see Tokens & scoping.

When a site has wordpress/mcp-adapter installed, the worker transparently proxies its tools too — Elementor element- level editing, WooCommerce, etc.

What it does NOT do

Section titled “What it does NOT do”

Three deliberate guardrails enforced in code:

  1. Never publish-now. create_draft writes status=draft. schedule_draft requires scheduled_at at least 60 seconds in the future. No tool hits the “publish” endpoint directly.
  2. Never delete posts or pages. delete_post, publish_post, and similar tools are simply not registered. Proxy tools matching delete-page, remove-post are filtered out of tools/list.
  3. Element-level deletes inside Elementor are allowed. delete-element, remove-section are page-content edits, not page deletion.

One documented exception: delete_astro_route removes an .astro file from a GitHub repo branch. This is allowed because (a) Astro pages are code files, not CMS content; (b) git history preserves the file; (c) the tool is super-admin tokens only at runtime.

Beyond the tools — workflows & SOPs

Section titled “Beyond the tools — workflows & SOPs”

The tool list is the raw capability; the rest of these docs are how you actually use it to build a site:

  • Workflows — task guides per platform: WordPress (MCP), Duda (Dev Mode), Astro (in code), plus the shared content/design team flow.
  • SOPs — the two automation pillars end to end: auto-input (getting content/layout in) and automation testing (QA, Playwright and not), with a time-savings model estimating hours saved per template.
  • Testing scenarios — recordable, step-by-step walkthroughs of the tools in action.

Why it exists

Section titled “Why it exists”

Claude talks to one MCP server at a time. If you have ten WordPress sites, you’d need ten connectors. SEO Navigator is a fan-out — one connector on Claude’s side (Desktop or Code), many sites on the backend, token-scoped so each role only sees what it needs.

What it’s not

Section titled “What it’s not”
  • Not a CMS — content lives in WordPress, Duda, or your Astro project.
  • Not a publisher — final publish always happens manually in the destination dashboard.
  • Not an AI — Claude does the writing. This server is plumbing.

Next

Section titled “Next”

→ Quick start (5 minutes) → Architecture