blog-google

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

1,560stars274forksUpdated 8/4/2026

Data Science & ML #blogging #search-console #google-api #analytics #seo #python

Security Assessment

Safe(92/100)

Security Score92/100

About blog-google

Blog Google is a Claude Code skill that connects a blogging or SEO workflow directly to Google's suite of free SEO and analytics APIs. It solves the problem of scattered, manual performance research by giving Claude one command surface to pull real Chrome user metrics, indexation status, search performance, entity analysis, and keyword data instead of guessing at how a blog is performing in Search.

The skill exposes a progressive, tier-based command set gated by whichever Google credentials the user has configured. With just an API key (Tier 0) it runs PageSpeed Insights (Lighthouse lab data plus CrUX field data), 25-week CrUX Core Web Vitals history, YouTube video search for embedding, and NLP entity extraction with sentiment for E-E-A-T analysis. Adding OAuth or a service account (Tier 1) unlocks Search Console analytics, URL Inspection, and Indexing API submission; a GA4 property (Tier 2) adds organic traffic reporting; and a Google Ads developer token (Tier 3) adds Keyword Planner volume data. It ships Python scripts run through a run.py wrapper, report templates, and reference docs on auth setup, rate limits, and Google Search currentness. Credentials live in a shared config file at ~/.config/claude-seo/google-api.json.

It targets bloggers, SEO practitioners, and content teams who want grounded, data-driven performance audits and indexation reports rather than opinion-based SEO advice. Typical uses include auditing Core Web Vitals trends, checking whether posts are indexed, reviewing Search Console click and impression data, and generating HTML/PDF performance reports.

FAQ

What Google credentials do I need to use it?

It works in tiers. An API key alone enables PageSpeed, CrUX, CrUX history, YouTube search, and NLP. OAuth or a service account adds Search Console, URL Inspection, and the Indexing API. A configured GA4 property adds organic traffic reports, and a Google Ads developer token plus customer ID adds Keyword Planner data. The skill detects and reports your tier before running commands.

Where are credentials stored?

In a JSON config file at ~/.config/claude-seo/google-api.json, which is shared with the companion claude-seo skill. If it's missing, the skill points you to references/auth-setup.md to walk through setup with a Google Cloud project.

Does it cost money to run?

The documentation states all the APIs are free at normal usage levels. Setup only requires a Google Cloud project with an API key and/or service account. The skill also ships a rate-limits/quotas reference and a quotas command.

Can it report on AI Overviews or AI Mode search performance?

No. The reference guidance explicitly notes there is no supported Search Console API endpoint for the dedicated generative-AI reports, so the skill reports those as unavailable and directs you to the Search Console UI rather than synthesizing data.

What are the prerequisites to run the scripts?

Python 3 and the Google Cloud credentials above. The skill advises always checking credentials first via the run.py wrapper's google_auth --check command before running any data command.

All Files

24 files

scripts/crux_history.py10.8 KB