PluginBench
Skill
Review
Audit score 70

seo-google

agricidaniel/claude-seo

Access Google's real SEO data: Search Console, PageSpeed, CrUX field metrics, GA4 organic traffic, and Indexing API.

What is seo-google?

Direct integration with Google's SEO APIs to retrieve actual field data from Chrome users, search performance metrics, indexation status, and organic traffic trends. Use this when you need real Google data rather than crawl-based estimates—Search Console analytics, Core Web Vitals from real users, indexation verification, or organic traffic attribution.

  • Query Search Console for clicks, impressions, CTR, and position data (28-day history)
  • Retrieve CrUX field data and 25-week Core Web Vitals trends (LCP, INP, CLS, FCP, TTFB)
  • Run PageSpeed Insights with combined Lighthouse lab scores and real user metrics
  • Inspect URL indexation status, canonical selection, and crawl state via URL Inspection API
  • Submit URLs to Google's Indexing API for JobPosting and BroadcastEvent content
  • Pull organic traffic reports from GA4 filtered by Search channel

How to install seo-google

npx skills add https://github.com/agricidaniel/claude-seo --skill seo-google
Prerequisites
  • Google Cloud project with API key and/or service account JSON
  • Search Console property ownership (for GSC, URL Inspection, Indexing API)
  • GA4 property ID (for organic traffic reports)
  • Config file at ~/.config/claude-seo/google-api.json with credentials
  • Run `/seo google setup` for step-by-step credential configuration
Claude Code
Cursor
Windsurf
Cline

How to use seo-google

  1. 1.Run `python3 scripts/google_auth.py --check --json` to verify credentials and detect tier
  2. 2.Execute `/seo google setup` to configure API key, service account, and GA4 property ID
  3. 3.Use `/seo google pagespeed <url>` or `/seo google crux <url>` for Core Web Vitals (Tier 0)
  4. 4.Query `/seo google gsc <property>` for Search Console analytics (Tier 1)
  5. 5.Run `/seo google inspect <url>` to check indexation status (Tier 1)
  6. 6.Submit URLs with `/seo google index <url>` or batch via `/seo google index-batch <file>` (Tier 1)
  7. 7.Pull organic traffic with `/seo google ga4 [property-id]` (Tier 2)
  8. 8.Check `/seo google quotas` to monitor rate limits across all APIs

Use cases

Good for
  • Monitor search performance: identify high-impression queries ranking at positions 4–10 for quick wins
  • Track Core Web Vitals trends over 25 weeks to validate performance improvements
  • Verify URL indexation status and debug crawl/indexing issues before they impact rankings
  • Submit newly published or updated pages to Google's Indexing API for faster discovery
  • Correlate organic traffic drops or gains with GA4 session and engagement metrics
Who it's for
  • SEO specialists and content strategists needing real Google field data
  • Technical SEO professionals debugging indexation and crawl issues
  • Content teams validating E-E-A-T signals and entity relevance
  • Product managers tracking organic traffic and Core Web Vitals impact
  • Agencies managing multiple properties via Search Console

seo-google FAQ

What credentials do I need?

Minimum: Google API key (Tier 0 for PageSpeed/CrUX). For Search Console and Indexing API, add a service account (Tier 1). For GA4 organic traffic, also configure ga4_property_id (Tier 2). Run `/seo google setup` for guided configuration.

Can I use this without Search Console ownership?

Yes. PageSpeed, CrUX, YouTube, NLP, and entity analysis work with API key only. Search Console, URL Inspection, and Indexing API require Tier 1 credentials and property ownership.

What is the rate limit?

Varies by API: PageSpeed (25 req/day free), CrUX (unlimited), Search Console (10M queries/day), URL Inspection (2,000/day per site), Indexing API (200 publish requests/day). Run `/seo google quotas` to check current usage.

How far back does Search Console data go?

Search Analytics defaults to 28 days. CrUX History provides 25-week trends. GA4 organic traffic reports use your GA4 retention settings (default 14 months).

Can I batch-process URLs?

Yes. Use `/seo google inspect-batch <file>` for URL Inspection (up to 2,000/day) and `/seo google index-batch <file>` for Indexing API (up to 200 URLs per batch).

Full instructions (SKILL.md)

Source of truth, from agricidaniel/claude-seo.


name: seo-google description: > Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores". user-invocable: true argument-hint: "[command] [url|property]" license: MIT metadata: author: AgriciDaniel version: "2.2.0" category: seo

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:

