Indeed · measured · dated
Scraping Indeed: only one combination worked
Indeed sits behind Cloudflare. A plain request was refused from every source we tried, including three residential proxy networks. A headless browser from a datacenter address was refused too. The job cards arrived only when a real browser ran through a residential address, and that is the whole finding.
Latest run
- Tested
- 10 Sep 2026
- Targets
- 9real sites
- Providers
- 3+ datacenter baseline
- Baseline pass rate
- 15 / 45no proxy
Quick answer
Browser plus residential address, or nothing
Five requests per source per method to an Indeed job search page. A pass requires the real job cards in the response.
| Source | Plain requests (curl) | Headless Chromium | From | |
|---|---|---|---|---|
| No proxy (datacenter) | 0 / 5HTTP 403 | 0 / 5HTTP 403 | $0 | |
![]() | 0 / 5HTTP 403 | 4 / 5 | $6/GB | See Oxylabs pricing |
![]() | not tested | not tested | $8.4/GB | See Bright Data pricing |
![]() | 0 / 5HTTP 403 | 4 / 5 | $2/GB | See Decodo pricing |
![]() | 0 / 5HTTP 403 | 5 / 5 | $5/GB | See SOAX pricing |
Five requests per source per method against Indeed, measured 10 Sep 2026 (plain) and 10 Sep 2026 (browser). The reason shown is what the site returned.
What happened
Neither half works alone
Status 403 from the datacenter address and from all three residential networks. Cloudflare’s challenge is served as a page, and a client with no JavaScript engine can never complete it. The address type made no difference at this stage, which is why a proxy alone does not solve this target.
The same headless Chromium that succeeded through a residential proxy was refused five times out of five when it came from our hosting-company address. The challenge was offered but the result was not accepted.
The challenge resolved on its own within a few seconds and the job cards arrived. One provider passed all five attempts and two passed four of five. No CAPTCHA solving service, no stealth plugin, no fingerprint patching.
Cloudflare weighs several signals together. A trusted address without a JavaScript engine cannot pass the test; an untrusted address that passes the test is still refused. Only both together clear the bar, and that is the clearest argument in our whole test for paying for a residential proxy on top of running a browser.
If you are building this
What we would do to collect Indeed pages
- Budget for both, or do not start. A residential proxy alone will not work and a browser alone will not work. The cost is the proxy traffic plus the CPU to run browsers, and on this target that is the price of entry.
- Count the traffic, not the requests. A browser moved roughly ten times the bytes of a plain request in our runs. On per-gigabyte pricing that is the number that decides your bill, so block images, fonts and media as we did.
- Expect misses and retry through a new address. Two of the three providers passed four attempts out of five. A failed challenge is normal; treat it as a retry with a fresh exit address rather than an error.
- Give the challenge time. Our runs waited up to fifteen seconds after load for either the job cards or the challenge to resolve. A scraper that gives up after two seconds will record a block that was about to become a page.
- Watch for the silent failure. Cloudflare can return a full-size page with no job cards in it. Check for the content you need, never for status 200; that rule is why our numbers differ from comparisons that count responses.
Method
How this was measured
The same script and server as every other number on this site.
The target is an Indeed job search page, requested five times per source. Plain requests carry the headers of a current desktop Chrome and no JavaScript engine. Browser requests use a headless Chromium through the same proxy, each in a fresh browser context so no cookie or challenge result carries over, waiting up to fifteen seconds for job cards or for the challenge to resolve. No CAPTCHA solving service and no anti-detection plugins were used. The two runs were made on different days, which is stated in the table.
Providers
What the working combination costs
List prices for the providers whose addresses cleared the challenge. Full results across all nine targets are on the front page.
| Provider | Pool | Locations | Targeting | Sessions | Trial | Entry price | |
|---|---|---|---|---|---|---|---|
![]() | 100M+ | 195 countries | City · ASN | Rotating and sticky | None on self-service | $6/GBStarter 5 GB, $30/mo, cancel any time | See Oxylabs pricing |
![]() | 72M+ | 195 countries | City · ASN · ZIP | Rotating and sticky | Free trial for verified businesses | $8.4/GBPay as you go, no commitment | See Bright Data pricing |
![]() | 115M+ | 195+ locations | City · ZIP · ASN | Rotating and sticky (minutes to days) | 3-day trial, 100 MB | $2/GBPay as you go $4/GB, plans from $2/GB | See Decodo pricing |
![]() | 155M+ | 195+ locations | City · ISP | Rotating and sticky, custom length | 3-day trial, 400 MB, $1.99 | $5/GBPay as you go $5/GB, $3/GB on $200/mo plan | See SOAX pricing |
We earn a commission if you buy through the pricing links. It does not change the numbers: the test script, the target list and the raw results are public, and providers do not see results before you do.




