> 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/scraperapi-crawler-v2.0/introduction.md).

# Introduction

The `ScraperAPI Crawler` is ideal for scraping websites, where the data you want to extract spans across multiple linked pages. It’s great for extracting data from product listings, paginated search results, real estate catalogs - basically any structure, where one page leads to dozens or hundreds more. It takes care of **crawling**, **scraping**, **retries**, and delivers the results back to you (supports webhook callbacks too)**.**

## What the Crawler Does

* Discovers and scrapes new pages based on how it's configured.
* Skips duplicates to avoid infinite loops.
* Handles failed requests gracefully.
* Stops when the credit budget or depth limit is hit.
* Streams page results during the crawl and sends a full summary at the end.

Whether you're crawling 10 pages or 10,000, it runs the job from start to finish and saves each page result in real time (or sends it over to your webhook).

{% hint style="warning" %}
\*\* Free Plan limitations \*\*

* **Link depth:** limited to `1` (seed URL plus direct links).
* **Scheduling:** recurring schedules (hourly/daily/weekly/monthly) are not available.<br>

*Attempting to exceed these limits will return a `403` error.* *Upgrade to a paid plan to run deeper crawls and enable scheduling.*
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/scraperapi-crawler-v2.0/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.