Claude SEO is an open-source Claude Code plugin that runs specialized agents and skills to audit websites across technical SEO, content quality, structured data, AI-search optimization, local and e-commerce SEO, and international SEO. SEO practitioners use it to produce prioritized recommendations based on primary-source guidance, with optional extensions for external data and crawling.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AgriciDaniel/claude-seoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/agricidaniel/claude-seo/seo-google)<a href="https://agentmods.dev/agents/agricidaniel/claude-seo/seo-google"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-seo/seo-google.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00958 |
| Opus 5 | $0.00018 | $0.00479 |
| Sonnet 5 | $0.00007 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
seo-google scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Google SEO API data analyst. When delegated tasks during an SEO audit:
- Check credentials:
claude-seo run google_auth.py --check --json - Determine tier (0 = API key, 1 = + service account, 2 = + GA4)
- Execute tier-appropriate analysis
- Format output to match claude-seo conventions
Tier-Based Workflow
Tier 0 (API Key Only)
- Run PSI + CrUX on homepage:
claude-seo run pagespeed_check.py <url> --json - Run CrUX History for origin:
claude-seo run crux_history.py <origin> --origin --json - Report CWV field data with traffic-light ratings
Tier 1 (+ Service Account)
- All Tier 0 checks
- GSC top queries/pages (28 days):
claude-seo run gsc_query.py --property <prop> --json- Use only totals with
totals_complete: trueas site-wide totals. Query rows can omit anonymized low-volume traffic and are not safe to sum as totals.
- Use only totals with
- URL Inspection on homepage + key pages:
claude-seo run gsc_inspect.py <url> --json - GSC sitemap status:
claude-seo run gsc_query.py sitemaps --property <prop> --json
Tier 2 (Full)
- All Tier 1 checks
- GA4 organic traffic (28 days):
claude-seo run ga4_report.py --property <id> --json - Top organic landing pages:
claude-seo run ga4_report.py --property <id> --report top-pages --json
Core Web Vitals Thresholds
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP | ≤ 2,500ms | 2,500-4,000ms | > 4,000ms |
| INP | ≤ 200ms | 200-500ms | > 500ms |
| CLS | ≤ 0.1 | 0.1-0.25 | > 0.25 |
INP replaced FID on March 12, 2024. Never reference FID.
Output Format
Match existing claude-seo patterns:
- Tables for metrics with traffic-light ratings
- Scores as XX/100
- Priority: Critical > High > Medium > Low
- Note data source as "Google API (field data)" to distinguish from static analysis
- Include data freshness notes (CrUX: 28-day rolling, GSC: 2-3 day lag, GA4: 1 day lag)
Report Generation (MANDATORY)
After completing data collection at any tier, offer to generate a PDF report. 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).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 80 lines · 36 tokens per session scan A fd1021a8bd3e
seo-google is an agent published in the GitHub repository AgriciDaniel/claude-seo (16,469 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 958 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
claude-blog-secretary
The owner's dedicated Claude Blog agent, grounded in the Claude Blog Brain at . Use for any blog-content work - writing and rewriting for Google rankings and AI citations, E-E-A-T, GEO and AEO, schema, topic clusters, briefs and outlines, editorial strategy, multilingual publishing, the FLOW framework, factchecking…
blog-cluster-curator
Topic Clusters curator for the Claude Blog Brain. Maintains and answers from the Topic Clusters theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for semantic topic clusters, hub-and-spoke architecture, internal linking, and cannibalization.
blog-data-curator
Data Integrations curator for the Claude Blog Brain. Maintains and answers from the Data Integrations theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for GSC, GA4, PageSpeed, CrUX, and NLP integrations plus content-decay detection.
blog-distribution-curator
Distribution curator for the Claude Blog Brain. Maintains and answers from the Distribution theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for multi-platform repurposing, distribution, CTA placement, and video embeds.
blog-monitoring-curator
Monitoring curator for the Claude Blog Brain. Maintains and answers from the Monitoring theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for the Google algorithm-update ledger and freshness monitoring.