# Google Jobs Scraper: by query and location, with salary (`steadydata/google-jobs-reliable`) Actor

Job listings from Google Jobs by query and location: title, company, location, source, posting date, salary when shown, and deduplicated apply links. Strict schema for pipelines and AI agents; only successfully delivered result pages are charged.

- **URL**: https://apify.com/steadydata/google-jobs-reliable.md
- **Developed by:** [Steadydata Team](https://apify.com/steadydata) (community)
- **Categories:** Jobs, AI, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 result page delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{
    "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

```json
{
    "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):

```json
{"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](https://apify.com/steadydata/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.

# Actor input Schema

## `queries` (type: `array`):

Job search queries, e.g. 'software engineer amsterdam'. Combine role and place in one query, or set location separately below.

## `location` (type: `string`):

Optional location appended to every query, e.g. 'Amsterdam' or 'Netherlands'.

## `maxJobsPerQuery` (type: `integer`):

Stop paginating after this many jobs per query.

## `country` (type: `string`):

ISO country code (e.g. US, NL, DE). Determines both the proxy exit country and the gl parameter; Google Jobs results are region-bound, so match this to where the jobs should be.

## Actor input object example

```json
{
  "queries": [
    "software engineer new york"
  ],
  "location": "",
  "maxJobsPerQuery": 50,
  "country": "US"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "software engineer new york"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadydata/google-jobs-reliable").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "queries": ["software engineer new york"] }

# Run the Actor and wait for it to finish
run = client.actor("steadydata/google-jobs-reliable").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "software engineer new york"
  ]
}' |
apify call steadydata/google-jobs-reliable --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,steadydata/google-jobs-reliable"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XqNPY75EoLpyvhPG8/builds/9Y9iG9ccfawL56ken/openapi.json