version: "1.0.1" name: blog-google description: > Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup". user-invokable: true argument-hint: "[setup|pagespeed|crux|crux-history|gsc|inspect|index|ga4|nlp|youtube|keywords|report|quotas] [url|property|query]" license: MIT metadata: author: AgriciDaniel version: "2.1.1" category: blog

Blog Google: Google API Data for Blog Performance

Direct access to Google's SEO APIs for blog performance analysis. Provides real Chrome user metrics, indexation status, search performance, entity analysis, YouTube video discovery, keyword volumes, and PDF/HTML performance reports.

All APIs are free at normal usage levels. Setup requires a Google Cloud project with an API key and/or service account.

Prerequisites

Always check credentials before running any command:

python3 skills/blog-google/scripts/run.py google_auth --check --json

Config file: ~/.config/claude-seo/google-api.json (shared with claude-seo)

{
  "api_key": "AIzaSy...",
  "oauth_client_path": "/path/to/client_secret.json",
  "default_property": "sc-domain:example.com",
  "ga4_property_id": "properties/123456789",
  "ads_developer_token": "...",
  "ads_customer_id": "123-456-7890",
  "ads_login_customer_id": "123-456-7890"
}

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

/blog google pagespeed <url>

Combined Lighthouse lab data + CrUX field data for a published blog post.

Script: python3 skills/blog-google/scripts/run.py pagespeed_check <url> --json Reference: references/api-reference.md

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.

/blog google crux <url>

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

Script: python3 skills/blog-google/scripts/run.py pagespeed_check <url> --crux-only --json

/blog google crux-history <url>

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

Script: python3 skills/blog-google/scripts/run.py crux_history <url> --json

Search Console

/blog google gsc <property>

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

Script: python3 skills/blog-google/scripts/run.py gsc_query --property <property> --json Default: 28 days, dimensions=query,page, type=web, limit=1000.

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

The dedicated Search Console generative-AI reports are a gradual, subset rollout in the Search Console UI. They have separate Search and Discover views; the Search view covers AI Overviews and AI Mode. Do not promise clicks, queries, or API retrieval from these dedicated views. Until Google documents an API, report that capability as SKIPPED or unavailable and point the user to the UI.

Search Console platform properties for Instagram, TikTok, X, and YouTube are also rolling out gradually. Their UI can expose Search and Discover performance, but /blog google gsc must not claim to retrieve these platform reports through the current API.

/blog google inspect <url>

URL Inspection: real indexation status from Google.

Script: python3 skills/blog-google/scripts/run.py gsc_inspect <url> --json

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

After a canonicalization fix, Google may retain the URL in a duplicate cluster for up to two weeks. If the implementation is now correct and the fix is within that window, report PENDING_REEVALUATION rather than an immediate failure. Search Console's Request Indexing feature is quota-limited; reserve it for important URLs.

For batch inspection: python3 skills/blog-google/scripts/run.py gsc_inspect --batch <file> --json

Indexing API

/blog google index <url>

Notify Google of a URL update through the Indexing API.

Script: python3 skills/blog-google/scripts/run.py indexing_notify <url> --json Reference: references/api-reference.md

The Indexing API is officially for JobPosting and BroadcastEvent/VideoObject pages. Always inform the user of this restriction. Daily quota: 200 publish requests. Do not present it as a general-purpose replacement for URL Inspection's Request Indexing feature.

For batch: python3 skills/blog-google/scripts/run.py indexing_notify --batch <file> --json

GA4 Traffic

/blog google ga4 [property-id]

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

Script: python3 skills/blog-google/scripts/run.py ga4_report --property <id> --json Default: 28 days, filtered to Organic Search channel group.

For top landing pages: python3 skills/blog-google/scripts/run.py ga4_report --property <id> --report top-pages --json

YouTube (Video Discovery)

YouTube research can add useful, relevant media and distribution context. Any third-party visibility correlation is observational, not a Google ranking or citation requirement. Free, API key only. Used by blog-write and blog-rewrite for video embedding.

/blog google youtube <query>

Search YouTube for videos relevant to a blog topic.

Script: python3 skills/blog-google/scripts/run.py youtube_search search "<query>" --json Quota: 100 units per search (10,000 units/day free).

Returns: title, channel, views, likes, duration, description, tags.

For video details + comments: python3 skills/blog-google/scripts/run.py youtube_search video <video_id> --json

NLP Content Analysis

Google's entity and sentiment analysis can support topic and editorial review. It does not expose ranking-system scores, and E-E-A-T is not a numeric Google ranking factor.

/blog google nlp <url-or-text>

Full NLP analysis: entities, sentiment, content classification.

Script: python3 skills/blog-google/scripts/run.py nlp_analyze --url <url> --json Free tier: 5,000 units/month. Requires billing enabled on GCP project.

For entity extraction only: python3 skills/blog-google/scripts/run.py nlp_analyze --url <url> --features entities --json

Keyword Research (Google Ads)

Gold-standard keyword volume data. Requires Google Ads account (Tier 3).

/blog google keywords <seed>

Generate keyword ideas from seed terms for blog topic research.

Script: python3 skills/blog-google/scripts/run.py keyword_planner ideas "<seed>" --json

For volume lookup: python3 skills/blog-google/scripts/run.py keyword_planner volume "<kw1>,<kw2>" --json

Reports

/blog google report <type>

Generate a PDF/HTML report with charts and tables.

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

Note: PDF generation requires system libraries: sudo apt install libpango1.0-dev libcairo2-dev. Falls back to HTML if WeasyPrint is unavailable or PDF rendering fails.

Rate Limits

Read references/rate-limits-quotas.md for detailed quota management.

Blog Workflow Integration

This skill is both user-invocable (/blog google pagespeed) and callable internally by other blog sub-skills:

• blog-seo-check: Runs PSI + CrUX on published post URL for live CWV data
• blog-rewrite: NLP entity analysis to identify E-E-A-T entity gaps
• blog-geo: GSC performance data for real search appearance insights
• blog-audit: Batch CWV + indexation checks across all published blog URLs
• blog-write / blog-rewrite: YouTube search for video embedding

Falls back gracefully when credentials are not configured.

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 Chrome traffic, not an auth error.
• Search Analytics data has 2-3 day lag.
• Indexing API is officially for JobPosting/BroadcastEvent pages only.
• All Google APIs used are FREE at normal usage levels.
• Read references/search-currentness.md before diagnosing a named update,

canonical change, Discover visibility, Google generative-AI reporting, platform properties, Preferred Sources, AMP, or crawler byte-limit issue.

• A named update's dates do not prove what caused an individual site's change.

Wait one full week after rollout before comparing data, and separate Web, Image, Video, and News performance.

• Googlebot processes only the first 2MB of supported files and first 64MB of

PDFs. Keep critical metadata and primary content before the cutoff.

Error Handling