Geonode logo

Unlimited Indeed scraper for AI agents.

An Indeed scraper for job postings, search results, company pages, reviews and salary pages. Unlimited requests for one flat bill from $50/mo, no credits, and a blocked request is free.

Start 48-hour free trial

No card. Unlimited pages. 5 threads. Failed requests $0

Unlimited web scraper
01

Images

02

Title

  • Title
  • Condition
03

Price & bidding

  • Price
  • Bids
  • Time left
  • Watchers
04

Seller

  • Seller rating
  • Sold listings
05

Specifics & shipping

  • Item specifics
  • Shipping
  • Item location

JavaScript rendered, parsed to JSON or Markdown, and a fetch that fails after three retries is never billed

Call it on Indeed

curl -X POST "https://scraper.geonode.io/v1/extract" \
  -H "X-Api-Key: $GEONODE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://www.indeed.com/jobs?q=data+engineer&l=Austin%2C+TX",
  "formats": [
    "json",
    "markdown"
  ],
  "render_js": true,
  "proxy": {
    "country": "US"
  }
}'

You came for an Indeed scraper. The key opens everything.

100% first-pass success

you’re here

Job header: Job title, Company name, Company rating, Location, Remote / hybrid tag, Job key (jk)

Pay & job details: Salary range, Pay period, Estimated-pay flag, Job type, Shift and schedule, Benefits list

Description: Full description text, Requirements, Posted date, Apply method (Indeed Apply vs external), External apply URL, Hiring insights

Search results: Result cards, Sponsored flag, Snippet, Posted age, Total result count, Next-page start offset

Company page: Overall rating, Review count, Rating breakdown, Review title and text, Reviewer role and location, Salary by job title

One subscription, from $50 a month flat. Everything after the first line adds $0

The hard part is getting in. That's our part.

  • $50/moflat, priced by concurrency, not per request

  • 0credits, meters or per-page charges

  • $0for any Indeed request that still fails after 3 retries

  • 48 hfree trial on your own Indeed URLs

  • Cloudflare98%

  • Akamai97%

  • Imperva Incapsula97%

  • DataDome96%

  • PerimeterX / HUMAN95%

  • reCAPTCHA v395%

  • Kasada94%

  • hCaptcha93%

First-pass success by anti-bot vendor, measured by us over 30 days, so of course it flatters us. The 48-hour trial exists so you can count against your own URLs. Full benchmark

What unlimited changes for Indeed data

  • Sold-comps pricing

    Completed listings are the real price of anything. Pull them at scale and price with evidence.

  • Arbitrage sourcing

    Sweep categories for mispriced inventory continuously instead of when the credit budget allows

  • Demand research

    Bids, watchers and sell-through, across a whole category, on one flat bill

  • Collection tracking

    Every listing of the thing you care about, the moment it appears

Cheap is supposed to be the trade-off

  • Michael T.

    Switched from Bright Data. Same quality, fraction of the cost. Their wholesale model actually makes sense.

  • Kristina Halvorson

    Finally a proxy provider that actually feels built for developers

  • Edgar Weissnat

    We run multiple large-scale data collection pipelines across several regions, and proxy reliability has always been one of the biggest bottlenecks. After switching to Geonode we noticed two immediate improvements: connection stability and predictable pricing. Previously we had to constantly optimize traffic to avoid massive proxy bills. With Geonode’s wholesale pricing model we can focus on building products instead of worrying about proxy usage. Integration with our Python stack and Playwright automation was straightforward and took less than a day.

  • Gladys Paucek

    Best proxy infrastructure I've used. The MCP integration with our AI agents was seamless.

  • Gladys Paucek

    Finally something that doesn’t feel like enterprise sales software.

Pick your thread count. That's the only decision.

Nothing is metered. Plans price threads (how many requests run at once), and pages stay unlimited on every one. An Indeed page that needs an anti-bot bypass costs exactly what a plain page costs

Roughly what each plan clears in a month, by endpoint

Starter

2 threads

$50 /mo

~470K
~280K
~1.1M
~610K
~120K
~400K

Growth

5 threads

$100 /mo

Popular
~1.2M
~700K
~2.8M
~1.5M
~300K
~1M

Scale

25 threads

$400 /mo

~5.9M
~3.5M
~13.8M
~7.6M
~1.5M
~5M

Pro

100 threads

$1,250 /mo

~23.5M
~14M
~55M
~30M
~5.9M
~20M

Max

250 threads

$2,500 /mo

~59M
~35M
~137M
~76M
~15M
~50M

The 48-hour trial runs at five threads, no card. Custom terms past 250 threads.

Yeah, but...

We do not yet publish a benchmark number for www.indeed.com, so we will not quote one here. What we can describe is the defence and how the Indeed scraper handles it. Indeed sits behind Cloudflare and serves an interstitial titled Additional Verification Required to traffic it distrusts, which returns a 200 with no job in it. The Indeed scraper uses residential and ISP IPs from our own pool, renders the page so the challenge resolves the way it would in a browser, and retries before giving up. If a request still fails after three retries it is never billed, on any plan. Measure your own job and search URLs in the 48-hour trial.

Four public page types. Job postings at /viewjob?jk=, which return the title, company, location, salary block, job type, benefits, full description and whether the role uses Indeed Apply or an external apply URL. Search results at /jobs?q=&l=, where the Indeed scraper returns each card with its sponsored flag, snippet and posted age plus the start offset for the next page. Company pages at /cmp/, including the overview, reviews tab with rating breakdown and the salaries tab by job title. Each type has its own target_param, indeed_job, indeed_search, indeed_company, so the Indeed scraper applies the right parser and returns typed JSON, Markdown or raw HTML.

Yes, with a flag. Indeed shows two kinds of pay: a range the employer entered and an Estimated figure Indeed computes from similar postings. They look alike on the page, and a naive Indeed scraper merges them into one number. The Indeed scraper returns the low and high values, the pay period, the currency and an is_estimate boolean, so you can filter employer-stated pay from modelled pay. When a posting has no salary at all the field is null rather than zero. The same applies on search cards, where the Indeed scraper reads the compact salary snippet and marks it estimated when Indeed does. Country routing reads the local Indeed domain in that market's currency.

The Indeed scraper reads only what a logged-out visitor sees: job postings, search results, company overviews, reviews and salary pages. It never logs into an Indeed account, so nothing behind Employer or job-seeker dashboards, including applicant data and resumes, is reachable or promised. Indeed's terms prohibit automated access and ToS is a separate question from law; in the US, hiQ v. LinkedIn supports collecting public data, while reviews and recruiter names are personal data under GDPR and CCPA and need a lawful basis to retain. Pagination is capped by Indeed itself: an Indeed scraper search stops offering new pages after roughly the first several hundred results, so split broad queries by location or date.

No request credits and no per-page meter. Plans are priced by concurrency, which is the number of requests in flight at once, from $50 a month. Run as many requests through that concurrency as you can, around the clock, for the same bill. A request that fails after three retries is not counted against anything.

Yes. Pass a country code and the request routes through a residential IP there, so marketplaces return local prices and currency, search engines return local results, and geo-restricted pages open. City and ASN targeting are available on the residential pool where a site is sensitive to it.

Typed JSON with the field table on this page, clean Markdown for feeding an LLM context window, or raw rendered HTML if you run your own parser. For pages without a dedicated parser you can pass a JSON schema and get AI-extracted fields back in that shape.

48 hours. Your worst Indeed URLs.

Five threads, no card, and the clock starts at your first API call. If it doesn’t earn the switch, don’t switch.