HOME SKILLS BLOG GITHUB
// SKILL

GOOGLE SEO APIS
REAL FIELD DATA

Google SEO API integration is a direct connection to Search Console, PageSpeed Insights, CrUX, the Indexing API, and GA4. It complements crawl analysis with search performance, index status, Chrome field metrics, and organic traffic from Google's own systems. Claude SEO guides the Google Cloud and OAuth setup.

By Daniel Agrici · Command surface verified:

$
/seo google pagespeed https://your-site.com

REQUIRES CLAUDE SEO INSTALLED IN CLAUDE CODE

Google API evidence routes through configured access tiers into separate reports
// RUN PREVIEW

What will happen if you start this skill?

Each route returns scoped Google evidence subject to credentials, permissions, quota, freshness, and sample availability.

OUTCOME

A selected Google API result for lab, field, search, analytics, video, entity, or eligible indexing work.

REQUIRED INPUT

Choose one route, for example /seo google pagespeed <url>, plus the credentials and property access it requires.

READINESS

Configured credentials do not prove API enablement, property permission, remaining quota, or sufficient CrUX samples.

LOCAL OUTPUT

Dated API evidence in the active session. The report route can write HTML, PDF, or Excel deliverables after analysis.

SIDE EFFECTS

Sends Google API requests and may write report files. An eligible Indexing API route sends an external notification.

COST + APPROVAL

Check live quota and supplementary billing. Confirm eligibility and owner approval before any Indexing API notification.

// HOW IT WORKS

Which Google SEO APIs does the skill use?

Claude SEO can query first-party Google sources directly: Search Console, PageSpeed Insights, CrUX, the Indexing API, and GA4. The core APIs are free within Google's normal quota limits, but they require your own project and credentials. Some supplementary services, including Cloud Natural Language, require billing to be enabled even when usage stays within a free tier.

The architecture is tiered. The bundled Tier 0 workflow expects an API key for PageSpeed and CrUX. OAuth or a service account adds Search Console, URL Inspection, and eligible Indexing API routes. A configured GA4 property ID adds traffic reports, and Ads credentials add Keyword Planner. Tier detection reports configured access; API enablement, property permissions, quota, and provider errors can still block a listed command.

Primary references: the official Search Console API documentation covers search analytics, sitemaps, sites, and URL Inspection, while the CrUX API documentation explains programmatic access to Chrome user-experience data.

/seo google [command] <url> TIER 0 API key PSI, CrUX, NLP TIER 1 OAuth / SA GSC, Indexing TIER 2 + GA4 ID GA4 organic TIER 3 + Ads token Keyword Planner PDF + EXCEL + JSON REPORTS cwv-audit, gsc-performance, indexation, full

The Six Capabilities

Each card maps to a real Google data source you can query the second your credentials are configured.

01
PAGESPEED + CRUX
Combined Lighthouse lab data and CrUX field data in one call. Mobile and desktop strategies. CrUX falls back to origin-level when URL-level data unavailable.
02
SEARCH CONSOLE
Clicks, impressions, CTR, position, top queries, top pages. URL Inspection for crawl/index status. Sitemap submission monitoring. All free.
03
CRUX HISTORY
The provider retains 40 weeks; the current script receives the default 25 periods. Compare field trends with deploy dates without claiming causation.
04
INDEXING API
Notify Google about eligible JobPosting pages or BroadcastEvent pages embedded in VideoObject. The API does not guarantee crawling or indexing and is not for ordinary URLs.
05
GA4 ORGANIC
Organic traffic, top landing pages, engagement, conversions. Requires Tier 2 (GA4 property ID configured). Pulls last 28 days by default.
06
PDF + EXCEL REPORTS
WeasyPrint-based A4 PDF report with matplotlib charts. Excel xlsx with Summary, Queries, Pages, Indexation sheets. Navy header styling, frozen rows, auto-filter.
// USAGE

How do you run the Google SEO APIs?

Credential Tier Detection

Always communicate the detected tier before running commands. Claude SEO checks ~/.config/claude-seo/google-api.json on every invocation and maps configured values to the four tiers. Detection does not test every API, property permission, or remaining quota, so a command can still fail after it appears available.

Commands by Tier

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>CrUX History analysis using the current 25-period provider default0
/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 entity <query>Knowledge Graph entity check0
/seo google safety <url>Web Risk URL safety check0
/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>Notify Google about one eligible JobPosting or BroadcastEvent page1
/seo google index-batch <file>Batch notifications for eligible pages, subject to quota1
/seo google ga4 [property-id]GA4 organic traffic report2
/seo google ga4-pages [property-id]Top organic landing pages2
/seo google keywords <seed>Keyword ideas from Google Ads Keyword Planner3
/seo google volume <keywords>Search volume lookup from Keyword Planner3

Indexing API restriction: Google officially supports this API only for pages with JobPosting structured data or a BroadcastEvent embedded in VideoObject. A successful notification does not guarantee crawling or indexing. Use URL Inspection for a few ordinary URLs and sitemaps for larger ordinary URL sets.

Generating Reports

After any analysis command, run /seo google report <type> to produce a styled deliverable. Report types are cwv-audit (Core Web Vitals from PSI + CrUX + history), gsc-performance (Search Console query tables and quick wins), indexation (batch inspection with coverage donut), and full (everything). PDF output uses WeasyPrint with matplotlib charts. Excel output ships with Summary, Queries, Pages, and Indexation sheets, frozen header rows, and auto-filter enabled, so pivots are one click away.

Rate Limits

Quotas apply to projects, properties, sites, or users rather than to a credential file itself. Recheck the live Google documentation and your Cloud console before a large run. Current published limits include:

  • PageSpeed Insights v5: 240 QPM, 25,000 QPD (API key)
  • CrUX + History: 150 QPM per project, with no API charge
  • GSC Search Analytics: 1,200 QPM per site and per user, 30M QPD per project
  • GSC URL Inspection: 600 QPM and 2,000 QPD per site
  • Indexing API: 380 requests per minute per project, 200 publish requests per day by default
  • GA4 Data API: 10 concurrent requests and 200,000 core tokens per standard property per day; 360 properties receive 2,000,000

Technical Notes

  • INP replaced FID on March 12, 2024. The skill never references FID.
  • CLS values from CrUX are string-encoded (e.g. "0.05"). Scripts handle parsing.
  • CrUX 404 means insufficient Chrome traffic, not an auth error. PSI lab data is the fallback.
  • CrUX field metrics use a rolling 28-day window, and history points are weekly and delayed. They are not real-time telemetry.
  • Search Analytics data has a 2-3 day lag. Reports note data freshness.
  • round_trip_time replaced effectiveConnectionType in CrUX in Feb 2025.
// FAQ

What should you know about Google SEO APIs?

The core Search Console, PageSpeed Insights, CrUX, eligible Indexing, and GA4 APIs have no usage charge within their normal quotas, but you need your own Google Cloud project, enabled APIs, credentials, and property access. Some supplementary APIs have billing or access requirements. Cloud Natural Language requires billing to be enabled, and Keyword Planner requires eligible Google Ads access.
// RELATED SKILLS

EXPLORE MORE

VIEW ALL 26 SKILLS →

PULL REAL GOOGLE DATA
FROM FIRST-PARTY SOURCES.

$
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git && bash claude-seo/install.sh
VIEW ON GITHUB ALL SKILLS >