Home › Guides › Indeed Jobs Scraper

Indeed jobs with structured salary and employer rating, by keyword and location

Indeed publishes two things company career sites usually don't: a salary estimate or range and an employer rating. The Indeed Jobs Scraper reads Indeed's own search payload (not fragile HTML) and returns clean rows: the salary as structured numbers (min, max, period, currency), the employer star rating and review count, the full description (measured median ~3,700 characters), benefits, location, posting date, employment type and a direct link. No login. Across 23 country sites.

Who it's for

• Salary-benchmarking teams building pay bands by role and city.
• Sales and competitive-intelligence teams scoring hiring intent, with each employer's rating.
• Job boards and LLM pipelines needing full descriptions at scale.
• Recruiters tracking who's hiring for a function right now in a market.

What you get

A one-sided range returns salaryMax: null (never Indeed's internal -1); no employer rating means null, not a misleading 0. Descriptions came back 47 of 47 in measurement.

How coverage works

Indeed hides deep pagination behind a login — page 2 of any search redirects to its sign-in screen (measured 2026-10-20 with a real browser). The Actor therefore does not page: each keyword × location pair returns up to ~45 postings, and coverage grows by adding more pairs. Want 1,000 nursing jobs in Texas? Give 25 city lines instead of one state line. No Actor can give you Indeed's full result set without an account, and this one won't pretend otherwise.

Input

{ "queries": ["registered nurse"], "locations": ["Houston, TX", "Austin, TX", "Dallas, TX"], "withDescription": true, "postedWithinDays": "7" }

Honest limits

• About 45 postings per keyword × location — Indeed's login wall; coverage comes from slicing, not paging.
• Salary isn't on every listing (40–83% depending on the query); with minSalary set, postings without a published salary are skipped so a filter never passes rows it couldn't check.
• No validThrough — its only source is the login-walled posting page; a field is dropped rather than shipped empty.
• Indeed refuses plain and datacenter requests — the default Apify Unblocker proxy gets through and should stay; blocked pages are never charged.

Pricing

Pay per event: $0.005 per keyword × location search that delivered rows, $0.002 per delivered posting, and $0.004 more only when a full description is returned. A list-only run is $0.002 a posting; with descriptions, $0.006. Blocked pages, empty searches, rows without a description and filtered-out postings are free. Current prices are on the actor's Pricing tab on Apify.

Related

For every open role across seven ATS platforms in one query use the Job Postings Database; for companies hiring on specific ATSs, the BambooHR Careers Scraper and the Workable Job Board Scraper; and for Google's aggregated panel, the Google Jobs Scraper.

Frequently asked questions

Why do I only get about 45 postings per keyword and location?

Indeed hides deeper pages behind a login — page 2 of a search redirects to its sign-in screen (measured 2026-10-20 with a real browser). The Actor does not page; coverage grows by slicing — more keywords, more cities, narrower postedWithinDays windows — not by raising maxItems.

Do I need an Indeed account?

No. The Actor never logs in and never asks you for credentials; it reads Indeed's own search payload through Apify's Unblocker proxy.

Why is salaryMax sometimes null when salaryText has a number?

"From $50 an hour" and "Up to $120,000 a year" are one-sided. Indeed marks the missing end with -1 internally; the Actor returns null instead of a nonsense value. A salary is published on 40 to 83% of listings depending on the query.

Why is companyRating null for some employers?

Indeed sends 0 when an employer has no rating yet; a zero would read as a one-star employer, so the Actor returns null.

How are the descriptions fetched — isn't that slow?

The Actor asks Indeed's own bulk description endpoint for every job key of a slice at once (measured 47 keys in a single request, 1.4 seconds), so turning descriptions on costs seconds, not a page per posting, and needs no login.

Using the data lawfully

The Actor reads only publicly visible job postings — no login, no candidate data. Public-data scraping is broadly lawful, but a site's terms are a separate matter: Indeed's terms restrict automated collection, so review your use case, keep volumes reasonable, and don't republish Indeed's content as your own. Indeed is a trademark of Indeed, Inc.; this Actor is not affiliated with it.