google-search-console-tool

Installation

$npx skills add garrettjsmith/localseoskills --skill google-search-console-tool

Summary

The agent can fetch actual organic search performance data (clicks, impressions, CTR, rankings) from Google Search Console and identify quick wins like low-CTR pages needing title/meta rewrites, content gaps with unserved search demand, and indexing issues blocking traffic. Invoke when the user needs truth-layer data on what queries drive traffic, how pages perform, or which content is missing.

SKILL.MD

Google Search Console Tool

GSC has official and community MCP servers available. When connected, use it for ground-truth organic search performance data — this is the only tool that shows ACTUAL clicks and impressions from Google.

When to Use GSC vs Other Tools

You NeedUse GSCUse Instead
Actual clicks and impressions from Google✅ Only source of truth
What queries drive traffic to which pages✅ Only source of truth
Click-through rate per query/page✅ Only source of truth
Average position per query✅ Ground truthSemrush/Ahrefs estimates
Is a specific page indexed?
Core Web Vitals per page
Crawl errors and issuesScreaming Frog (more detailed)
Keyword search volume❌ No volume dataSemrush, DataForSEO
Competitor keyword data❌ Your site onlySemrush, Ahrefs
Backlink data❌ Very limitedAhrefs
Local pack rankings❌ Organic onlyLocal Falcon
Citation dataBrightLocal

Critical Distinction

GSC shows organic search performance only — not map pack, not LSA, not ads. A business can get zero clicks in GSC but rank #1 in the local pack (because map pack clicks don't show in GSC as organic clicks). Always pair GSC data with Local Falcon map pack data for complete visibility.

Core Workflows

Location Page Performance

When: User wants to know how their location pages perform in organic search.

What to pull:

  1. Filter pages by URL containing "/locations/" or your location page pattern
  2. Get clicks, impressions, CTR, average position per page
  3. Get queries driving traffic to each location page

How to interpret:

  • High impressions, low clicks (low CTR): Title tag or meta description doesn't compel clicks — rewrite them
  • High position (>20), some impressions: You're on page 2-3, close to breaking through — optimize content
  • Location page with zero impressions: Page may not be indexed, or keywords don't trigger it
  • Impressions for queries you don't have a page for: Content gap — create a page for that query

CTR benchmarks by position (approximate):

PositionExpected CTR
125-35%
212-18%
38-12%
4-55-8%
6-102-5%
11-200.5-2%

If CTR is below expected for the position, the title/meta needs improvement.

Local Keyword Discovery

When: User wants to find keywords they're already getting impressions for but not optimizing.

What to pull:

  1. All queries with impressions, filtered to last 3 months
  2. Sort by impressions descending
  3. Look for queries containing city names, "near me," service terms

What to look for:

  • Queries with high impressions but position 8+: Optimization targets — these have demand
  • Queries with "near me" variations: Confirm GBP is optimized for these services
  • Queries you rank for that you didn't expect: New keyword opportunities
  • Queries with city names you don't have a page for: Location page gaps

Index Coverage

When: User asks "is my page indexed?" or location pages aren't getting traffic.

What to check:

  1. URL Inspection for specific pages — are they indexed?
  2. Index coverage report — any errors affecting location pages?
  3. Sitemap processing — is the sitemap submitted and processed?

Common issues for local:

  • Location pages not in sitemap → add them
  • Location pages marked "Discovered – currently not indexed" → thin content, Google didn't find them valuable enough
  • Location pages blocked by robots.txt → fix robots.txt
  • Location pages with "Duplicate, submitted URL not selected as canonical" → canonicalization issue between similar location pages

Core Web Vitals

When: User's pages are slow or CWV failing.

What to check:

  1. CWV report for location pages specifically
  2. Which pages fail LCP, FID/INP, CLS
  3. Mobile vs desktop performance

For local: Mobile CWV matters most — local searches are predominantly mobile. If mobile CWV fails, fix it before other optimization.

Content Gap Identification

When: Looking for new content opportunities from actual search data.

What to pull:

  1. Queries where you have impressions but no dedicated page
  2. Queries with high impressions but position 15+
  3. Compare queries to your existing page structure

Example: GSC shows 500 impressions/month for "emergency plumber Orchard Park" but you don't have a page specifically about emergency plumbing in Orchard Park → create one.

Key Metrics and What They Mean

MetricWhat It IsLocal SEO Context
ClicksActual clicks from Google to your siteThe number that matters — this is real traffic
ImpressionsTimes your page appeared in search resultsShows demand even if you're not getting clicks
CTRClicks ÷ ImpressionsLow CTR = title/meta issue. Compare to position benchmarks
Average PositionAverage ranking position for a queryRemember: this is organic only, not map pack

What to Do Next

What You FoundNext ActionSkill
Location pages with low CTRRewrite title tags and meta descriptionslocal-landing-pages
Queries without dedicated pagesCreate pages targeting those querieslocal-landing-pages
Location pages not indexedFix technical issues (thin content, canonical, sitemap)local-seo-audit, screaming-frog-tool
CWV failing on mobileFix page speed issueslocal-seo-audit
Good organic performance, want to see map pack tooRun Local Falcon scanslocal-falcon-tool
Competitor analysis neededGSC is your-site only — use Semrush for competitor datasemrush-tool
Need this in a client reportInclude GSC data in performance reportslocal-reporting

Default next step: GSC is the truth layer. Start every performance analysis with GSC data, then supplement with other tools. If GSC shows no impressions for a keyword, either the page doesn't exist, isn't indexed, or doesn't target the keyword properly.