DataForSEO SERP Tracker
Pricing
from $0.01 / 1,000 results
DataForSEO SERP Tracker
Track keyword rankings, analyze SERPs & perform keyword research using DataForSEO API. Get organic results, featured snippets, people also ask & more for any keyword. Live SERP Analysis, Keyword Research, Ranked Keywords, Competitor Analysis, Multi-Device, BYOK: Bring your own DataForSEO API creds
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
The Howlers
Maintained by CommunityActor stats
0
Bookmarked
356
Total users
20
Monthly active users
11 days ago
Last modified
Categories
Features
Share
Track keyword rankings, analyze SERPs, and perform keyword research using the DataForSEO API. Get organic results, featured snippets, people also ask, and more for any keyword.
No API key needed. The actor uses its own DataForSEO access and bills per event. If you have a DataForSEO account, you can add your own login and password instead.
Quick Start
Check the top 10 Google results for a keyword
{"task": "serp_live","keyword": "coffee shop","location": "United States","languageCode": "en","searchEngine": "google","device": "desktop","depth": 10}
Input Parameters
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
task | string | "serp_live" | No | The task to perform |
keyword | string | - | No | The keyword to search for (for SERP tasks) |
keywords | array | - | No | Multiple keywords for batch operations |
domain | string | - | No | Target domain for ranked keywords or competitor analysis |
location | string | "United States" | No | Location for search results (e.g., 'United States', 'New York,New York,United States') |
locationCode | integer | - | No | DataForSEO location code (alternative to location name) |
languageCode | string | "en" | No | Language code (e.g., 'en', 'es', 'fr') |
searchEngine | string | "google" | No | Search engine to use |
device | string | "desktop" | No | Device type for search |
depth | integer | 100 | No | Number of results to fetch (10-700) |
taskId | string | - | No | Task ID for retrieving async results |
dataForSeoLogin | string | - | No | Your own DataForSEO API login (email). Leave empty to use the actor's built-in access |
dataForSeoPassword | string | - | No | Your own DataForSEO API password. Leave empty to use the actor's built-in access |
webhookUrl | string | - | No | URL to receive results when the run completes (for Zapier, Make, n8n integrations) |
Pricing
This actor uses pay-per-event billing:
| Event | When it is charged | Price |
|---|---|---|
| Actor start | Once when the run starts, one event per GB of memory (minimum one). At the default 1 GB of memory that is $0.10 per run | $0.10 per GB |
| SERP Query | Once per keyword. A live SERP run (serp_live) is one query. A batch (serp_task_post) is one query for each keyword DataForSEO accepts, so a 20 keyword batch is 20 queries. Fetching a task's results (serp_task_get) is not charged as a query, because that keyword was paid for when it was posted | $0.005 |
| Keyword Research | Once per run of keyword_suggestions, keyword_ideas or search_volume, however many keywords come back | $0.05 ($0.15 from November 23, 2026) |
| Competitor Analysis | Once per run of ranked_keywords or competitors, however many rows come back | $0.10 |
| Result | Each item written to the default dataset | $0.00001 |
Batches respect the run's maximum total charge. If the cap cannot cover every keyword, the run submits only the keywords it can pay for, lists the rest in keywordsNotSubmitted, and says so in the run's status message. Keywords that are not submitted are not charged.
A task DataForSEO could not complete charges no SERP Query, Keyword Research or Competitor Analysis event. Only the actor start and the one result row are billed. The run still ends as succeeded, so check the row's status:
- When DataForSEO reports that Google has no results for the keyword (code 40102 No Search Results), the row has
statusset tono_results, an emptyorganicResultslist andorganicCount0. - When a
serp_task_gettask is not finished yet, the row hasstatusset topending. Runserp_task_getagain in a minute. - When DataForSEO rejects every keyword in a
serp_task_postbatch (for example 40501 Invalid Field: 'location_name'), the row hasstatusset toerrorand the reason inerror. Each keyword inresultscarries its ownstatusCode,acceptedset to false and its reason inerror. No SERP Query is charged. When DataForSEO rejects only some keywords, the row stayssuccess, only the accepted keywords are charged, and each rejected keyword carries its reason the same way. - Any other DataForSEO error (for example 40100 when your own login or password is wrong, 40501 for an unsupported location, or 40401 for a task ID that does not exist) writes a row with
statusset toerror, the reason inerrorand DataForSEO's code indataForSeoStatusCode. The run's status message gives the same reason. Onserp_liveand the keyword and competitor tasks, temporary errors such as 40101 Internal SE Server Error or 50000 Internal Error are retried twice before the row reports them. Onserp_task_postandserp_task_getthey are reported right away, so run the task again later.
Google may ignore the site: filter and return pages from other domains, for example when the site has no page that matches the rest of the query. That is a normal result, not no_results, and it is charged as one SERP Query. Check the domain of each returned URL before you read a site: search as a match.
Troubleshooting
"Not Authorized" or "Unauthorized"
This only happens with your own DataForSEO credentials: the login or password is wrong, or your DataForSEO account cannot use that endpoint. Check both fields, or leave them empty to use the built-in access.
"API error 429" or "Rate limit"
Too many requests. Wait a minute and try again, or reduce the number of items per run.
"Invalid Field: 'location_name'" on keyword ideas, ranked keywords or competitors
keyword_ideas, ranked_keywords and competitors use DataForSEO Labs, which covers country locations only. Use a country such as "United States" or its location code (2840).
No results or an error row
Every run writes one row. Read its status, and its error or message field, which say what DataForSEO answered. Common causes:
- Invalid input format (check the examples above)
- A location DataForSEO does not recognize
- The target data doesn't exist or is too small to track
How do I see sample output first?
Set demoMode to true. The run returns sample data, makes no DataForSEO calls and charges no query events.
Built by John Rippy | Actor Arsenal