Skip to content
Agentmart
Submit a tool

dataforseo

Keyword & SERP research via the DataForSEO API — search volume, competition, CPC, keyword ideas for naming/SEO decisions

Skill by alinaqi

IndexedMIT★ 711
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/alinaqi-dataforseo

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Keyword & SERP research via the DataForSEO API — search volume, competition, CPC, keyword ideas for naming/SEO decisions

Use cases: backend, marketing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/dataforseo

What's inside

Skill name
dataforseo
Description
Keyword & SERP research via the DataForSEO API — search volume, competition, CPC, keyword ideas for naming/SEO decisions
License
MIT
Instructions
71 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (2)

  • SKILL.md
  • dataforseo.py

SKILL.md (first lines)

# DataForSEO Skill — keyword & SERP research

**Purpose:** Get real search demand (monthly volume, competition, CPC) and
keyword ideas from Google Ads data via [DataForSEO](https://dataforseo.com), so
naming and content decisions are grounded in data rather than intuition.

## Auth (never commit the key)

DataForSEO uses HTTP Basic auth. Provide credentials via environment only:

```bash
export DATAFORSEO_LOGIN="you@example.com"
export DATAFORSEO_PASSWORD="…"
# or a single combined value:
export DATAFORSEO_API_KEY="login:password"   # or its base64
```

The helper reads these from the env — it never hardcodes or logs the secret,
and only ever calls `api.dataforseo.com`. Keep the key in a local `.env` that is
git-ignored; do not paste it into the repo, a URL, or chat.

## Usage

The helper is `dataforseo.py` in this skill folder:

```bash
DFS="$(cat ~/.claude/.bootstrap-dir)/skills/dataforseo/dataforseo.py"

python3 "$DFS" whoami                                  # auth check + balance
python3 "$DFS" volume "claude code" "coding agent"     # search volume table
python3 "$DFS" ideas  "coding agent"                   # related keyword ideas
# options: --location <code, default 2840=US>  --language <code, default en>
```

`volume` → each keyword's monthly search volume, competition (LOW/MEDIUM/HIGH),
and CPC. `ideas` → the searched long-tail around a seed.

## Reading the results (naming decisions)

- **Zero / `n/a` volume on every candidate is itself the answer:** the names
  aren't search terms, so SEO can't rank them against each other — decide on
  clarity/brand and accept that discovery happens on GitHub/HN/X, not search.
- **Category term vs. brand term:** a huge-volume category word (e.g. the tool's
  ecosystem name) is where demand lives; a brand name rides it only if it
  contains it. Weigh discoverability against being on-brand for what you built.
- **Wrong-intent volume is a trap:** a candidate with existing volume may be
  drawing an audience searching for something *else* (a different industry
  meaning). That volume hurts, it doesn't help.
- **Competition + CPC** proxy commercial intent, not just popularity — high CPC
  means advertisers pay for that term (buyers), low CPC often means informational
  or noise.

## Cost & etiquette

`live` endpoints bill per call (search volume / ideas ≈ $0.05–0.10 each). Batch
many keywords into ONE `volume` call (it accepts up to 1000) rather than looping.
Check `whoami` for balance before large runs.

## Common endpoints (beyond the helper)

| Need | Endpoint |
|------|----------|
| Search volume | `keywords_data/google_ads/search_volume/live` |
| Keyword ideas | `keywords_data/google_ads/keywords_for_keywords/live` |
| SERP (who ranks) | `serp/google/organic/live/advanced` |
| Ranked keywords for a domain | `dataforseo_labs/google/ranked_keywords/live` |
| Competitor domains | `dataforseo_labs/google/competitors_domain/live` |

All take the same Basic-auth header; POST a JSON array of task objects.

From alinaqi/maggy, MIT.

More from alinaqi/maggy

Signals

Stars
711
Forks
61
Open issues
0
Last commit (this folder)
Sep 19, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from alinaqi

Cite this page

dataforseo skill. Agent Mart. https://agentmart.dev/skills/alinaqi-dataforseo (last updated 2026-10-24)