← ClaudeAtlas

seo-gsc-comparelisted

Compare Google Search Console performance between two time periods to identify trends and changes. Supports month-over-month (MoM), year-over-year (YoY), or custom date ranges. Use when user says "GSC compare", "period comparison", "month over month", "year over year", "compare performance", "MoM", or "YoY".
YogeshKu7877/claude-seo-skills · ★ 3 · Data & Documents · score 79
Install: claude install-skill YogeshKu7877/claude-seo-skills
# GSC Compare — Period-over-Period Comparison @skills/seo/references/mcp-degradation.md @skills/seo/references/gsc-api-reference.md Compares GSC performance between two date periods — by default month-over-month (last 28 days vs prior 28 days). Surfaces top movers by page and query with directional indicators. ## MCP Check Before calling any GSC tool, verify the MCP is connected: 1. Use ToolSearch with query `+google-search-console` 2. If tools returned — note the actual tool name prefix, proceed to Inputs 3. If no tools returned — display the GSC MCP error template from `references/mcp-degradation.md` and stop: ``` ## Google Search Console MCP Not Available The `/seo gsc compare` command requires the GSC MCP, which is not currently connected. **What you can do:** - Use `/seo technical <url>` for crawlability and indexability analysis (no live data) - Use `/seo audit <url>` for a full static SEO audit **To connect GSC MCP:** - Install and configure a Google Search Console MCP server (see README for setup) - Add it to ~/.claude/mcp.json at user scope (NOT project scope) - Verify GSC property access before running commands (domain vs URL prefix format) - See references/gsc-api-reference.md for property format details ``` ## Inputs - `site`: The GSC property URL. Accept both formats: - Domain property: `sc-domain:example.com` - URL prefix: `https://example.com` or `https://www.example.com` - If user provides a bare domain (no prefix), call `list_sites` to ide