# Google Jobs Scraper | Job Listings & Apply Links (`gridforge/google-jobs-scraper`) Actor

Extract Google Jobs listings with titles, companies, locations, descriptions, apply links, and salary when listed. About 10 jobs per search; add more specific searches for more coverage. $3 per 1,000 jobs plus a small run-start fee. Export JSON, CSV, or Excel.

- **URL**: https://apify.com/gridforge/google-jobs-scraper.md
- **Developed by:** [GridForge](https://apify.com/gridforge) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 job returneds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Google Jobs Scraper: Job Listings & Apply Links

Extract Google Jobs search results as structured job records, including title, company, location, description, apply links, listed salary, job type, posting text, and available qualifications, benefits, and responsibilities.

**About 10 jobs per search; add more specific searches for more coverage.** This version fetches one page and does not paginate. A higher `maxJobsPerQuery` cannot force Google to return additional pages.

### Quick start

1. Add a job query such as `data analyst`.
2. Choose a location and Google country, if needed.
3. Keep the default Google SERP proxy configuration.
4. Start the Actor and inspect the results. Export JSON, CSV, or Excel, or use the Apify API.

### Input example

```json
{
  "queries": ["data analyst"],
  "location": "New York, NY",
  "maxJobsPerQuery": 10,
  "country": "us",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["GOOGLE_SERP"]
  }
}
```

The query and location match the form's current example values. Input names and values match the existing schema; no schema or runtime logic change is proposed.

### Output example (illustrative)

```json
{
  "query": "data analyst",
  "searchLocation": "New York, NY",
  "title": "Data Analyst",
  "company": "Example Company",
  "location": "New York, NY",
  "salary": null,
  "jobType": "Full-time",
  "posted": "2 days ago",
  "applyLinks": [{"source": "Company website", "url": "https://example.com/careers"}],
  "qualifications": ["Example qualification"],
  "benefits": [],
  "responsibilities": ["Example responsibility"],
  "description": "Example description."
}
```

This is a schema illustration, not an actual opening or recorded scrape. Fields can be null or missing when the source does not supply them. Salary is source text when present, not a calculated pay estimate. `posted` can be relative text. Apply links are not independently vetted job offers.

### Inputs

| Field | Default/example | Meaning |
|---|---|---|
| `queries` | Required; example `data analyst` | One search phrase per array item |
| `location` | Empty; form example `New York, NY` | Search location; empty lets Google decide |
| `maxJobsPerQuery` | 10 | Output cap per search, not a pagination setting; schema range 1-50 |
| `country` | `us` | Two-letter Google country code |
| `proxyConfiguration` | Apify proxy, `GOOGLE_SERP` | Keep the existing default for Google Jobs requests |

### Pricing

The job-result event costs **$0.003 per returned job** ($3 per 1,000 jobs). The current configuration also includes an **Actor Start event at $0.00005**, defined per GB of memory with a minimum of one event. At the default 1 GB this is $0.00005 per run.

Failed searches do not incur job-result events, but the start event can still apply. Users currently do not pay platform usage costs separately. Confirm the live Pricing tab before running. No prices or proxy settings were changed as part of this documentation update.

### FAQ

**How do I get more jobs?** Add more specific searches by role, neighborhood, seniority, or work arrangement. Searches can overlap; deduplicate across runs if needed. This version returns about 10 jobs per search and does not paginate.

**Why is salary missing?** Google does not provide a separate salary field for every job. A description may mention compensation even when `salary` is null. No salary is invented.

**Does a successful run guarantee every query worked?** No. Inspect individual records and any error rows. A platform status is not a completeness guarantee.

**Can I schedule it?** Yes, through Apify schedules. Each scheduled run follows the live pricing rules. Jobs and availability change over time.

**Is this a job application service?** No. It collects search results; it does not apply, contact employers, verify employers, or guarantee that an opening remains available.

Not affiliated with or endorsed by Google.

# Actor input Schema

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

What to search for, e.g. 'data analyst' or 'remote customer support'. One search per line.

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

City, state or country, e.g. 'New York, NY' or 'remote'. Leave empty to let Google decide.

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

Google shows about 10 jobs per search. For more results, add more specific searches (e.g. by neighborhood or seniority).

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

Two-letter country code for the Google version used, e.g. us, gb, ca.

## `proxyConfiguration` (type: `object`):

Keep the default Google SERP proxy - Google Jobs needs it.

## Actor input object example

```json
{
  "queries": [
    "data analyst"
  ],
  "location": "New York, NY",
  "maxJobsPerQuery": 10,
  "country": "us",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "GOOGLE_SERP"
    ]
  }
}
```

# 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": [
        "data analyst"
    ],
    "location": "New York, NY",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "GOOGLE_SERP"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("gridforge/google-jobs-scraper").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": ["data analyst"],
    "location": "New York, NY",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["GOOGLE_SERP"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("gridforge/google-jobs-scraper").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": [
    "data analyst"
  ],
  "location": "New York, NY",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "GOOGLE_SERP"
    ]
  }
}' |
apify call gridforge/google-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

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/ZXyCA5veHIIYeppcq/builds/eGnhaFV3jRsKZ6qrq/openapi.json