Google Search API / Recruitment Data

The fastest Google Search API for recruitment data

Candidates start on Google, and whoever owns that results page gets the applications. See who ranks for every role you hire for, in every market, with responses in under one second from $1 per 1,000 requests, dropping under $0.50 at volume.

Search as a candidate in any city with one location value
Use site: operators to isolate boards, aggregators, or career pages
Blocked attempts are retried at our cost and never billed

<1s

Typical response time

$1/1K

List price, under $0.50 at volume

Charge for failed requests

195

Countries, city-level targeting

Who tracks recruitment search data

Hiring competition is visible before it shows up in headcount: it shows up in who ranks for the roles you are trying to fill.

Job boards and aggregators

Measure your visibility against rival boards for the role queries that actually bring traffic.

Talent acquisition teams

See whether your careers page or a third-party board owns searches for your own open roles.

Employer brand teams

Track what candidates find when they search your company name alongside a role.

Staffing and search firms

Spot the markets and roles where competitors are advertising hardest.

Talent intelligence analysts

Map hiring pressure by role and city from what surfaces on the results page.

Why recruitment visibility goes unmeasured

Most hiring reporting looks inward at the funnel. Three things happen before a candidate ever reaches it.

Failure 01

Aggregators own your own roles

Search a role at your own company and a third-party board often ranks above your careers page. You then pay that board for candidates who were looking for you specifically.

Paying for your own applicants

Failure 02

Hiring is intensely local

The boards that dominate in Austin are not the ones that dominate in São Paulo. A national view flattens exactly the differences that decide where to spend.

Budget spent in the wrong channels

Failure 03

Manual checking cannot cover a role set

Checking a few roles in one city is easy. Doing it for every open requisition across every market, often enough to see movement, is where the method stops.

Most requisitions unmeasured

The data a role query returns

One call to the scraper.google.search actor returns the results page a candidate in that city sees — who ranks, what each listing promises, and what Google suggests they search next.

organic_results[]

array

Ranked results for the query.

position

integer

Organic rank, excluding ads and feature blocks.

title

string

Result headline as rendered by Google.

link

string

Destination URL.

snippet

string

Description text shown under the title.

snippet_highlighted_words

array

Terms Google bolded in the snippet.

source

string

Publisher name attributed by Google.

related_searches

object

Adjacent role queries — often where an emerging title shows up first.

knowledge_graph

object

Employer panel, when the query includes a company name.

pagination

object

current, next, and other_pages for going deeper.

search_information

object

Query displayed, total results, and spelling-correction state.

metadata

object

Engine used and the stored raw page URL for auditing.

POST /api/v1/scraper/request

200 ok

# request
curl --location 'https://api.scrapeless.com/api/v1/scraper/request' \
--header 'x-api-token: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "actor": "scraper.google.search",
    "input": {
        "q": "backend engineer jobs austin",
        "location": "Austin, Texas",
        "gl": "us",
        "hl": "en"
    }
}'

# response (trimmed)
{ "organic_results": [
    { "position": 1,
      "title":   "Backend Engineer Jobs in Austin",
      "link":    "https://aggregator-a.com/austin",
      "snippet": "312 open roles updated today…",
      "source":  "Aggregator A" } ],
  "related_searches": {},
  "search_information": {
    "total_results": 1840000 },
  "metadata": { "engine": "google.search" } }

Full parameter and field reference

Watching how candidates see your company more broadly? See Brand monitoring in SERPs

Read the official product reference

How a recruitment scan works

Build your role and market list

Titles you hire for crossed with the cities you hire in. One request per pair, with location set to the market.

Isolate what you need

Use site: in q to restrict a query to a specific board or to your own careers domain, which turns a broad scan into a targeted check.

Track movement over time

Store who ranks per run. A competitor climbing for your core roles in one city is the finding; a single snapshot never shows it.

Built for job boards, talent acquisition, and employer brand teams

The fastest response in the category

A role scan is requisitions multiplied by cities, refreshed often enough to see movement. Sub-second responses make weekly tracking across a full requisition list practical rather than aspirational.

under 1s

typical vendor window

request

unblock

parse

Search as a candidate in that city

Pass a city-level location and results reflect that market. Hiring is local, and the board that dominates one metro is often absent in the next one.

Market Parameters

"location": "Austin, Texas"

"gl": "us" "hl": "en"

195 countries covered

Operators that narrow the question

The query field supports site:, inurl:, and intitle:, so a scan can isolate a single board, check only your own careers domain, or find role titles wherever they appear.

Query Operators

site:yourcompany.com/careers

intitle:"backend engineer"

inurl:/jobs/

Depth past the first page

Page with start and set volume with num, so a scan reaches the niche boards and regional aggregators that never appear at the top.

Pagination

"start": 0 | 10 | 20 …