python3 scripts/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

TierDetectionAvailable Commands
0 (API Key)api_key presentpagespeed, crux, crux-history, youtube, nlp
1 (OAuth/SA)+ OAuth token or service accountTier 0 + gsc, inspect, sitemaps, index
2 (Full)+ ga4_property_id configuredTier 1 + ga4, ga4-pages
3 (Ads)+ ads_developer_token + ads_customer_idTier 2 + keywords, volume

Always communicate the detected tier before running commands.

Quick Reference

CommandWhat it doesTier
/seo google setupCheck/configure API credentials--
/seo google pagespeed <url>PSI Lighthouse + CrUX field data0
/seo google crux <url>CrUX field data only (p75 metrics)0
/seo google crux-history <url>25-week CWV trend analysis0
/seo google gsc <property>Search Console: clicks, impressions, CTR, position1
/seo google inspect <url>URL Inspection: index status, canonical, crawl info1
/seo google inspect-batch <file>Batch URL Inspection from file1
/seo google sitemaps <property>GSC sitemap status1
/seo google index <url>Submit URL to Indexing API1
/seo google index-batch <file>Batch submit up to 200 URLs1
/seo google ga4 [property-id]GA4 organic traffic report2
/seo google ga4-pages [property-id]Top organic landing pages2
/seo google youtube <query>YouTube video search (views, likes, duration)0
/seo google youtube-video <id>YouTube video details + top comments0
/seo google nlp <url-or-text>NLP entity extraction + sentiment + classification0
/seo google entities <url-or-text>Entity analysis only (for E-E-A-T)0
/seo google keywords <seed>Keyword ideas from Google Ads Keyword Planner3
/seo google volume <keywords>Search volume lookup from Keyword Planner3
/seo google entity <query>Knowledge Graph entity check0
/seo google safety <url>Web Risk URL safety check0
/seo google quotasShow rate limits for all APIs--

PageSpeed + CrUX

/seo google pagespeed <url>

Combined Lighthouse lab data + CrUX field data.

Script: python3 scripts/pagespeed_check.py <url> --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 <url>

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

Script: python3 scripts/pagespeed_check.py <url> --crux-only --json

/seo google crux-history <url>

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

Script: python3 scripts/crux_history.py <url> --json Reference: references/pagespeed-crux-api.md

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


Search Console

/seo google gsc <property>

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

Script: python3 scripts/gsc_query.py --property <property> --json Reference: references/search-console-api.md Default: 28 days, dimensions=query,page, type=web, limit=1000.

Includes quick-win detection: queries at position 4-10 with high impressions.

/seo google inspect <url>

URL Inspection: real indexation status from Google.

Script: python3 scripts/gsc_inspect.py <url> --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 <file>

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

Script: python3 scripts/gsc_inspect.py --batch <file> --json

/seo google sitemaps <property>

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: python3 scripts/gsc_query.py sitemaps --property <property> --json


Indexing API

/seo google index <url>

Notify Google of a URL update.

Script: python3 scripts/indexing_notify.py <url> --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 <file>

Batch submit URLs from a file. Tracks quota usage.

Script: python3 scripts/indexing_notify.py --batch <file> --json


GA4 Traffic

/seo google ga4 [property-id]

Organic traffic report: daily sessions, users, pageviews, bounce rate, engagement.

Script: python3 scripts/ga4_report.py --property <id> --json Reference: references/ga4-data-api.md Default: 28 days, filtered to Organic Search channel group.

/seo google ga4-pages [property-id]

Top organic landing pages ranked by sessions.

Script: python3 scripts/ga4_report.py --property <id> --report top-pages --json


YouTube (Video SEO)

YouTube mentions have the strongest AI visibility correlation (0.737). Free, API key only.

/seo google youtube <query>

Search YouTube for videos. Returns title, channel, views, likes, duration.

Script: python3 scripts/youtube_search.py search "<query>" --json Reference: references/youtube-api.md Quota: 100 units per search (10,000 units/day free).

/seo google youtube-video <video_id>

Detailed video info + tags + top 10 comments.

Script: python3 scripts/youtube_search.py video <video_id> --json Quota: 2 units (video details + comments).


NLP Content Analysis

Google's own entity/sentiment analysis. Enhances E-E-A-T scoring.

/seo google nlp <url-or-text>

Full NLP analysis: entities, sentiment, content classification.

