Keyword Rankings
Last updated
⌘Ctrlk
DataPipeline is ScraperAPI's no-code dashboard for scheduled scraping. In this tutorial, you will use DataPipeline to track Google Search rankings for any keyword list. By the end, you will have daily SERP snapshots with rank, SERP features, and metadata for every keyword you monitor, so you can catch rank drops and competitor moves without juggling tools or flaky scrapers.
Click DataPipeline in the left sidebar.
Select New project.
Select the Google search tile.
Under Input settings, choose List and enter your keywords, one per line:
best running shoes
best running shoes for beginners
best running shoes men
best running shoes womenFor larger keyword lists, switch to Upload file and upload a CSV with one keyword per row.
Under Output settings, choose Download. Results will be available in the dashboard when the job completes. For automated pipelines, enter a Webhook URL instead so results are posted to your server as they arrive.
JSON gives you the full structured response including all SERP features. CSV flattens each result to a row — position, title, link, and snippet become columns, and nested fields like related_questions are retained as JSON-encoded strings in their own column.
Under Scraping frequency, select Just scrape once. To track rankings on a recurring basis, switch this to Daily, Weekly, or another interval. Recurring schedules require a paid plan.
Click Review & start scraping. The Job summary panel shows the estimated credit cost before you confirm.
Click into the project after the run completes and click Download results. Results are retained for 30 days.
Each keyword produces a set of rows with position, title, link, and snippet. Compare result sets across dates to spot ranking changes.
Under Additional options & filters you can fine-tune your requests:
Country code: targets a specific country's Google Search results.
Domain: sets the Google domain to search (e.g. co.uk, com.au).
Time based search: filters results by recency — past 24 hours, past week, past month, or past year.
UULE: encodes a specific city for local search results.
Number of results: sets how many organic results to return per page.
Additional parameters: pass any additional supported ScraperAPI parameters, separated by &.
Some parameters increase the cost per request. Check the Cost per Job panel before committing to a configuration at scale.
Prefer to set this up in your own codebase? Try the API playground instead.
Last updated