# Google Jobs Scraper — Listings, Salary, Filters (`scrape.badger/google-jobs-scraper`) Actor

Scrape Google Jobs at scale: structured job listings with title, company, location, salary, posted date, job type, schedule, apply links, qualifications and responsibilities. Two data sources — Google Careers RPC (fast, ~1-2s) for Google's own openings.

- **URL**: https://apify.com/scrape.badger/google-jobs-scraper.md
- **Developed by:** [ScrapeBadger](https://apify.com/scrape.badger) (community)
- **Categories:** Jobs, Developer tools, Automation
- **Stats:** 53 total users, 12 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 job pages

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

### What does Google Jobs Scraper do?

Scrape [Google for Jobs](https://www.google.com/search?q=jobs) — the aggregator that pulls from LinkedIn, Indeed, company career pages and more. Keyword + location search with date-posted, job-type, remote, and radius filters.

### Why use Google Jobs Scraper?

- **Aggregated source.** LinkedIn, Indeed, Glassdoor, Monster, company careers — Google de-duplicates across them.
- **Filter set.** `date_posted`, `job_type`, `ltype` (remote), `lrad` (radius).
- **200+ country domains.** Local job markets with `gl` + `hl`.
- **Per-job apply link.** Direct-to-apply URL when Google surfaces it.
- **Two modes.** `rpc` (fast API) or `serp` (full SERP context).

### What data can Google Jobs Scraper extract?

| Field | Type | Description |
|---|---|---|
| title | string | Job title |
| company | string | Employer name |
| location | string | Job location |
| via | string | Source site |
| description | string | Full job description |
| posted\_at | string | Human-readable (e.g. '3 days ago') or ISO |
| schedule | string | Full-time / part-time / contract / internship |
| job\_type | string | Remote / hybrid / on-site |
| thumbnail | string | Company logo URL |
| apply\_link | string | Direct apply URL |

### How to scrape Google Jobs (Google for Jobs)

1. Click **Try for free**.
2. Enter your query in `q` (e.g. `senior backend engineer python`).
3. Optional: set `location`, `date_posted` (past day/week/month), `job_type`, `ltype` (remote only).
4. Set `gl` / `hl` for country + language.
5. Set `max_pages` — each page is ≈ 10 jobs.
6. Click **Start** — jobs stream into the dataset.

### How much will it cost?

**$0.008 per page (≈ $8 per 1,000 pages).** One call per page. A 3-page run pushes ≈ 30 jobs for $0.024.

#### Competitor benchmark

| Actor | Author | Price | Notes |
|---|---|---|---|
| bebity/indeed-scraper | bebity | $29 /mo subscription | Indeed-only |
| curious\_coder/linkedin-jobs-scraper | curious\_coder | ~$12 / 1k | LinkedIn-only |
| community/google-jobs-scraper | community | ~$10 / 1k | Google-aggregated |
| **scrape-badger/google-jobs-scraper** | **ScrapeBadger** | **$8 / 1k pages** | **20% below closest competitor** |

### Input

Configure the run in the **Input** tab above, or pass a JSON object matching the fields below when calling the Actor via the Apify API.

| Field | Required | Description |
|---|---|---|
| q | ✅ | Job search query. |
| mode | — | `rpc` (default, fast) or `serp` (rich SERP context). |
| location | — | City / region string. |
| date\_posted | — | Google enum: `today` / `3days` / `week` / `month`. |
| job\_type | — | Full-time / part-time / contract / internship. |
| ltype | — | Remote filter. |
| lrad | — | Radius in km / miles. |
| gl / hl | — | Country + language. |
| max\_pages | — | Pagination budget. |

### Output

Every successful run streams records into the run's dataset. Download as JSON, CSV, XML, Excel, or HTML from the **Dataset** tab; consume programmatically via the Apify API or webhooks.

Example record:

```json
{
  "title": "Senior Backend Engineer (Python)",
  "company": "Acme Corp",
  "location": "New York, NY (Remote)",
  "via": "LinkedIn",
  "description": "We're looking for\u2026",
  "posted_at": "3 days ago",
  "schedule": "Full-time",
  "job_type": "Remote",
  "thumbnail": "https://u2026/",
  "apply_link": "https://linkedin.com/jobs/view//u2026"
}
```

### Tips / Advanced options

- **Use `date_posted: today` for real-time sourcing.** Recruiters win by speed — hit Google Jobs with a cron every hour for fresh postings.
- **SERP mode adds context.** `mode: serp` returns richer results (featured snippets, related searches). Slower but better for market intelligence.
- **Dedupe by `apply_link`.** Google aggregates from multiple sources — same job may appear under different `via`. `apply_link` is the canonical dedupe key.
- **`ltype` filters remote-only.** Essential for distributed-team recruiters.

### FAQ, Disclaimers, Support

#### Can I filter by salary?

Not at the query level — Google doesn't consistently surface salary. Post-filter on `description` if the posting includes it.

#### Why are some jobs missing `apply_link`?

Google doesn't always expose it. When absent, the full description typically includes contact info.

#### What's the difference between `mode: rpc` and `mode: serp`?

`rpc` is Google's internal API (fast, cheap, jobs-only). `serp` is the full SERP rendering (more context, slower). Default `rpc` is what most users want.

#### Can I scrape LinkedIn directly?

This actor proxies Google's LinkedIn aggregation. For direct LinkedIn scraping, use a dedicated LinkedIn actor (outside this suite).

#### Disclaimer

This Actor scrapes public Google data only. You're responsible for compliance with Google's Terms of Service and any applicable data-protection laws (GDPR, CCPA, etc.) in your jurisdiction. ScrapeBadger does not store the scraped results — they are delivered directly to your Apify dataset.

#### Support

Something not working? Open a ticket in the **Issues** tab above — we triage within one business day. Full API reference: [docs.scrapebadger.com](https://docs.scrapebadger.com).

#### Powered by

[ScrapeBadger](https://scrapebadger.com) — Google-optimised residential proxy pool + browser-farm fallback, 99.7% uptime, unmetered bandwidth. No CAPTCHAs reach you.

# Actor input Schema

## `q` (type: `string`):

Job title or keywords. Example: <b>software engineer</b>, <b>senior react developer</b>, <b>data scientist remote</b>.

## `mode` (type: `string`):

<b>rpc</b> (default, ~1-2s): Google Careers' own batchexecute RPC — structured JSON with rich fields (qualifications, responsibilities, apply URL). Scope: Google's own openings (~3-4k roles). <b>serp</b>: public Google Jobs vertical (aggregates LinkedIn / Indeed / Built In / ZipRecruiter). Slower; supports the full filter set (job\_type, date\_posted, ltype, radius).

## `gl` (type: `string`):

ISO 3166-1 alpha-2 country code (lowercase). Example: <b>us</b>, <b>gb</b>, <b>de</b>.

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

Alias for <b>gl</b>. Optional — use this or <b>gl</b>, not both.

## `hl` (type: `string`):

ISO 639-1 language code. Example: <b>en</b>, <b>es</b>, <b>de</b>.

## `language` (type: `string`):

Alias for <b>hl</b>. Accepts locale form like <b>en-US</b>, <b>pt-BR</b>. Optional.

## `domain` (type: `string`):

Google domain to hit. Example: <b>google.com</b>, <b>google.co.uk</b>, <b>google.de</b>.

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

City / state / region for geo-targeting. Example: <b>New York, NY</b>, <b>London</b>. SERP mode only.

## `job_type` (type: `string`):

Employment type filter. SERP mode only.

## `date_posted` (type: `string`):

Restrict to postings within this window. SERP mode only.

## `ltype` (type: `string`):

Remote / hybrid / onsite filter. SERP mode only.

## `lrad` (type: `string`):

Radius in miles around <b>location</b>. Example: <b>25</b>. SERP mode only.

## `chips` (type: `string`):

Raw Google chip filter string. Example: <b>date\_posted:today</b>. Optional — overrides the structured fields above when set.

## `uds` (type: `string`):

Opaque UDS filter token copied from a Google Jobs URL. Optional.

## `uule` (type: `string`):

UULE-encoded location string for precise geo targeting. Optional.

## `max_pages` (type: `integer`):

How many pages of jobs to fetch. Each page is a separate API call (costs N credits) and is walked via Google's <b>next\_page\_token</b>. Stops early if Google signals no more pages.

## `next_page_token` (type: `string`):

Resume from a specific page by passing the <b>next\_page\_token</b> returned by a prior run. Optional.

## Actor input object example

```json
{
  "q": "software engineer",
  "mode": "rpc",
  "gl": "us",
  "hl": "en",
  "domain": "google.com",
  "job_type": "",
  "date_posted": "",
  "ltype": "",
  "max_pages": 1
}
```

# Actor output Schema

## `dataset` (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 = {
    "q": "software engineer"
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrape.badger/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 = { "q": "software engineer" }

# Run the Actor and wait for it to finish
run = client.actor("scrape.badger/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 '{
  "q": "software engineer"
}' |
apify call scrape.badger/google-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrape.badger/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/w61DG40Rd8rIDhPIn/builds/8el8wHxnCJT6d8oqW/openapi.json