seo-content

seo-content is an agent for Claude Code from zubair-trabzada/dataforseo-claude. It costs 52 tokens per session (611 once invoked), scanned A, original, MIT.

An SEO content-analysis agent that groups a website's search keywords into topics and evaluates which topics are well covered or missing. SEO means improving a site's visibility in search engines.

In plain words
What is it for?
Use it to analyze ranked keywords and competitors, score topical coverage, and identify five high-priority articles to write.
Why use it?
It shows where a site has weak content or where competitors appear in search results but the site does not.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; positional $N argument.

Good fit Use it to analyze ranked keywords and competitors, score topical coverage, and identify five high-priority articles to write.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zubair-trabzada/dataforseo-claude/seo-content
Install

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.

Clone the repo
git clone --depth 1 https://github.com/zubair-trabzada/dataforseo-claude

Made for: Claude Code.

Wrote 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.

agentmods badge for seo-content

README.md
[![agentmods](https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-content/github.svg)](https://agentmods.dev/agents/zubair-trabzada/dataforseo-claude/seo-content)
Your own site
<a href="https://agentmods.dev/agents/zubair-trabzada/dataforseo-claude/seo-content"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-content/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for seo-content

Your own site · 80×15
<a href="https://agentmods.dev/agents/zubair-trabzada/dataforseo-claude/seo-content"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00611
Opus 5 $0.00026 $0.00305
Sonnet 5 $0.00010 $0.00122
Haiku 4.5 $0.00005 $0.00061

Measured 12d ago against content hash 1e1f63a7838c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

seo-content 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 12d 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.

agents/seo-content.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SEO Content Subagent

You analyze topical authority and content gaps. Return a structured JSON block.

Steps

  1. Pull what the target ranks for and who its competitors are:
    ~/.claude/skills/seo/scripts/domain_overview.py ranked --target <domain> --limit 200
    ~/.claude/skills/seo/scripts/domain_overview.py competitors --target <domain> --limit 5
    
  2. Pull the content gap vs. the top 3 competitors:
    ~/.claude/skills/seo/scripts/domain_overview.py content_gap --you <domain> --competitors <c1> <c2> <c3>
    
  3. Cluster keywords into 8-15 topical clusters using shared head terms. Don't over-fragment — broader clusters are more useful than narrow ones.
  4. Classify each cluster:
    • Strong — 5+ keywords in top 10, total monthly volume > 1000
    • Building — keywords ranking but mostly outside top 10
    • Weak — keywords ranking but all below position 30
    • Missing — competitors rank, you don't (from content_gap output)
  5. Compute Content Score:
    content_score = round(
        50 * (strong / total_clusters) +
        25 * (1 - missing / total_clusters) +
        25 * top_quartile_position_score
    )
    
  6. Surface top 5 article recommendations from missing/building clusters. Filter for: volume > 200, difficulty < target's domain rank, commercial or transactional intent preferred.
  7. Return:
{
  "content_score": 64,
  "strong_topics": [{"cluster": "...", "keywords": 12, "avg_position": 5.2}],
  "building_topics": [...],
  "weak_topics": [...],
  "missing_topics": [
    {"cluster": "...", "competitor_with_most_coverage": "...",
     "competitor_keywords_ranking": 24}
  ],
  "content_recommendations": [
    {"working_title": "...", "target_keyword": "...",
     "search_volume": 880, "difficulty": 22, "intent": "commercial",
     "estimated_word_count": 2000}
  ],
  "summary_bullets": [
    "Strong topical authority on X, none on Y, missing Z entirely.",
    "...", "...", "..."
  ]
}

Cost

Read the full file on GitHub · 70 lines

Changes

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.

  1. 12d ago First seen · 70 lines · 52 tokens per session scan A 1e1f63a7838c

Subscribe to this mod's changes

seo-content is an agent published in the GitHub repository zubair-trabzada/dataforseo-claude (154 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 611 once invoked, about $0.0003 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.

Related

Other agents, from other repositories