Google Jobs Vertical: Pay Bands, Highlights & Apply Routes avatar

Google Jobs Vertical: Pay Bands, Highlights & Apply Routes

Pricing

from $0.49 / 1,000 results

Go to Apify Store
Google Jobs Vertical: Pay Bands, Highlights & Apply Routes

Google Jobs Vertical: Pay Bands, Highlights & Apply Routes

Search Google's Jobs vertical by keyword, place, country and language. Export parsed salary bands, employer logos, remote and no-degree flags, Google's qualification/responsibility/benefit highlights, and every apply option with its real URL.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

Xyrelith Data

Xyrelith Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

an hour ago

Last modified

Features

Limited permissions

Share

Search Google's Jobs tab by role, place, country and language, then receive one clean row per listing with the pay band pulled apart, the employer's logo, Google's own qualification/responsibility/benefit lists, and every place the job can be applied to.

Google's Jobs view is an aggregator: a single search can surface the same opening from LinkedIn, Indeed, Glassdoor, ZipRecruiter, a company career site and several smaller boards. This actor turns that view into structured records instead of a page of cards.

What it does

  • Searches the Google Jobs vertical (udm=8) with a keyword and one or more places.
  • Targets any Google country market (gl) and interface language (hl).
  • Applies Google's filter chips: date posted, job type, remote/work-from-home, no-degree-mentioned, and employer.
  • Saves the salary exactly as Google shows it and also parses minimum, maximum, currency and pay period.
  • Collects every apply option on the job, including the provider name, the real destination URL, and whether Google marks it as a direct application.
  • Splits Google's "Job highlights" into Qualifications, Responsibilities and Benefits lists, including the extra items Google hides behind a "more items" toggle.
  • Fans out across Google's own filter slices to go past the roughly ten listings a single Jobs page returns, then de-duplicates by Google's job ID.
  • Has a URL mode for feeding in Google Jobs search links or job share links you already have.

Modes

Search by keyword + location — the default. Each query is combined with each location. Leave locations empty to search the whole country selected under Google country. Google needs a place to open the Jobs view, so the country name is used as the location when none is supplied.

Parse Google Jobs URLs — paste search links (...&udm=8... or ...&ibp=htl;jobs...) or a job's share link (...&htidocid=...). Search links keep their own filters; a share link returns that one listing.

Input

FieldTypeDefaultWhat it does
modedropdownsearchSearch by keyword, or parse Google Jobs URLs.
searchQuerieslist– (UI prefill: software engineer)Job titles, skills or phrases.
locationslist– (UI prefill: Austin, TX)Cities, regions or countries added as "jobs near ...".
gldropdownusGoogle country market.
hldropdownauto (same as country)Interface language. Keep auto outside English markets; forcing English often returns no jobs.
radiusKmnumber0Best-effort radius hint in the search phrase.
datePosteddropdownanyPast 24 hours, 3 days, week or month.
jobTypedropdownanyFull-time, part-time, contractor, internship or temporary.
remoteOnlybooleanfalseKeep jobs Google tags as remote/work from home.
noDegreeOnlybooleanfalseKeep jobs with no degree requirement mentioned.
companytextemptyEmployer name to search and verify.
maxItemsnumber50Row cap across the whole run.
fanOutbooleantrueRepeat the search across filter slices to exceed ten jobs per query.
maxSearchesPerQuerynumber10Cap on filter slices per query.
includeDescriptionbooleantrueSave the full description.
includeHighlightsbooleantrueSave the three highlight lists.
includeErrorRowsbooleanfalseSave a diagnostic row when a search finds no jobs.
onlyNewJobsbooleanfalseScheduled runs: skip job IDs seen before.
stateNametextdefaultSeparate seen-jobs memory per alert.
startUrlslistemptyGoogle Jobs URLs used by URL mode.

Output

Every row is a job listing. Empty fields are omitted rather than written as null. With includeErrorRows, a run that finds no jobs at all also saves a diagnostic row with recordType: "error" and an error reason.

Identity and context

  • jobId — Google's stable job ID (the htidocid value).
  • title, employerName, employerLogoUrl, location, otherLocationsCount, source.
  • shareLink — the Google share link for the listing.
  • sourceUrl — canonical Google URL for the record (the share link, or the search page).
  • position — order on the page.
  • searchQuery, searchLocation, searchFilter, searchUrl, country, language.
  • recordType, scrapedAt.

Pay and timing

  • salary — exactly as Google shows it.
  • salaryMin, salaryMax — parsed numbers.
  • salaryCurrency, salaryCurrencyCode, salaryPeriod — symbol, ISO code and hour/day/week/month/year.
  • salarySource — tag when the pay came from Google's salary chip, description when it was parsed from a pay sentence in the description.
  • postedAgo — Google's own age string.
  • postedAt — computed ISO date.
  • postedDaysAgo — numeric age.
  • postedAtApproximate — true when Google says "30+ days ago".

