Google Search Scraper

Google Search queries (e.g. food in NYC) and/or full URLs (e.g. https://www.google.com/search?q=food+NYC).

Enter one item per line.

Number of search results per page. By default, Google Search returns 10 results. The allowed values are: 10, 20, 30, 40, 50 and 100.

This setting only applies to Search queries, but not to URLs.

The maximum number of search result pages crawled for each search query or URL. Note that a value greater than one might significantly slow down the actor.

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

If checked, the crawler will return results in a structure suitable for CSV format. Only organic and paid results are included.

Country determines the IP address of the proxy used for the query and the Google Search domain (e.g. google.es for Spain). The values must be lower-cased ISO 3166 country codes supported by Google. By default, the actor uses United States (google.com).

This setting only applies to Search queries, but not to URLs.

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 values must be lower-cased ISO 639 language codes supported by Google.

This setting only applies to Search queries, but not to URLs.

The code for geolocation of search results. 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.

This setting only applies to Search queries, but not to URLs.

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

If checked, the HTML of 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 the pages in browser, but use of this feature has some performance penalty.

If checked, the lower quality results that Google normally filters out will be included. Usually it is few hundred extra results.

Custom JavaScript function to extract additional attributes from the HTML of the 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.