Google Jobs Scraper

Google Jobs Scraper: listings, employers and the boards they came from

Search the public Google Jobs results and get one row per listing: the job title, the employer, the location, which board Google picked it up from, Google's own stable job ID, the employment type and a link to the Google listing page.

The awkward part, stated plainly because it decides whether this fits your project. Google does not put the apply link in the results it serves, so applyUrl comes back null. What you get instead is applyOptions, the board names Google lists, and googleJobUrl, the listing page that carries the working apply buttons. salary and description come back null on that same path.

💼 What Google Jobs Scraper does

It runs your keywords against Google's jobs results for one country and language, reads the listing cards, and writes a row each.

The identity fields. jobId is Google's own htidocid, so the same listing keeps the same ID between runs and deduping is easy. When Google does not give one, a stable hash of the title, employer, location and link is used instead.

The routing fields. source is the board Google credits, like LinkedIn or Indeed. applyOptions lists every board Google offers for that listing. googleJobUrl opens the listing where the apply buttons live.

Duplicates are removed by Google's ID within a run, so the same posting surfacing twice arrives once.

📥 What you give it

{
  "query": "software engineer",
  "location": "Toronto",
  "country": "CA",
  "maxItems": 25,
  "maxScrolls": 3,
  "deadlineSeconds": 90
}

Set country to match your location. This is the one mistake that reliably returns nothing. Asking for Berlin while country is still US comes back empty; Berlin with country: "DE" returns jobs. Change both together.

deadlineSeconds bounds the fetching, not the whole run. A run can take longer than the number you set, because the steps that follow a slow fetch are not inside that budget.

📤 What you get back

A real row from a recent run, with the long Google link cut short:

{
  "ok": true,
  "jobId": "kqGSSHMeuPf_Dy4XAAAAAA==",
  "title": "Software Engineer - E3",
  "company": "Lockheed Martin",
  "location": "Longmont, CO",
  "source": "LinkedIn",
  "applyUrl": null,
  "sourceUrl": null,
  "datePosted": "3 days ago",
  "salary": null,
  "description": null,
  "employmentType": "Full-time",
  "query": "software engineer",
  "searchLocation": null,
  "country": "US",
  "googleJobUrl": "https://www.google.com/search?ibp=htl;jobs&q=software+engineer&htidocid=kqGSSHMeuPf_Dy4XAAAAAA%3D%3D&hl=en-US...",
  "applyOptions": ["LinkedIn", "BeBee"]
}

🧾 Reading the output

An empty query writes the sample row and stops, so you can see the shape before spending anything.

The Overview table shows applyUrl, which is always empty, and hides googleJobUrl, applyOptions and employmentType, which are not. Read the dataset as JSON or export it.

▶️ How to run it

1. Open Google Jobs Scraper and click Try for free. 2. Put your keywords into Job keywords, replacing the example. 3. Type a Location, then set Google country to that country's code. Both, every time. 4. Set Maximum jobs, then click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$1.50 per 1,000 jobs, which is $0.0015 a row. The same rate on every Apify plan, no volume tiers.

A job is charged only once a complete row has been written. maxItems caps the rows, so it also caps what a run can bill.

Not charged as jobs: the sample row, every diagnostic row, duplicates removed within a run, and a search that comes back with nothing.

💡 What people use it for

• Watching a job title in one city daily and alerting on new jobId values.
• Seeing which boards a company posts through, by counting source and applyOptions across a role.
• Building a picture of hiring in a market, by running the same keywords against several country

codes.

• Feeding titles, employers and locations into a CRM, using googleJobUrl as the link a human opens.

🚧 What it does not do

• No apply links. applyUrl and sourceUrl are null. Use applyOptions for the board names

and googleJobUrl for the page with the working buttons.

• No salary, no description. Both come back null on this path, even where Google shows them.
• datePosted is relative text, like 2 days ago. Convert it against the run time if you need a

date.

• Expect roughly ten listings from one search. The 100 ceiling is a limit, not a promise, and

maxScrolls asks Google for more without guaranteeing it.

• Australia and Ireland come back empty right now. Confirmed working today: US, GB, DE,

FR, ES, CA. Try one small search before planning a large run against anywhere else.

• A listing with no employer name is skipped, quietly, because a row without a company is not

much use.

• deadlineSeconds does not bound the whole run, only the fetching inside it.
• One search per run. Use a schedule or several runs for a list of titles.

🧭 Which Google scraper do you need?

❓ Questions people ask

Do I need a Google API key or a job board account? No. These are public search results.

Why is applyUrl empty? Because Google does not put it in the results it serves. Open googleJobUrl and the apply buttons are there.

Why did my search return nothing? Nine times out of ten, country did not match location. Set both to the same place and try again.

Can I filter by salary or date? Not in the input. datePosted comes back as Google's relative wording and salary is not populated, so neither is something you can filter on here.

Can I schedule it? Yes. jobId is stable between runs, so diffing yesterday against today gives you the new postings.

Is scraping Google Jobs legal? These are public listings. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the keywords, the location, the country and the run ID. The errorCode on the diagnostic row usually names the problem on its own.