Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AgricIDaniel/claude-seo/llms.txt

Use this file to discover all available pages before exploring further.

/seo google bridges the gap between Claude SEO’s crawl-based analysis and Google’s own real-time data sources: actual Chrome user metrics from CrUX, real indexation status from URL Inspection, search performance from Search Console, and organic traffic from GA4. All Google APIs used are free — you bring your own credentials. The plugin operates fully without any keys at all; each tier you add simply unlocks more data. Run /seo google setup to walk through configuration interactively.

​
4-tier credential system

No keys are required to start. Add credentials in any order — each tier delivers independent value.
TierCredentials requiredAPIs unlocked
0API key onlyPageSpeed Insights, CrUX field data, CrUX History (25-week trends)
1+ OAuth token or Service AccountSearch Console (queries, URL Inspection, sitemap status), Indexing API
2+ GA4 property configGA4 organic traffic, top landing pages, device / country breakdown
3+ Google Ads developer tokenKeyword Planner search volume and competition data
All credentials are stored in ~/.config/claude-seo/google-api.json with 0o600 file permissions (owner read/write only). Nothing is checked into the repository and nothing is transmitted beyond Google’s own API endpoints. The config file holds your service account path, API key, default Search Console property, and GA4 property ID.

​
Setup wizard

1

Run the setup command

/seo google setup
The wizard reads references/auth-setup.md and checks which credentials are already configured via python3 scripts/google_auth.py --check --json.
2

Add a Tier 0 API key

Create a Google Cloud project, enable the PageSpeed Insights API and CrUX API, and generate an API key. Paste it when prompted. This immediately unlocks PSI, CrUX field data, and 25-week CrUX History trends — no OAuth required.
3

Add a Tier 1 Service Account (optional)

Create a service account in Google Cloud Console, download the JSON key file, and add the service account’s client_email to Search Console under Settings → Users → Add. Point the config to the key file path. This unlocks GSC queries, URL Inspection, sitemap status, and the Indexing API.
4

Add a GA4 property ID (optional)

Find your property ID in GA4 Admin → Property Details (format: properties/123456789). Add it to the config. This unlocks organic traffic reports, top landing pages, and device/country breakdowns.
5

Add Google Ads developer token (optional)

A Google Ads account with an approved developer token unlocks Keyword Planner for real search volume and competition data. Add the ads_developer_token and ads_customer_id to the config file.
6

Verify the configuration

/seo google check
The skill reports the detected tier and lists which commands are available at your current credential level.

​
Available subcommands

​
Tier 0 — API key only

# Combined Lighthouse lab + CrUX field data (mobile + desktop)
/seo google pagespeed https://example.com

# CrUX field data only (faster, no Lighthouse run)
/seo google crux https://example.com

# 25-week CWV trend: improving / stable / degrading per metric
/seo google crux-history https://example.com
CrUX History returns 25 weeks of weekly p75 values for LCP, INP, and CLS with trend direction and percentage change. LCP can be decomposed into four subparts — TTFB, load delay, load duration, render delay — to localize bottlenecks. INP replaced FID on March 12, 2024; FID is never referenced anywhere in Claude SEO.

​
Tier 1 — + OAuth or Service Account

# Search Console: clicks, impressions, CTR, position (28-day default)
/seo google gsc https://example.com

# URL Inspection: real indexation status, canonical, crawl info
/seo google inspect https://example.com/page

# Batch URL Inspection from a file (one URL per line)
/seo google inspect-batch urls.txt

# GSC sitemap status: submitted counts, errors, warnings
/seo google sitemaps sc-domain:example.com

# Submit URL to Indexing API (officially for JobPosting + VideoObject pages)
/seo google index https://example.com/new-page

# Batch submit up to 200 URLs
/seo google index-batch urls.txt
GSC Search Analytics data has a 2–3 day lag. Quick-win detection is built in: queries at position 4–10 with high impressions are surfaced automatically as CTR optimization opportunities.

​
Tier 2 — + GA4 property config

# Organic traffic report: sessions, users, pageviews, bounce rate
/seo google ga4

# Top organic landing pages ranked by sessions
/seo google ga4-pages
Both commands filter to the Organic Search channel group automatically and default to a 28-day window.

​
Tier 3 — + Google Ads developer token

# Keyword ideas from Google Ads Keyword Planner
/seo google keywords "seo audit tool"

# Search volume for specific keywords (comma-separated)
/seo google volume "seo audit tool, seo plugin, claude code seo"

​
PDF and HTML reports

After any data collection run, Claude SEO can generate a professional PDF report using WeasyPrint (A4 layout) with matplotlib charts at 200 DPI. A full site audit report runs approximately 32 A4 pages and includes a cover page, table of contents, executive summary, data sections, recommendations, and methodology. 
# Core Web Vitals audit — gauges, timelines, distributions
/seo google report cwv-audit

# Search Console performance — query tables, quick wins
/seo google report gsc-performance

# Indexation status — coverage donut chart
/seo google report indexation

# Comprehensive report — all sections combined
/seo google report full
The typical workflow is to run data collection commands with --json output piped to files, then pass those files to the report generator: 
python3 scripts/pagespeed_check.py https://example.com --json > cwv.json
python3 scripts/gsc_query.py --property sc-domain:example.com --json > gsc.json
python3 scripts/google_report.py --type full --data cwv.json --domain example.com

​
Rate limits

APIPer-minutePer-dayAuth required
PageSpeed Insights v5240 QPM25,000 QPDAPI key
CrUX + CrUX History150 QPM (shared)UnlimitedAPI key
GSC Search Analytics1,200 QPM/site30 M QPDService Account
GSC URL Inspection600 QPM2,000 QPD/siteService Account
Indexing API380 RPM200 publish/dayService Account
GA4 Data API10 concurrent~25 K tokens/dayService Account
The Indexing API’s 200 publish/day limit is a hard Google quota. Use /seo google index-batch to prioritize your most important URLs and track which ones have been submitted. The skill reports quota usage after every batch run.

Build docs developers (and LLMs) love

Get started for freeTalk to us