Google Search Console Skill — First-Party Organic Search Data

Every other data source in the LocalSEOSkills ecosystem provides third-party estimates — modeled search volumes, estimated rankings, approximated traffic. Google Search Console is the exception. GSC delivers first-party data directly from Google: actual clicks, actual impressions, actual click-through rates, actual average positions. For the queries and pages Google shows your site for, GSC is the source of truth that no third-party tool can replicate.

The google-search-console-tool skill connects Claude to your GSC data. When a strategy skill needs to understand actual organic performance — not estimated, not modeled, but actual clicks and impressions from Google’s own records — dispatch routes to GSC.

What This Skill Does

The google-search-console-tool skill enables Claude to pull query-level performance data (clicks, impressions, CTR, average position), page-level performance data, device breakdowns, date range comparisons, and index coverage status. Combined with the local-reporting and local-seo-audit strategy skills, this data powers performance analysis grounded in first-party metrics.

Prompt: "Pull our Search Console data for the last 3 months.
Which local landing pages are getting impressions but low clicks?
That's our CTR optimization opportunity."

Skills fired: dispatch → local-reporting + google-search-console-tool
Data pulled: Page performance data, query-level metrics

Output:
CTR Optimization Opportunities — Last 90 Days

Pages with high impressions but below-average CTR:
  1. /plumbing-services-scottsdale
     Impressions: 2,400 | Clicks: 72 | CTR: 3.0% | Avg Position: 6.2
     Opportunity: Position is borderline local pack. Improving to top 3
     would increase CTR substantially.

  2. /emergency-plumber-phoenix
     Impressions: 1,800 | Clicks: 108 | CTR: 6.0% | Avg Position: 3.8
     Opportunity: Already near local pack threshold. Title tag and
     meta description optimization could lift CTR at current position.

  3. /drain-cleaning-tempe
     Impressions: 890 | Clicks: 18 | CTR: 2.0% | Avg Position: 8.4
     Opportunity: Position too low for meaningful CTR. Focus on
     ranking improvement before CTR optimization.

Priority: Page 2 (best ROI — small position improvement = large CTR gain)

Query Discovery for Local SEO

GSC reveals the actual queries Google associates with your site — including queries you didn’t know you were appearing for. This is invaluable for local keyword strategy because it shows real local query patterns that keyword research tools might miss.

Prompt: "What local queries are we getting impressions for that we don't
have dedicated pages for? These are content gap opportunities."

Skills fired: dispatch → local-keyword-research + google-search-console-tool

Output:
Queries Without Dedicated Pages — Content Gaps

Queries with 100+ monthly impressions and no matching page:
  1. "24 hour plumber scottsdale" — 340 impressions, 8 clicks
     No dedicated page. Currently matching to /plumbing-services-scottsdale
     Action: Create /24-hour-plumber-scottsdale landing page

  2. "plumber near 85251" — 220 impressions, 12 clicks
     No zip code-specific page. Matching to generic service page.
     Action: Create zip code landing page or add 85251 content section

  3. "water heater repair scottsdale" — 180 impressions, 5 clicks
     Service mentioned on main page but no dedicated page.
     Action: Create /water-heater-repair-scottsdale

Estimated traffic gain from creating these 3 pages: 40-80 clicks/month
(based on expected CTR improvement from dedicated page relevance)

Performance Benchmarking Over Time

GSC’s date comparison feature lets you measure SEO progress with actual Google data. Combined with the local-reporting strategy skill, this creates client reports grounded in first-party metrics rather than third-party estimates.

The google-search-console-tool skill pulls comparison data across any two date ranges, broken down by query, page, device, or country. For local SEO reporting, the most useful comparison is month-over-month or quarter-over-quarter by page, showing which local landing pages are gaining or losing organic visibility.

When to Use GSC vs LocalSEOData

LocalSEOData provides local-specific metrics that GSC doesn’t cover: GBP profile data, geogrid rankings, citation health, AI visibility, local pack position. These are the core local SEO metrics.

Google Search Console provides organic performance data that LocalSEOData doesn’t cover: actual clicks from Google, actual impression counts, real CTR by query, and index coverage status. This is the website traffic layer.

They answer different questions. LocalSEOData answers “how visible is this business in local search?” GSC answers “how much organic traffic is the website getting and from which queries?” Both matter for a complete local SEO picture. Most audits and reports use both data sources.

Connecting Google Search Console to LocalSEOSkills

  1. Google Search Console access for the property (owner or full user)
  2. Google API credentials with Search Console API enabled
  3. In Claude Code: Settings then MCP Servers then Add Server
    • Name: Google Search Console
    • Authentication: OAuth2 or API key per Google’s setup
  4. Restart Claude Code
  5. Verify connection

Get Started

"Pull Search Console data for [domain] for the last 30 days.
Show me the top 20 queries by impressions with clicks, CTR,
and average position for each."

If you see actual query data with click counts and positions, the integration is working.

Learn More

To learn what this skill can do for your local SEO workflow, see the skill overview.