Google Jobs Scraper

Search Google Jobs by job title and location, then collect normalized listing cards and expanded job details. It only emits jobs extracted from Google's own Jobs results.

By default the Actor requests the static Jobs vertical (udm=8) through Apify Proxy's HTTP-only GOOGLE_SERP group, which serves plain-HTTP absolute-URI forwarding, and parses the result cards straight from the returned HTML. When the configured proxy is not that group, the Actor falls back to the browser transport: it opens Google's Jobs search surface with Playwright, loads additional cards up to the configured limit, and expands each available job detail panel.

Input

Field	Required	Default	Description
query	Yes	software engineer	Job title or keywords entered in Google Jobs.
location	No	New York, NY	City, state, region, or country included in the search.
queries	No	[]	Additional job queries. Native Google pages are processed concurrently and output is deduplicated globally.
maxItems	No	50	Maximum unique job records.
maxConcurrency	No	2	Concurrent search pages, from 1 to 4.
gl	No	us	Two-letter Google country code.
hl	No	en	Google interface language.
experienceLevel, salaryMin, salaryMax, remoteFilter, educationLevel	No	—	Retained for Cloud input compatibility and recorded in requestedFilters when supplied. The local Actor does not apply these criteria to result matching yet.
maxScrolls	No	10	Maximum result-list loads.
maxRequestRetries	No	3	Bounded retries for temporary failures and blocks.
navigationTimeoutSecs	No	60	Navigation timeout.
requestHandlerTimeoutSecs	No	300	Whole search-page handler timeout.
detailTimeoutSecs	No	12	Timeout while opening one job's detail panel.
proxyConfiguration	No	Apify Proxy GOOGLE_SERP group	Apify Proxy or custom proxy configuration. Selecting the HTTP-only GOOGLE_SERP group uses the static-SERP HTTP transport; any other configuration (including residential) uses the browser transport, and GOOGLE_SERP is stripped before a browser session is created.

The complete accepted input schema, including compatibility fields and bounds, is in .actor/input_schema.json.

Output

Records contain the fields Google exposes for each job when available:

• identity: stable id, jobId, result type, global position, title, company, and company logo;
• source provenance: dataSource, retrievalMethod (googleJobsSerpHtml for the static-SERP transport, googleJobsPage for the browser transport), page number and result position, and Google's own googleJobUrl deep link when the card exposes one;
• location: location, city, state/region, country, remote/workplace type;
• employment and compensation: employment types, salary range, currency, period;
• job content: full description, qualifications, responsibilities, detailed benefits, card benefit highlights;
• dates and source: posted time, source board, source domain;
• application: primary apply URL and all available apply links;
• search context: query, requested location, locale, Google Jobs URL, requested filter values when supplied, and scrape timestamp.

Unavailable optional fields are omitted recursively. The Actor does not invent values from the search input, does not store challenge pages, and does not store raw Google responses. Every emitted record includes at least 20 populated top-level fields, with source-backed listing values and search or retrieval metadata.

The complete dataset field contract is in .actor/dataset_schema.json.

How to use

Enter a job title and location in the Apify Input tab, choose result limits and a supported proxy, and start the Actor. Review records in the Output dataset.

Google may block automated requests or omit the Jobs vertical. CAPTCHA, authentication, explicit access-control pages, and pages without source-backed job cards are reported as failures and are never stored as dataset records. A challenge verdict is only reached after the card parse produced zero records, so a healthy page whose snippets merely mention verification is never discarded. The Actor reads only Google's own Jobs surface and never falls back to a third-party job board.

The static Jobs SERP carries the listing cards (title, company, location, salary, posted date, employment type, benefit and qualification highlights, and Google's htidocid deep link) but not the per-job detail panel, so description, applyUrl, applyLinks, responsibilities, and detailed benefits stay absent on the HTTP transport unless the browser transport is used. They are never fabricated.