seo-google skill

Google SEO APIs

Direct access to Google's own SEO data. Bridges the gap between crawl-based analysis (existing claude-seo skills) and Google's real-time field data: actual Chrome user metrics, real indexation status, search performance, and organic traffic.

All APIs are free. Setup requires a Google Cloud project with API key and/or service account -- run /seo google setup for step-by-step instructions.

Prerequisites

Before executing any command, check credentials:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run google_auth.py --check --json

Config file: ~/.config/claude-seo/google-api.json

{
  "service_account_path": "/path/to/service_account.json",
  "api_key": "<GOOGLE_API_KEY>",
  "default_property": "sc-domain:example.com",
  "ga4_property_id": "properties/123456789"
}

If missing, read references/auth-setup.md and walk the user through setup.

Credential Tiers

Always communicate the detected tier before running commands.

Quick Reference

PageSpeed + CrUX

/seo google pagespeed

Combined Lighthouse lab data + CrUX field data.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run pagespeedcheck.py --json Reference: references/pagespeed-crux-api.md Default:** Both mobile + desktop strategies, all Lighthouse categories.

Output merges lab scores (point-in-time Lighthouse) with field data (28-day Chrome user metrics). CrUX tries URL-level first, falls back to origin-level.

/seo google crux

CrUX field data only (no Lighthouse run). Faster.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run pagespeed_check.py --crux-only --json

/seo google crux-history

25-week CrUX History trends. Shows whether CWV metrics are improving, stable, or degrading.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run cruxhistory.py --json Reference:** references/pagespeed-crux-api.md

Output includes per-metric trend direction, percentage change, and weekly p75 values.

Search Console

/seo google gsc

Search Analytics: clicks, impressions, CTR, position for last 28 days.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run gscquery.py --property --json Reference: references/search-console-api.md Default:** 28 days, dimensions=query,page, type=web, limit=1000.

For EU sites, read references/dma-consent-mode-v2.md before interpreting CTR or GA4 drops: DMA and Consent Mode v2 change what Search Console and GA4 record.

Includes quick-win detection: queries at position 4-10 with high impressions. The totals block comes from a separate dimensionless aggregate query because query-level rows can omit anonymized low-volume traffic. Treat totals as site-wide only when totals_complete is true. --limit caps total returned dimension rows, not the size of every pagination request.

AI surfaces in GSC (2026):

- Generative AI performance report (launched 2026-06-03), a dedicated view of AI Overviews + AI Mode visibility. Impressions only (no clicks/CTR/position/query); dimensions Pages/Countries/Devices/Dates (Pacific Time); 1,000-row limit; newest data preliminary; a separate Discover gen-AI report also exists. Available to all websites worldwide since 2026-08-31 (launched to a subset 2026-06-03); dates support hourly, daily, weekly and monthly granularity.

- AI Mode already rolls into standard Performance totals (Web search type), clicks (external-link clicks in AI Mode) and impressions are counted in the normal report, so you cannot cleanly split "classic" vs "AI" traffic from totals. Use the Generative AI report for impressions-only AI visibility.

- Data-reliability caveat: a GSC logging error made impressions, CTR, and average position unreliable from 2025-05-13 to 2026-04-27 (clicks unaffected; fixed forward-only, no backfill). Treat impression/CTR/position trends spanning that window with caution; expect an apparent impressions drop after the fix.

Platform properties (2026): Search Console can expose verified TikTok,

Instagram, X, and YouTube accounts as individual properties. Verify each

account separately, unless it was already added through a claimed Search

profile. Use these properties for Google Search performance only, not as a

substitute for the platform's own analytics. Source:

developers.google.com/search/docs/monitor-debug/analyze-social-video-content

/seo google inspect

URL Inspection: real indexation status from Google.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run gsc_inspect.py --json

Returns: verdict (PASS/FAIL), coverage state, robots.txt status, indexing state, page fetch state, canonical selection, mobile usability, rich results.

/seo google inspect-batch

Batch inspection from a file (one URL per line). Rate limited to 2,000/day per site.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run gsc_inspect.py --batch --json

/seo google sitemaps

List submitted sitemaps with status, errors, warnings. Sitemap contents report submitted counts only; URL Inspection API is the indexation truth for whether specific URLs are indexed.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run gsc_query.py sitemaps --property --json

Indexing API

/seo google index

Notify Google of a URL update.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run indexingnotify.py --json Reference:** references/indexing-api.md

The Indexing API is officially for JobPosting and BroadcastEvent/VideoObject pages. Always inform the user of this restriction. Daily quota: 200 publish requests.

/seo google index-batch

Batch submit URLs from a file. Tracks quota usage.

Script: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run indexing_notify.py --batch --json

GA4 Traffic

/seo google ga4 [property-id]