> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/getting-started/tutorials/no-code-tutorials/keyword-rankings-no-code.md).

# Keyword Rankings

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.

***

## Step 1: Create the project

Click [**DataPipeline**](https://dashboard.scraperapi.com/projects) in the left sidebar.

1. Select **New project**.
2. Select the **Google search** tile.

## Step 2: Configure input settings

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 women
```

For larger keyword lists, switch to **Upload file** and upload a CSV with one keyword per row.

## Step 3: Configure output settings

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.

## Step 4: Set scraping frequency

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.

## Step 5: Review and start

Click **Review & start scraping**. The Job summary panel shows the estimated credit cost before you confirm.

## Step 6: Review results

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.

## Additional options

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 `&`.

{% hint style="info" %}
Some parameters increase the cost per request. Check the Cost per Job panel before committing to a configuration at scale.
{% endhint %}

***

{% hint style="info" %}
Prefer to set this up in your own codebase? [Try the API playground instead](/getting-started/tutorials/api-tutorials/keyword-rankings-api.md).
{% endhint %}

## More tutorials

* [Scrape any URL](/getting-started/tutorials/no-code-tutorials/any-url-no-code.md)
* [Track prices across Amazon and Walmart](/getting-started/tutorials/no-code-tutorials/track-prices-no-code.md)
* [Monitor unauthorized sellers and MAP violations](/getting-started/tutorials/no-code-tutorials/monitor-sellers-no-code.md)
* [Monitor Google Shopping prices](/getting-started/tutorials/no-code-tutorials/google-shopping-no-code.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scraperapi.com/getting-started/tutorials/no-code-tutorials/keyword-rankings-no-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.