"num": results per page

pagination.next

Plans built for requisition-wide scans

Scan cost is roles multiplied by markets multiplied by frequency, so effective cost per successful request decides how much of the requisition list you can watch. Start at $1 per 1,000 and move down the curve.

Basic

$0.00/1K

Pay as you go

No commitment. Consumption-based pricing at list rates.

Comparing recruitment search data sources

Teams measuring hiring visibility usually choose between manual checks, a general rank tracker, and querying the results page directly.

Scrapeless Google Search API

Build it in-house

Typical SERP API vendor

Typical response time

Under one second

Degrades under load

Multiple seconds

Market granularity

City-level, included

Residential IPs per market

Country-level on most plans

Query operators

site:, inurl:, intitle: supported

Build your own handling

Varies

Entry price per 1K

$1.00, under $0.50 at volume

Proxy and engineering cost

$1.00 and up

Cost of a blocked request

Never billed

Paid in bandwidth either way

Usually billed

Time to first clean dataset

Under an hour

4–8 weeks

Days

Start measuring recruitment visibility on the fastest, lowest-cost API

Sub-second results from any market, from $1 per 1,000 requests, dropping under $0.50 at volume, with failed requests never billed. See the full endpoint reference, parameter list, and pricing.

View the product page

Drops into the stack you already run

Official SDKs and verified nodes, so a scheduled rank pull is a configuration task rather than a build.

Python SDK

Node.js SDK

Go SDK

n8n verified node

Make

Pipedream

Activepieces

Dify

MCP server

Webhooks

Need implementation details? View product details or open the Google Search API docs for the full parameter list, response schema, and SDK examples.

Choose the search workflow your team needs

Explore focused solutions for search visibility, AI retrieval, commerce intelligence, research and monitoring. Each use case connects Google Search API results to a clear business outcome.

SEO Rank Monitoring

Measure domain visibility, ranking pages and SERP feature presence across keyword groups, markets and devices.

Local SEO & Rankings

Compare local rankings, business listings, Maps visibility and review signals across cities, regions and service areas.

AI SEO & GEO Visibility

Monitor brand mentions, citations and source visibility across AI-generated search experiences and target topics.

Product & Market Research

Study demand signals, alternatives, category presence and competing offers through structured search results.

AI Models & RAG

Give LLMs, agents and RAG pipelines current, attributable search context for grounding and retrieval workflows.

Keyword Rank Tracking

Track exact keyword positions and movement over time by location, language, device and result type.

Shopping Price Monitoring

Compare public Google Shopping prices, merchants, ratings and product visibility for selected categories.

News & Media Monitoring

Follow headlines, publishers, emerging stories and shifts in public narratives across relevant queries.

Travel Data

Structure Google Flights and Hotels results for route, stay, destination and travel-market research.

You are here

Recruitment Data

Collect Google Jobs results to monitor roles, employers, locations and labor-market demand.

Ad Verification

Verify PPC and Ads visibility, placement and competitive messaging across target queries and markets.

Academic Research

Organize Google Scholar results, authors and cited sources for academic and evidence-based research.

Trend Analysis

Use Google Trends signals to compare changing interest across topics, time periods and markets.

Image Search

Use Google Lens and Images results to discover visual matches, sources and related content.

Brand Monitoring

Track where a brand appears across organic results, news, shopping and other SERP surfaces.

Need Google Search API specifications and pricing?

Review supported Google API categories, structured response examples, integration steps and pricing on the Product page.

Questions teams ask before they buy

Which is the cheapest API for recruitment search data?

Compare effective cost per successful request rather than list price. Scrapeless lists at $1 per 1,000 and drops under $0.50 at volume, and blocked attempts are never billed.

Which search API is fastest for role scans?

Scrapeless returns most requests in under one second, so a scan across a full requisition list and several cities finishes inside a working session.

Can I check results as a candidate in a specific city?

Yes. Pass a city, metro, or postal code in the location parameter. Hiring is local, and the boards that dominate one metro are often absent in another.

Can I restrict a scan to one job board or to our careers page?

Yes. The query field supports advanced operators including site:, inurl:, and intitle:, so a request can target a single domain or a specific title pattern.

Can I scan past the first page?

Yes. Use start to paginate and num to control results per request, which is how a scan reaches niche and regional boards.

What happens when Google changes the results layout?

Parsing is maintained on our side and the response schema stays stable. New blocks are added as new fields rather than by renaming existing ones.

Do I still need my own proxies?

No. IP sourcing, rotation, fingerprinting, and CAPTCHA handling sit behind the endpoint, across 195 countries and regions.

Scanning a full requisition list? Get a custom rate.

A solutions engineer will scope your roles, markets, and scan frequency, then send back custom pricing — usually within one business day. Smaller lists can start free today.

Try for free

Explore workflow