Indeed Job Scraper — titles, companies, salaries

The Indeed Job Scraper collects job postings from Indeed search results. Give it search terms and a location, and it returns Indeed's own result set for each search: job title, company, location, the posting's stated salary, employer rating and posting date.

To scrape Indeed job listings, put one or more search terms in queries, optionally a location, and pick a country — us, uk, ca, au or de. No Indeed account, login or cookies are used; this Actor reads what a logged-out visitor sees. Around 39 jobs per search, across five countries.

What it returns

Field	Type	Notes
jobKey	string	Indeed's own job ID — stable, use it to de-duplicate
title	string
company	string
location	string	Includes the postcode where Indeed shows one
salary	string	The posting's stated pay, e.g. "$120,000 - $140,000 a year" — null when the posting does not state one
companyRating	number	Indeed employer rating out of 5
companyReviewCount	number
postedAt	string	ISO 8601 timestamp
jobUrl	string	Direct link to the posting
query, country, searchLocation, sourceUrl, collectedAt	string	Provenance for every row

Input

{ "queries": ["software engineer", "data analyst"], "location": "Austin, TX", "country": "us" }

Field	Description
queries	Search terms. Required, up to 50. Duplicates collapse to one fetch.
location	Optional location filter, e.g. "Austin, TX".
country	us (default), uk, ca, au or de.
maxItems	Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below.
concurrency	Searches run in parallel. Default 3.

Use cases

• Talent-market and compensation research across roles and cities
• Competitor hiring signals — who is growing which team
• Filling an ATS or job board with live Indeed postings
• Recruiting lead lists by role, employer or location
• Tracking Indeed postings over time by re-running on a schedule

Reliability

Measured across 30 distinct Indeed job searches in one run: 29/30 searches succeeded, 1,132 jobs collected, every schema field populated.

The salary field is the Indeed posting's own stated pay. It is deliberately not inferred from Indeed's estimated-salary panel, which sits beside the results and describes the market rather than the job — so salary is null when the employer did not state one, rather than confidently wrong.

An Indeed search that cannot be read is recorded in the run's SUMMARY under failures, and a run where every search failed exits with an error.

Frequently asked questions

Do I need an Indeed account or API key? No. The Indeed Job Scraper uses no account, login, cookies or API key — only public Indeed search pages are read.

Which countries does the Indeed Job Scraper support? Five: United States (us), United Kingdom (uk), Canada (ca), Australia (au) and Germany (de), selected with the country field. One run searches one country.

Is the Indeed salary real or estimated? Real — salary is the posting's stated pay, and null when the posting gives none. Indeed's own salary estimate is never substituted.

How many Indeed jobs does one search return? Around 39, which is what one Indeed results page carries. Ten search terms therefore return roughly 390 jobs.

How do I de-duplicate Indeed jobs across runs? Use jobKey, Indeed's stable job identifier, which does not change between runs for the same posting.

Can I get the full Indeed job description? No. This Actor returns the fields Indeed exposes on the search results page; it does not open each posting. Follow jobUrl for the full description.

What happens on a free Apify plan? The run stops at 250 requests and 250 results and reports that it hit the limit. Any paid plan runs the full input.

Limitations

The Indeed Job Scraper reads one results page per search, so it collects the first page rather than paginating a whole market; run several narrower queries to widen coverage. Full job descriptions, application counts and recruiter contacts are out of scope.

Free plan limit

Runs started from an Apify free plan stop at 250 requests and 250 results, and the run reports that it reached the limit. Any paid plan runs the full input and maxItems you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not cover for free-plan runs. It binds on requests as well as results so that a large input list cannot spend those fetches for rows the run will not return.