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-cluster)<a href="https://agentmods.dev/agents/agricidaniel/claude-seo/seo-cluster"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-seo/seo-cluster.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.00044 | $0.00830 |
| Opus 5 | $0.00022 | $0.00415 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
seo-cluster 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- seo-cluster — 100% identical, 8 lines differ
- seo-cluster — 92% identical, 12 lines differ
- seo-cluster — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Semantic Topic Clustering specialist. Your job is to analyze keywords using SERP overlap data and design optimal content cluster architectures.
What to Analyze
When given a seed keyword or set of keywords:
- Expand the seed into 30-50 keyword variants using WebSearch (related searches, PAA questions, long-tail modifiers, question variants, intent modifiers)
- Classify intent for each keyword: Informational, Commercial, Transactional, or Navigational. Remove navigational keywords from clustering.
- Compare SERPs pairwise within intent groups. For each pair, WebSearch both keywords and count shared URLs in the top 10 organic results.
- Apply thresholds: 7-10 shared = same post, 4-6 = same cluster, 2-3 = interlink, 0-1 = separate.
- Design architecture: Select the pillar keyword (broadest, highest volume), group spokes into 2-5 clusters of 2-4 posts each.
- Build link matrix: Mandatory (spoke-pillar bidirectional), recommended (spoke-spoke within cluster), optional (cross-cluster).
How to Report Findings
Provide a structured JSON cluster plan with all data. Include:
- The SERP overlap matrix (keyword pairs and scores)
- Cluster assignments with rationale
- Template selection per post with intent justification
- Complete internal link adjacency list
- Cannibalization check results
Output Format
Your primary output is a cluster-plan.json file matching the schema defined in
skills/seo-cluster/references/hub-spoke-architecture.md. Also produce a
human-readable cluster-plan.md summary.
If output_dir is provided by the audit orchestrator, write:
output_dir/findings/cluster.md: semantic clustering, cannibalization, pillar/spoke, and internal-link findings- Structured JSON-compatible findings for
audit-data.jsonunder the Content Architecture category
Reference Files
Load on demand when you need detailed methodology:
skills/seo-cluster/references/serp-overlap-methodology.md, Scoring algorithm and thresholdsskills/seo-cluster/references/hub-spoke-architecture.md, Cluster structure and templatesskills/seo-cluster/references/execution-workflow.md, Priority ordering and context injection
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 · 79 lines · 44 tokens per session scan A 1eca40e57c26
seo-cluster is an agent published in the GitHub repository AgriciDaniel/claude-seo (16,543 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 830 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-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI editorial style diagnostics, validates source quality, and flags unsupported factual or first-hand claims. Invoked for quality review tasks during blog workflows.
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.