Google Search Results Scraper

Google Search terms (e.g. food in NYC) and/or full URLs (e.g. https://www.google.com/search?q=food+NYC). Please enter one item per line.

Maximum number of Google Search result pages crawled for each search term or URL. Please note that Google limits the number of search results pages it shows you to between 300 and 400.

Number of search results for each Google result page. By default, Google Search returns 10 results per page. The allowed values are: 10, 20, 30, 40, 50 and 100. Since our Free plan contains 100 free SERP proxies, and every request consumes 1 proxy, you will get exactly 100 free requests, no matter the amount of results you will get per each. This is why to get maximum value from this scraper, we recommend setting up this parameter to its maximum, 100.

If checked, the scraper will return results for the mobile version of the Google search. By default, desktop results are returned.

This option allows to arrange the results in a structure suitable for CSV format. If checked, Related queries with respective URLs, People Also Ask, reviews and prices will not be included. Only organic and paid results will be included. Note: please take into account that displayed paid results are still heavily dependent on your location and browsing history.

Country determines the IP address of the proxy used for the search and the Google Search domain (e.g. google.es for Spain). By default, the actor uses United States (google.com).

Language for the search results, which is passed to Google Search as the hl URL query parameter. Only set this if you want to use a non-default language for the selected country.

The code for the exact location for the Google search. It's passed to Google Search as the uule URL query parameter. You can use the UULE code generator. Learn more about emulating local search.

Maximum number of search results pages the scraper will load in parallel. A higher number means you will get your results faster, but it will also burn through your available proxies quicker.

If checked, the HTML of the Google Search results pages will be stored to the default dataset, under the html property. This is useful if you need to process the HTML, but it makes the dataset large and reduces performance.

If checked, the HTML of the Google Search results pages will be stored to the default key-value store and links to the files stored to the dataset under the htmlSnapshotUrl property. This is useful for debugging, since you can easily view the pages in the browser. However, the use of this feature may present some performance penalty.

If checked, the lower quality results that Google normally filters out will be included. This usually consists of a few hundred extra results.

Custom JavaScript function to extract additional attributes from the HTML of the Google result pages. The function accepts the same parameters as the handlePageFunction of the CheerioCrawler in Apify SDK. The return value of the function is saved to the results as the customData property.