Work arrangement

  • remote — true when Google tags the job remote/work-from-home or the location is Anywhere/Remote.
  • workFromHome — true specifically for Google's "Work from home" tag.
  • remoteEvidence — the signals behind the remote flag.
  • employmentType and employmentTypes — as shown, plus a normalised list.
  • benefits — Google's benefit tag chips.
  • noDegreeMentioned and noDegreeTag — whether no degree requirement is mentioned, and whether Google itself labelled it.

Description and highlights

  • description — full text, with paragraph breaks preserved.
  • descriptionIsPreview — true when Google only exposes a short preview.
  • jobHighlights — object with qualifications, responsibilities and benefits lists.

Apply options

  • applyLinks — every option as {site, url, direct, resolved, titleMatch}. resolved is true when the real destination URL is present; titleMatch is true/false when the URL slug can be checked against the job title, or omitted for ID-only URLs.
  • applyUrl — the first option Google lists whose URL does not clearly name a different job, otherwise the first option.
  • directApplyUrl — first option Google marks as "Apply directly on ...".
  • applyOptionsCount — number of apply options.
  • isNew — present when onlyNewJobs is on.

How the job cap is handled

Google's Jobs view does not expose numbered pages: asking for page 2 returns no listings. It shows roughly ten jobs per search. To reach more, the actor repeats the same search with Google's own filter phrases (dates, job types, remote, no degree) and merges the results by jobId. The base search always runs first; when maxItems is ten or less, only the base runs, keeping small jobs cheap. Set fanOut to false if you want exactly one request per query.

Salary parsing

Pay text is parsed, not guessed. £50,000 - £60,000 per annum becomes {salaryMin: 50000, salaryMax: 60000, salaryCurrency: "£", salaryCurrencyCode: "GBP", salaryPeriod: "year"}. Hourly, daily, weekly, monthly and yearly forms are recognised, along with K, M, B, +, from, up to, and grouped numbers such as ₹12,00,000. When Google's salary chip is absent, the actor also checks pay sentences in the full description (for example "The pay range is $120,000 - $150,000 a year") before leaving the field empty.

Google's apply buttons point at redirect URLs, but the real destination is already present in the page data. This actor reads those destinations directly, removes Google Jobs attribution parameters, and keeps the provider name, direct-apply flag and a best-effort titleMatch check. Some jobs carry links from several boards; all of them are returned, and applyUrl skips a link whose slug clearly names a different job.

Examples

Software engineer jobs in Austin, last week

{
"searchQueries": ["software engineer"],
"locations": ["Austin, TX"],
"datePosted": "pastWeek",
"maxItems": 50
}

Remote nursing contracts in Houston

{
"searchQueries": ["registered nurse"],
"locations": ["Houston, TX"],
"jobType": "contractor",
"remoteOnly": true,
"maxItems": 30
}

UK market, no degree mentioned, top 20

{
"searchQueries": ["data analyst"],
"locations": ["London"],
"gl": "gb",
"hl": "en",
"noDegreeOnly": true,
"maxItems": 20
}

Parse a saved Google Jobs link

{
"mode": "byUrl",
"startUrls": ["https://www.google.com/search?q=python+developer+jobs+near+Berlin&udm=8&hl=en&gl=de"]
}

Use cases

  • Hiring-market dashboards: open roles by title, place, employer and pay band.
  • Compensation research: compare advertised ranges across markets.
  • Lead lists: find employers hiring for a niche and reach the posting directly.
  • Job-alert automation: scheduled runs with onlyNewJobs and stateName.
  • Board attribution: see which boards Google is aggregating for a role.

FAQ and limits

Does this need a login or my own proxy? No. It runs with no credentials, cookies or proxy configuration from you; the actor selects the right access route itself.

Why are there about ten jobs from one search? That is Google's Jobs view. The actor fans out across Google's filter chips and de-duplicates to find more, and says so in the run log. It never invents a page 2.

Why do some rows have no salary? Many employers do not publish pay. Google only shows a salary when the source provides one; the actor never estimates or invents an amount. It does read a pay sentence from the description when Google has no salary chip.

Why do some rows have no highlights? Google generates highlight blocks mainly for US listings and not for every job. When a block is absent it is omitted.

Why is the location sometimes "Anywhere"? Google uses that label for fully remote listings. It is treated as a remote signal and preserved as shown.

Does it work in every country? It works in the markets where Google's Jobs tab is available. Some countries or queries return Google's standard web results instead of the Jobs view; the actor reports that in the status message. Google Jobs is not available in South Korea or mainland China, and several other markets (for example Australia, New Zealand, Ireland, Poland and the Nordics) return no listings. Use the local language setting (auto) outside English-speaking markets.

Why does an English search in Germany return nothing? Forcing English in a non-English market is a known Google Jobs zero-results behaviour. Leave hl on auto so Google uses the market's own language.

What about the employer logo? Google-hosted employer logos are returned when the listing has one. Listings without a logo simply omit the field.

Is the posted date exact? It is computed from the age Google displays, so treat it as an approximation, especially for "30+ days ago".

Does the actor need a browser? No. It reads Google's rendered Jobs page over HTTP, which keeps runs fast and inexpensive.

Data source

Public Google Jobs search result pages. This actor is independent and is not affiliated with, endorsed by, or sponsored by Google.