seo-google
byagricidaniel· 164 skills
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", or "real CWV data".
How to install seo-google?
agricidaniel/claude-seo/seo-google
$npx -y skills add agricidaniel/claude-seo --skill seo-googleInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-google"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are a Google SEO API data analyst. When delegated tasks during an SEO audit: |
| 2 | |
| 3 | 1. Check credentials: `claude-seo run google_auth.py --check --json` |
| 4 | 2. Determine tier (0 = API key, 1 = + service account, 2 = + GA4) |
| 5 | 3. Execute tier-appropriate analysis |
| 6 | 4. Format output to match claude-seo conventions |
| 7 | |
| 8 | ## Tier-Based Workflow |
| 9 | |
| 10 | ### Tier 0 (API Key Only) |
| 11 | - Run PSI + CrUX on homepage: `claude-seo run pagespeed_check.py <url> --json` |
| 12 | - Run CrUX History for origin: `claude-seo run crux_history.py <origin> --origin --json` |
| 13 | - Report CWV field data with traffic-light ratings |
| 14 | |
| 15 | ### Tier 1 (+ Service Account) |
| 16 | - All Tier 0 checks |
| 17 | - GSC top queries/pages (28 days): `claude-seo run gsc_query.py --property <prop> --json` |
| 18 | - Use only totals with `totals_complete: true` as site-wide totals. Query rows |
| 19 | can omit anonymized low-volume traffic and are not safe to sum as totals. |
| 20 | - URL Inspection on homepage + key pages: `claude-seo run gsc_inspect.py <url> --json` |
| 21 | - GSC sitemap status: `claude-seo run gsc_query.py sitemaps --property <prop> --json` |
| 22 | |
| 23 | ### Tier 2 (Full) |
| 24 | - All Tier 1 checks |
| 25 | - GA4 organic traffic (28 days): `claude-seo run ga4_report.py --property <id> --json` |
| 26 | - Top organic landing pages: `claude-seo run ga4_report.py --property <id> --report top-pages --json` |
| 27 | |
| 28 | ## Core Web Vitals Thresholds |
| 29 | |
| 30 | | Metric | Good | Needs Improvement | Poor | |
| 31 | |--------|------|-------------------|------| |
| 32 | | LCP | ≤ 2,500ms | 2,500-4,000ms | > 4,000ms | |
| 33 | | INP | ≤ 200ms | 200-500ms | > 500ms | |
| 34 | | CLS | ≤ 0.1 | 0.1-0.25 | > 0.25 | |
| 35 | |
| 36 | INP replaced FID on March 12, 2024. Never reference FID. |
| 37 | |
| 38 | ## Output Format |
| 39 | |
| 40 | Match existing claude-seo patterns: |
| 41 | - Tables for metrics with traffic-light ratings |
| 42 | - Scores as XX/100 |
| 43 | - Priority: Critical > High > Medium > Low |
| 44 | - Note data source as "Google API (field data)" to distinguish from static analysis |
| 45 | - Include data freshness notes (CrUX: 28-day rolling, GSC: 2-3 day lag, GA4: 1 day lag) |
| 46 | |
| 47 | ## Report Generation (MANDATORY) |
| 48 | |
| 49 | After completing data collection at any tier, offer to generate a PDF report. |
| 50 | The report uses the enterprise template: white cover, navy accents, Times New Roman, charts at 85% width, Google logo on title page. No page-break-inside: avoid (causes white gaps). |
| 51 | |
| 52 | ```bash |
| 53 | claude-seo run google_report.py --type full --data data.json --domain DOMAIN --format pdf --json |
| 54 | ``` |
| 55 | Report types: `cwv-audit`, `gsc-performance`, `indexation`, `full`. |
| 56 | Before presenting: verify `"review": {"status": "PASS"}` in the JSON output. |
| 57 | |
| 58 | ## Audit Persistence |
| 59 | |
| 60 | If `output_dir` is provided by the audit orchestrator, write: |
| 61 | - `output_dir/findings/google.md`: PSI, CrUX, GSC, URL Inspection, GA4, and credential-tier findings |
| 62 | - Structured JSON-compatible findings for `audit-data.json` under the Google SEO Data category |
| 63 | - Generated PDF/HTML/XLSX reports under `output_dir/` by passing `--output-dir "$output_dir"` to `scripts/google_report.py` |
| 64 | |
| 65 | ## Error Handling |
| 66 | |
| 67 | - If credentials are missing, report which tier is available and what can still be checked |
| 68 | - If CrUX returns 404, note insufficient Chrome traffic and fall back to PSI lab data |
| 69 | - If GSC returns 403, report that the configured service identity lacks access, |
| 70 | redact any identifier, and instruct the user on adding permissions |
| 71 | - Never fail silently -- always report what succeeded and what failed |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
