google-seo-mcp
Helps developers install, authenticate, and debug the Google SEO MCP server for external data access.
Install
mkdir -p .claude/skills/google-seo-mcp && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13793" && unzip -o skill.zip -d .claude/skills/google-seo-mcp && rm skill.zipInstalls to .claude/skills/google-seo-mcp
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Expert skill for installing, configuring, and troubleshooting the Google SEO MCP server.Key capabilities
- →Install the Google SEO MCP server globally or locally
- →Configure Google Search Console using OAuth 2.0
- →Set up Bing Webmaster Tools with an API key
- →Configure Google Analytics 4 using a service account JSON key
- →Run internal health checks to verify API tokens and connectivity
- →List authorized sites for configured accounts
How it works
The skill provides commands to install, configure, and diagnose the Google SEO MCP server, handling authentication flows for Google Search Console, Bing Webmaster Tools, and Google Analytics 4.
Inputs & outputs
When to use google-seo-mcp
- →Troubleshooting MCP connection issues
- →Authenticating with Google Search Console
- →Running health checks for SEO tools
About this skill
Google SEO MCP Expert Skill
This skill enables agents to manage the Google SEO MCP server (Google, Bing, and GA4). Use this to resolve configuration issues, list sites, and run performance queries.
🚀 Quick Start (Recommended)
Run the server directly without installation to verify setup:
npx google-seo-mcp setup
🛠️ Installation
Global Installation (CLI access)
npm install -g google-seo-mcp
Local Development
npm install && npm run build
⚙️ Configuration Patterns
1. Google Search Console (OAuth 2.0)
The default and most common way. Initiates a local server at localhost:3000 for browser authorization.
google-seo-mcp setup --engine=google
2. Bing Webmaster Tools
Requires an API key from Bing Webmaster Settings.
google-seo-mcp setup --engine=bing
3. Google Analytics 4 (Service Account)
Primary support for Service Accounts. JSON key file path is required.
google-seo-mcp setup --engine=ga4
🔍 Diagnostic & Debugging Workflows
If the user reports "0 results" or "not connected" errors, follow this diagnostic loop:
Step 1: Check Connectivity
Run the internal health check to verify API tokens and connectivity.
google-seo-mcp diagnostics
Step 2: Verify Authorized Sites
Verify which sites are actually authorized for use.
google-seo-mcp sites
Step 3: Verbose Debugging
Enable the internal logger to track account resolution and site filtering. Logs are sent to stderr.
DEBUG=true google-seo-mcp sites_list
🧪 Advanced Account Management
List All Configured Accounts
google-seo-mcp accounts list
Site Boundary Management
Google SEO MCP allows restricting an account to specific sites.
# Add a site to an account's whitelist
google-seo-mcp accounts add-site [email protected] --site=https://example.com/
# Remove an account entirely
google-seo-mcp accounts remove [email protected]
💡 Troubleshooting "0 Results" Guide
Common reasons for empty results:
- Protocol Mismatch:
https://example.com/(URL prefix) is different fromexample.com(Domain). - GSC Data Lag: Data is typically unavailable for the last 2-3 days. Query ranges older than 3 days.
- Account Scoping: The site might not be in the account's configured boundary. Use
google-seo-mcp sitesto confirm.
When not to use it
- →When managing SEO tools other than Google, Bing, or GA4
- →When the issue is not related to configuration or connectivity of the MCP server
- →When the user does not have access to required API keys or service accounts
Prerequisites
Limitations
- →The skill is for Google SEO MCP server management.
- →It requires specific API keys for Bing Webmaster Tools.
- →It requires a JSON key file path for Google Analytics 4 service accounts.
How it compares
This skill offers a command-line interface for direct management and diagnosis of the Google SEO MCP server, providing specific commands for each service and troubleshooting steps, unlike manual web-based configuration.
Compared to similar skills
google-seo-mcp side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| google-seo-mcp (this skill) | 0 | 1mo | Review | Intermediate |
| local-search-ads | 0 | 5mo | No flags | Intermediate |
| developing-in-lightdash | 1 | 29d | Review | Intermediate |
| zendesk | 15 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
local-search-ads
garrettjsmith
When the user wants to run ads that appear inside the Google Maps local pack / map pack results. Also use when the user mentions "local search ads," "map pack ads," "ads in the map results," "local pack ads," "Google Maps ads," "location extensions ads," or "promoted pins on Google Maps." For LSAs (
developing-in-lightdash
lightdash
Build, configure, and deploy Lightdash analytics projects. Supports both dbt projects with embedded Lightdash metadata and pure Lightdash YAML projects without dbt. Create metrics, dimensions, charts, and dashboards using the Lightdash CLI.
zendesk
vm0-ai
Zendesk Support REST API for managing tickets, users, organizations, and support operations. Use this skill to create tickets, manage users, search, and automate customer support workflows.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
controlling-spotify
oaustegard
Control Spotify playback and manage playlists via MCP server. Use when user requests playing music, controlling Spotify, creating playlists, searching songs, or managing their Spotify library.
smithery-ai-cli
smithery-ai
Find, connect, and use MCP tools and skills via the Smithery CLI. Use when the user searches for new tools or skills, wants to discover integrations, connect to an MCP, install a skill, or wants to interact with an external service (email, Slack, Discord, GitHub, Jira, Notion, databases, cloud APIs, monitoring, etc.).