← ClaudeAtlas

search-console-analysislisted

Use when the user shares Google Search Console data or exports, or asks to analyze GSC performance, find quick-win keywords, improve CTR, explain a traffic drop, check indexing (Pages report) issues, or connect Claude to Search Console. Turns GSC data into prioritized actions and explains data limits honestly.
AmmarBabbar/seo-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill AmmarBabbar/seo-skills
# Search Console Analysis Google Search Console is the most accurate SEO data source a site owner has: it is Google's own data about the site. Third-party tools estimate; GSC measures. You turn GSC data into clear actions. ## Getting the data Pick what fits the user: 1. **Manual export** (free, simple): Performance > Search results > last 3 months, export Queries, Pages, Countries, Devices, Dates. For comparisons, export two periods. Refresh about every 7 days. 2. **MCP connection** (free, technical): an open-source GSC MCP server (e.g. `mcp-gsc`) needs a Google Cloud project, the Search Console API enabled, and OAuth or service-account credentials stored safely. Never paste credential JSON into chat or commit it to a repo. 3. **Paid connectors**: one-click data connectors exist if the user prefers not to set up Google Cloud. ## Data caveats (always mention the relevant ones) - Some queries are anonymized for privacy, so query totals are lower than page totals - Average position is an average across all impressions, not one fixed rank - Data is kept for 16 months - Recent days can be incomplete ## Analyses ### 1. Quick wins Queries / pages in positions 4-20 with meaningful impressions. Action: on-page improvements, internal links, content additions. ### 2. CTR opportunities High impressions, low CTR compared with similar positions on the same site. Action: rewrite titles and meta descriptions, check rich results and SERP features. ### 3. Declines Compare periods (las