SEO Performance MCP
Get per-URL SEO verdicts—refresh, expand, merge, or kill—by blending Search Console, GA4, Matomo, Clarity, and AI citation signals inside your agent.
Overview
SEO Performance MCP is an MCP server for the Launch phase that delivers per-URL SEO verdicts using GSC, GA4, Matomo, Clarity, and AI citation inputs.
What is this MCP server?
- Per-URL actions: refresh, expand, merge, kill
- Data sources: Google Search Console, GA4, Matomo, Microsoft Clarity, AI citations
- Env-driven setup: GSC service account, GSC_SITE_URL, Matomo URL/token/site id
- npm `@automatelab/seo-performance-mcp` v1.0.0 with npx `-y` runtime hint
- Stdio transport for Claude Code and Cursor workflows
- Version 1.0.0
- Five integrated signal types named in catalog description
- Four verdict actions: refresh, expand, merge, kill
What problem does it solve?
Your site has dozens of URLs and fragmented dashboards, so you never confidently decide which pages to refresh, merge, or delete.
Who is it for?
Solo operators with Search Console and analytics already wired who want agent-native content portfolio decisions.
Skip if: Pre-launch sites with no GSC data, or builders who only need keyword research without performance history.
What do I get? / Deliverables
Your agent returns structured refresh/expand/merge/kill guidance per URL so you can prioritize content work in one pass.
- Per-URL refresh/expand/merge/kill recommendations
- Unified view across up to five signal families in agent chat
- Actionable content backlog for solo SEO maintenance
Recommended MCP Servers
Journey fit
Launch SEO is when you decide which URLs deserve investment; this server outputs actionable page-level decisions instead of raw metric dumps. SEO subphase fits because verdicts are tied to search performance and content portfolio hygiene, not pure error monitoring.
How it compares
Analytics-backed SEO verdict MCP, not a keyword generator or a standalone rank tracker UI.
Common Questions / FAQ
Who is SEO Performance MCP for?
Indie site owners and small SaaS teams who monitor GSC and analytics and want MCP tools to rank-fix content by URL.
When should I use SEO Performance MCP?
Use it during quarterly content audits, after traffic plateaus, or when AI citations and classic SEO metrics disagree on a URL’s value.
How do I add SEO Performance MCP to my agent?
Add stdio config for `@automatelab/seo-performance-mcp`, set GSC_SERVICE_ACCOUNT_JSON and GSC_SITE_URL (plus Matomo vars if used), then run verdict tools from the agent.