Google Jobs Scraper (reliable)

Fetch job listings from Google Jobs for up to 100 search queries per run: title, company, location, source board, posting date, employment type, salary when shown, and a stable job ID for deduplication across runs. Built for job boards, recruitment analytics and AI agents — strict schema, explicit error codes, and you only pay for result pages that are actually delivered.

Why this scraper

• Only successful results are charged. A query that hits a block or returns no results shows up as a clear error record at no cost.
• Fails loudly, never silently. When Google changes its page, you get an explicit error instead of a quietly empty dataset — and we fix it fast; reliability is the product.
• Clean business data. Job postings as companies published them: no scraping of personal contact details, no profile data.
• Deduplication built in. Every job carries Google's stable job ID, so merging runs and tracking new postings over time is trivial.

Who this is for

Recruiters and job boards tracking what is being posted, market analysts watching hiring demand, and sales teams using job ads as a buying signal.

Google Jobs aggregates across LinkedIn, Indeed and company career pages, so one query covers sources you would otherwise scrape separately.

Who this is not for

Read this before you buy. This actor returns job postings as companies published them: no recruiter names, no e-mail addresses, no phone numbers, and it never will. It does not apply to jobs or open the source board; via tells you where the posting lives. Results are region-bound, exactly as on Google Jobs: a query with the wrong country returns nothing (at no cost). Billing is per delivered result page of roughly ten jobs, not per job; if you need a strict per-job price, another actor may fit your accounting better.

Input example

{
    "queries": ["software engineer amsterdam", "data analyst rotterdam"],
    "location": "",
    "country": "NL",
    "maxJobsPerQuery": 50
}

country sets both the proxy exit country and Google's region parameter; Google Jobs results are region-bound, so match it to where the jobs should be. Queries can be in any language; interface labels (posting date, employment type) come back in English.

Output example

{
    "query": "software engineer amsterdam",
    "status": "ok",
    "jobCount": 42,
    "jobs": [
        {
            "jobId": "abc123",
            "title": "Software Engineer",
            "company": "Example B.V.",
            "location": "Amsterdam, Netherlands",
            "via": "LinkedIn",
            "posted": "3 days ago",
            "salary": "",
            "scheduleType": "Full-time"
        }
    ]
}

A failed query produces an error record instead (and is not charged):

{"query": "someterm", "status": "error", "errorCode": "NO_RESULTS", "error": "No job cards found"}

Error codes: NO_RESULTS, BLOCKED, FETCH_ERROR. INPUT_TRUNCATED appears once when your input is longer than this actor accepts.

Related actors from steadydata

• company-career-site-jobs (publishing soon): the companies' own boards, without the aggregator
• google-trends-batch: whether demand for a role is rising

Pricing

Pay per event: one job-page-fetched event per delivered result page. No charge for failed queries, no separate platform-usage surcharge.

FAQ

Where does the data come from? Google Jobs aggregates postings from LinkedIn, Indeed, company career sites and more; each job's via field tells you the source board.

Can I search in my own language? Yes — phrase queries in any language and set country to the target region; only the metadata labels come back in English.

Is personal data collected? No. Only job postings as published by companies; the actor extracts no personal contact fields.

Why is it so much cheaper than comparable actors? Because it does not drive a browser. It reads the page Google renders server-side, which is faster and far lighter, and that saving goes into the price.

I get no results, what now? Almost always the country does not match the query. Google Jobs is region-bound, so searching a Dutch city with the country set to US returns nothing. Set country to the region the jobs are in; the error message says so too, and you are not charged for it.