Indeed Jobs Scraper — Public Listings avatar

Indeed Jobs Scraper — Public Listings

Pricing

from $2.00 / 1,000 indeed job listings

Go to Apify Store
Indeed Jobs Scraper — Public Listings

Indeed Jobs Scraper — Public Listings

Search public Indeed job listings by position, location, salary, company, job type, and posting date into structured datasets.

Pricing

from $2.00 / 1,000 indeed job listings

Rating

0.0

(0)

Developer

Crab Walker

Crab Walker

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

3

Monthly active users

15 hours ago

Last modified

Share

Indeed Public Jobs Scraper

Search public Indeed job listings by position, location, or URL. The Actor does not log in, use candidate or employer accounts, or access private data.

Indeed protects its public pages against non-browser HTTP clients. This Actor uses browser-level TLS and header impersonation with session-sticky proxy support, automatically rotating to a fresh residential session when a proxy tunnel fails. It visits each public job-detail page to return the full description, without logging into Indeed or solving CAPTCHAs.

Listings whose public detail page remains unavailable after proxy rotation are skipped, so maxItemsPerSearch counts complete records with full descriptions rather than incomplete or chargeable placeholder rows.

Input

Use the reference Actor fields position, maxItemsPerSearch, country, location, parseCompanyDetails, saveOnlyUniqueItems, and followApplyRedirects, or provide public Indeed search URLs in startUrls. The legacy aliases maxItems and maxPages are also accepted.

Output

Each row exposes the reference Indeed fields (positionName, salary, jobType, company, companyIndeedUrl, location, rating, reviewsCount, externalApplyLink, url, id, postedAt, postingDateParsed, description, and company/error fields) plus shared provenance fields.

Pricing for 70%+ margin

Profit on pay-per-event is profit = 0.8 * revenue - platformCosts, so margin = profit / revenue. For 70% margin with costs borne by the developer:

revenue >= platformCosts / 0.1 (i.e. 10x costs)

Measured cost drivers per 1,000 full-description results (FREE/BRONZE tier): residential proxy ~0.4 GB x $8 = ~$3.20, compute + transfer + writes ~$0.15. Total C ≈ $3.35 / 1,000 results.

  • Set apify-default-dataset-item to $0.04-0.05 per result ($40-50 / 1,000). At $0.05: profit = 0.8*50 - 3.35 = $36.65, margin ≈ 73%.
  • Keep platform usage costs included in the event price (predictable for users). The safest alternative is enabling "Pass platform usage costs to users" in Console monetization: margin is then fixed at 80% and the event price can be lower.
  • Set minimalMaxTotalChargeUsd to ~$0.50 so a run can cover start + first results.
  • Memory is capped (min 256 MB, max 1024 MB, default 512 MB) so a high-memory run cannot multiply compute costs without extra revenue.

Cost controls in code: charge-limit checks run before each detail fetch (no proxy burn for unbilled results), detail retries capped at 2, and includeFullDescription: false skips detail pages entirely (~10x less proxy for snippet-only runs).

Add an APIFY_API_TOKEN repository secret. The GitHub Actions workflow runs tests and publishes the Actor on pushes to main or master.