Serp keyword research
Skill Crawlora-org/crawlora-skills/skills/serp-keyword-research
Crawlora Agent Skills — structured public web data (search, e-commerce, social, finance, app stores, media, reviews) via the Crawlora REST API. Installable in any agent with the skills CLI or as a Claude Code plugin marketplace.
npx -y skills add Crawlora-org/crawlora-skills --skill serp-keyword-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Runs SERP and keyword research via the Crawlora API — Google, Bing, and Brave search results plus Google Trends interest-over-time and related/rising queries — returning clean JSON. Use when the user wants search-engine rankings, SERP snapshots, autocomplete/keyword suggestions, or trend data instead of scraping result pages.
SKILL.md
3.8 KB, 940 tokens by cl100k_base, as published. Nobody here has run it
SERP & keyword research
Capture search-engine results (Google, Bing, Brave) and keyword/trend signals (Google autosuggest, Google Trends) as normalized JSON from the Crawlora API.
When to use this skill
- "What ranks for <query> on Google / Bing?" / "snapshot the SERP for …".
- "Keyword ideas / autocomplete for …" (suggest endpoints).
- "Is <topic> trending?" / "interest over time / by region for <keyword>."
- "Related and rising queries for …" (Google Trends).
- SEO/SERP monitoring, keyword discovery, or trend research.
Setup (one-time)
- Get a free Crawlora API key (2,000 credits/mo, no card) at https://crawlora.net.
export CRAWLORA_API_KEY=sk_your_key_here- All requests:
x-api-key: $CRAWLORA_API_KEYagainsthttps://api.crawlora.net/api/v1. Missing/invalid key →401.
How it works
- SERP — Google search is
POST /google/searchwith asearchOptionbody; Bing and Brave areGET /bing/search?q=...andGET /brave/search?q=.... Cross-check engines for coverage; on a503challenge, fall back to another engine. - Verticals — news/videos/images per engine (
/google/news,/bing/videos, …). - Keyword ideas — autosuggest:
GET /google/suggest?q=...(and/bing/suggest,/brave/suggest). - Trends — Google Trends
POSTendpoints:/google/trends/explore/interest-over-time,/interest-by-region,/related-topics,/rising-queries,/top-queries(body:{"keywords":[...]}), plusGET /google/trends/trendingfor what's hot now.
Full endpoint list, methods, and params: reference/endpoints.md.
Calling the API
# GET search engines + suggest:
scripts/crawlora.sh /bing/search q="web scraping api" | jq '.'
scripts/crawlora.sh /brave/search q="web scraping api" | jq '.'
scripts/crawlora.sh /google/suggest q="web scraping" | jq '.'
# POST endpoints take a JSON body (note -X POST):
scripts/crawlora.sh -X POST /google/search '{"searchOption":{"q":"web scraping api"}}' | jq '.'
scripts/crawlora.sh -X POST /google/trends/explore/interest-over-time '{"keywords":["web scraping"]}' | jq '.'
Raw curl fallback:
curl -fsS -H "x-api-key: $CRAWLORA_API_KEY" \
"https://api.crawlora.net/api/v1/bing/search?q=web%20scraping%20api" | jq '.'
Endpoint reference
See reference/endpoints.md for every Google, Bing,
Brave, and Google Trends endpoint this skill uses (method, path, params, description).
Examples
- SERP snapshot:
POST /google/search(and/bing/search) for a target query; record the ranked result titles/URLs to track positions over time. - Keyword expansion: seed term →
/google/suggest→ for each suggestion,POST /google/trends/explore/rising-queriesto find momentum. - Trend check:
POST /google/trends/explore/interest-over-timewith{"keywords":["electric bikes","e-bikes"]}and compare the series.
Notes & limits
- Credits / pay-on-success: billed only on
2xx; free tier 2,000 credits/mo. Key at https://crawlora.net. - Public data only — public search results; respect each engine's terms.
- Security: key lives in
CRAWLORA_API_KEYonly — never hardcode, query-param, or commit it. - Search endpoints may return
503when the engine serves a challenge page — retry or switch engines (Google ↔ Bing ↔ Brave). Google search is rate-limited to ~1 req/s (429on excess).
What ships with it: 2 files
24.4 KB alongside SKILL.md, 1 of them executable
reference/
- endpoints.md22.6 KB
scripts/
- crawlora.shruns1.8 KB