dataforseo-serp-api_skill

This skill fetches localized SERP results from DataForSEO to track rankings and monitor search visibility across locations and languages.

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill leonardo-picciani/dataforseo-agent-skills --skill dataforseo-serp-api

SKILL.md5.2 KB

Overview

This skill connects to the DataForSEO SERP API to fetch localized search engine results for rank tracking, SERP monitoring, and one-off SERP lookups. It supports live and task-based flows, returns normalized summaries for user consumption, and includes raw payloads for debugging and auditing. The skill is designed for multi-engine queries (Google, Bing, YouTube) and location/language-specific requests.

How this skill works

The skill selects the appropriate SERP endpoint (engine and result format: regular, advanced, or HTML), gathers required inputs (query, location, language, device, depth), and chooses live or task mode depending on volume and scheduling needs. It performs HTTP requests with HTTP Basic Auth, validates top-level and task status codes, then returns a compact normalized result plus the raw response for troubleshooting.

When to use it

Track daily or scheduled keyword rankings across countries, cities, or languages
Fetch an ad-hoc Google/Bing/YouTube SERP for analysis or intent classification
Compare SERPs across locations or devices to detect regional differences
Monitor SERP features (local pack, news, images) and detect volatility
Capture SERP HTML or screenshots for forensic SEO or reporting

Best practices

Choose Live for interactive queries and Task-based for high-volume or scheduled jobs
Always include location + language when you need localized results
Validate top-level status_code == 20000 and check each tasks[].status
Store task IDs for polling or use postback_url to receive results asynchronously
Return both a normalized summary and the raw API payload for debugging

Example use cases

Build a rank-tracking product that polls daily and stores historical positions per location
Compare top 10 organic results for a keyword across US and UK and surface differing competitors
Monitor a set of transactional keywords for SERP feature changes and send alerts on volatility
Fetch Google Maps/local pack entries for a query and extract business names, ratings, and addresses
Generate SERP screenshots or HTML snapshots to include in client reports or tickets

FAQ

Yes. The API uses HTTP Basic Auth (login:password). Provide these credentials and encode them as Basic auth for requests.

When should I use task-based flows instead of live calls?

Use task-based flows for scheduled polling, high-volume batches, or when you need asynchronous processing and the ability to poll tasks_ready/task_get.

What indicates a successful response?

Treat top-level status_code == 20000 as success, and verify each tasks[].status is successful before using task results.