Google Jobs Scraper

Google Jobs Search queries (e.g. Teacher) and/or full URLs (e.g. https://www.google.com/search?q=teacher&ibp=htl;jobs).

Enter one item per line.

The maximum number of search result pages for each search query.

If checked, the crawler will return results in a structure suitable for CSV format. Only 'googleJobs' results are included. CSV headers would be: title, companyName, location, description...

Notice: To get Google Jobs results from a location, please use UULE param(Setting country to 'es' will not return Google Jobs Results from Spain. To get Google Jobs Results from Spain, please use UULE param) .

This param is for 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.

Allow you to search jobs within the radius - in kilometers.

Jobs results can be filtered by this filter param. The filter param can built from categories.param:categories.options.value. Eg: date_posted:today,employment_type:FULLTIME

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.