Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.
Scored across 18 tools
Most tools target a distinct resource and action, making selection straightforward. Minor overlap exists between get_ai_search_traffic and get_search_performance's AI-assistant traffic section, and among the three search-performance reporting tools, but descriptions are clear enough to avoid major confusion.
All tools follow a consistent lowercase snake_case verb_noun pattern: check_, generate_, get_, list_, publish_, request_, run_. The verbs are descriptive and every noun object clearly identifies the resource being acted on.
At 18 tools the set is slightly above the ideal 3-15 range, but the scope is broad enough to justify it: website management, article generation, publishing, search analytics, AI search, indexing, backlinks, and auditing. No tool feels redundant enough to remove.
The surface covers the main SEO lifecycle well: websites, keyword plans, articles, publishing, search performance, indexing, backlinks, and audits. Obvious gaps are article update/delete operations and website removal, but agents can work around these for most core workflows.
Check whether AI assistants (ChatGPT, Claude, Gemini, Perplexity) mention or cite a website when answering questions in its niche. Takes 1-3 minutes; results are cached for 7 days.
Inputs: url (required).
Start generating an SEO article for a target keyword. Returns immediately; generation takes 5-10 minutes in the background — poll get_article_status for the scheduled_date until it shows a blog.
scheduled_date is YYYY-MM-DD and defaults to today (UTC). One article is
generated per website per date; if that date already has an article the
existing blog_id is returned. Counts toward the plan's monthly limit.
Inputs: keyword (required), website_id (required), topic, scheduled_date.
Generate an AI keyword/content plan for the website. Optionally guide it with topic instructions and comma-separated primary/secondary keywords. Can take a minute or two. Set replace_existing=true only after the user explicitly approves discarding the current plan's pending topics; that path also requires confirm_replace_existing=true.
Inputs: website_id (required), primary_keywords, replace_existing, secondary_keywords, +2 more.
Show traffic the website receives from AI assistants and AI search (ChatGPT, Perplexity, Claude, Gemini, etc.): sessions, engaged pages and per-source breakdowns. Dates are YYYY-MM-DD; defaults to the last 30 days.
Inputs: website_id (required), limit, end_date, start_date.
Read a single article by blog_id. By default returns metadata and a short excerpt; set include_content=true for the full HTML content.
Inputs: blog_id (required), include_content.
Check article generation/publication status per date. Dates are YYYY-MM-DD and default to the current month. A date with has_blog=true and a blog_id means the article is ready to read via get_article.
Inputs: website_id (required), end_date, start_date.
Get the website's backlink profile from the SEOPro AI backlink network: totals, unique sources, available credits and the most recent earned backlinks.
Inputs: website_id (required).
Get auto-indexing stats for the website: how many URLs are indexed, pending or failed.
Inputs: website_id (required).
Get the website's scheduled keyword/content plan: which keywords are planned, their scheduled dates and statuses.
Inputs: website_id (required).
Get the Google Search Console performance summary for a website: clicks, impressions, CTR, average position, top keywords, AI-assistant traffic sources and device/country breakdowns.
Dates are YYYY-MM-DD; defaults to the last 30 days.
Inputs: website_id (required), end_date, start_date.
Get monthly search-performance trends (clicks, impressions, CTR, average position) for the last N months. Use to spot growth or decay.
Inputs: website_id (required), months.
List the website's top search keywords with clicks, impressions, CTR and average position. Great for finding quick wins (positions 5-15 with high impressions). Dates are YYYY-MM-DD; defaults to the last 30 days.
Inputs: website_id (required), limit, end_date, start_date.
Get content stats for a website: total articles, keywords tracked, published posts and whether SEO autopilot is enabled.
Inputs: website_id (required).
List the website's articles (drafts and published), newest first. Optionally filter by status (e.g. 'draft', 'published').
Inputs: website_id (required), limit, status.
List the websites in the user's SEOPro AI account.
Returns each website's numeric website_id (needed by most other tools),
URL, platform and autopilot status. Call this first.
Inputs: no named parameters.
Publish an article to the website's connected platform (WordPress, Shopify, Webflow, etc.). Set publish_as_draft=true to push it as an unpublished draft in the CMS instead of going live. Before calling, show the user the article and destination and obtain explicit approval. Every call requires confirm_publish=true.
Inputs: blog_id (required), confirm_publish, publish_as_draft.
Submit up to 50 URLs for search-engine indexing (Google/Bing) via SEOPro AI auto-indexing. Requires the auto-indexing feature on the account. Show the exact URL list and obtain explicit user approval first; every call requires confirm_indexing=true.
Inputs: urls (required), website_id (required), confirm_indexing.
Run a technical SEO audit on any URL: meta tags, headings, images, links, performance, content quality, security and social metadata, with a scored result. Rate-limited for free accounts.
Inputs: url (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
AI SEO agent on your Google Search Console data: audits, quick wins, content, WordPress publishing.
SEO data your AI can cite: Search Console, GA4, keywords, backlinks, SERPs and AI visibility.
Track AI visibility, SERP rankings, site audits and Search Console data, and create SEO content.
AI visibility, Google rankings, Search Console and site audit data for your SEO agent.
Add one secure layer between your agents and this server.