Web Scraper
No credit card required
Web Scraper
No credit card required
Crawls arbitrary websites using the Chrome browser and extracts data from pages using JavaScript code. The Actor supports both recursive crawling and lists of URLs and automatically manages concurrency for maximum performance. This is Apify's basic tool for web crawling and scraping.
Do you want to learn more about this Actor?
Get a demoChange Log
3.0.14 (2023-08-22)
- Updated Crawlee version to v3.5.2.
- Updated Node.js version to v18.
- Added new options:
- Dismiss cookie modals (
closeCookieModals
): Using the I don't care about cookies browser extension. When on, the crawler will automatically try to dismiss cookie consent modals. This can be useful when crawling European websites that show cookie consent modals. - Maximum scrolling distance in pixels (
maxScrollHeightPixels
): The crawler will scroll down the page until all content is loaded or the maximum scrolling distance is reached. Setting this to0
disables scrolling altogether. - Exclude Glob Patterns (
excludes
): Glob patterns to match links in the page that you want to exclude from being enqueued.
- Dismiss cookie modals (
3.0 (version-3
)
- Rewrite from Apify SDK to Crawlee, see the v3 migration guide for more details.
- Proxy usage is now required.
2.0 (version-2
)
Main difference between v1 and v2 of the scrapers is the upgrade of SDK to v2, which requires node v15.10+. SDK v2 uses http2 to do the requests with cheerio-scraper, and the http2 support in older node versions were too buggy, so we decided to drop support for those. If you need to run on older node version, use SDK v1.
Please refer to the SDK 1.0 migration guide for more details about functional changes in the SDK. SDK v2 basically only changes the required node version and has no other breaking changes.
- deprecated
useRequestQueue
option has been removedRequestQueue
will be always used
- deprecated
context.html
getter from thecheerio-scraper
has been removed- use
context.body
instead
- use
- deprecated prepareRequestFunction input option
- use
pre/postNavigationHooks
instead
- use
- removed
puppeteerPool/autoscaledPool
from the crawlingContext objectpuppeteerPool
was replaced bybrowserPool
autoscaledPool
andbrowserPool
and available on thecrawler
property ofcrawlingContext
object
- custom "Key-value store name" option in Advanced configuration is now fixed, previously the default store was always used
Actor Metrics
2.4k monthly users
-
268 stars
>99% runs succeeded
38 days response time
Created in Mar 2019
Modified 4 months ago