Script: python3 scripts/nlp_analyze.py --url <url> --json or --text "..." Reference: references/nlp-api.md Free tier: 5,000 units/month. Requires billing enabled on GCP project.

/seo google entities <url-or-text>

Entity extraction only (faster, less quota).

Script: python3 scripts/nlp_analyze.py --url <url> --features entities --json


Keyword Research (Google Ads)

Gold-standard keyword volume data. Requires Google Ads account.

/seo google keywords <seed>

Generate keyword ideas from seed terms.

Script: python3 scripts/keyword_planner.py ideas "<seed>" --json Reference: references/keyword-planner-api.md Requires: Ads developer token + customer ID in config (Tier 3).

/seo google volume <keywords>

Search volume for specific keywords (comma-separated).

Script: python3 scripts/keyword_planner.py volume "<kw1>,<kw2>" --json


Supplementary

/seo google entity <query>

Knowledge Graph entity check. Verifies brand presence.

Reference: references/supplementary-apis.md Uses Knowledge Graph Search API with API key.

/seo google safety <url>

Web Risk API check for malware/social engineering flags.

Reference: references/supplementary-apis.md

/seo google quotas

Display rate limits table. Read references/rate-limits-quotas.md.


Reports

After any analysis command, offer to generate a PDF/HTML report.

/seo google report <type>

Generate a professional PDF report with charts and analytics.

Script: python3 scripts/google_report.py --type <type> --data <json> --domain <domain> --format pdf

TypeInputOutput
cwv-auditPSI + CrUX + CrUX History dataCore Web Vitals audit with gauges, timelines, distributions
gsc-performanceGSC query dataSearch Console report with query tables, quick wins
indexationBatch inspection dataIndexation status with coverage donut chart
fullAll data combinedComprehensive Google SEO report (all sections)

Workflow:

  1. Run data collection commands (pagespeed, gsc, inspect-batch, etc.)
  2. Save JSON output to file: python3 scripts/pagespeed_check.py <url> --json > data.json
  3. Generate report: python3 scripts/google_report.py --type cwv-audit --data data.json --domain <domain>

Convention: After completing analysis, suggest: "Generate a report? Use /seo google report <type>"


Rate Limits

APIPer-MinutePer-DayAuth
PSI v5240 QPM25,000 QPDAPI Key
CrUX + History150 QPM (shared)UnlimitedAPI Key
GSC Search Analytics1,200 QPM/site30M QPDService Account
GSC URL Inspection600 QPM2,000 QPD/siteService Account
Indexing API380 RPM200 publish/dayService Account
GA4 Data API10 concurrent~25K tokens/dayService Account

Cross-Skill Integration

  • seo-audit: Spawns seo-google agent for live CWV + indexation data (conditional)
  • seo-technical: Uses pagespeed_check.py for real CWV field data
  • seo-performance: CrUX field data supplements Lighthouse lab data
  • seo-sitemap: GSC sitemap status shows submitted counts, errors, and warnings; use URL Inspection for indexation truth
  • seo-content: GSC query data informs keyword targeting
  • seo-geo: GSC search appearance data includes AI Overview references

Output Format

  • CWV metrics: traffic-light rating (Good / Needs Improvement / Poor)
  • Performance reports: tables with sortable columns
  • Always include data freshness note
  • Save reports as GOOGLE-API-REPORT-{domain}.md
  • Use templates from assets/templates/ for structured output

Technical Notes

  • INP replaced FID on March 12, 2024. Never reference FID.
  • CLS values from CrUX are string-encoded (e.g., "0.05"). Scripts handle parsing.
  • CrUX 404 = insufficient traffic, not an auth error.
  • Search Analytics data has 2-3 day lag.
  • round_trip_time replaced effectiveConnectionType in CrUX (Feb 2025).
  • Custom Search JSON API is closed to new customers (2025).

Error Handling

ScenarioAction
No credentials configuredRun /seo google setup. List Tier 0 commands that work with just an API key.
Service account lacks GSC accessReport error. Instruct: add client_email to GSC > Settings > Users > Add.
CrUX data unavailable (404)Report insufficient Chrome traffic. Suggest PSI lab data as fallback.
GA4 property not foundReport error. Show how to find property ID in GA4 Admin > Property Details.
Indexing API quota exceededReport 200/day limit. Suggest prioritizing most important URLs.
Rate limit (429)Wait and retry with exponential backoff. Report which API hit the limit.