# Indeed Proxies: 1,026 Words, First Request

> We measured Indeed through residential proxies: plain HTTP with a browser TLS fingerprint returns 2,394 words; rendering costs 1.77x the bytes for 683 words.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Indeed Proxies: 1,026 Words, First Request

# Indeed Proxies: 1,026 Words, First Request

Social proxiesSep 28, 2026·10 min read·By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

What the Indeed home page costs to read, measured on 28 September 2026: 601,347 bytes of plain HTTP HTML with a browser TLS fingerprint yield 2,394 words in 9.4 seconds, 1,066,178 bytes of rendered page yield 683 words in 52 seconds, and the jobs collector returns 10 listings with parsed salary ranges in 7.3 seconds

On this page [The keyword has no demand, the scraper does](/blog/indeed-proxies/#the-keyword-has-no-demand-the-scraper-does) [Plain HTTP with a browser fingerprint gets the whole home page](/blog/indeed-proxies/#plain-http-with-a-browser-fingerprint-gets-the-whole-home-pa) [The exit country picks the site, not the language](/blog/indeed-proxies/#the-exit-country-picks-the-site-not-the-language) [Ten listings with salaries as numbers in 7.3 seconds](/blog/indeed-proxies/#ten-listings-with-salaries-as-numbers-in-7-3-seconds) [Indeed's robots.txt is a three-tier policy](/blog/indeed-proxies/#indeed-s-robots-txt-is-a-three-tier-policy) [Cost per thousand pages](/blog/indeed-proxies/#cost-per-thousand-pages) [Where we stop](/blog/indeed-proxies/#where-we-stop) [The setting that works on Indeed](/blog/indeed-proxies/#the-setting-that-works-on-indeed)

Indeed is the target where the plain request wins and the browser loses. On 26 September 2026 the Indeed home page answered a plain HTTP client through a US residential exit with 1,026 words on the first request; on 28 September the same fetch, sent with a browser TLS fingerprint, returned 200 OK, 601,347 bytes and 2,394 words in 9.4 seconds. Rendering the page in a real browser cost 1,066,178 bytes and 52 seconds for 683 words. From a UK exit the same URL became uk.indeed.com. The setting is residential, plain HTTP with a browser fingerprint, country pinned to the market, and the jobs collector when you want salaries as numbers: ten listings in 7.3 seconds.

## The keyword has no demand, the scraper does

Google returns no autocomplete at all for "indeed proxies" or "proxies for indeed", and the first page for the head term is Indeed describing itself: five of ten results are Indeed search pages for jobs with the word proxy in the title, 4,653 of them. The rest is a Reddit thread from someone whose personal Indeed scraper stopped working, a scraper-comparison listicle, two vendor guides and a 2023 post about enhancing your job search. Nothing on that page measures what Indeed returns to a request.

The demand is one word over. "Indeed scraper" autocompletes to github, apify, extension, python, api, reddit, chrome extension, free and n8n; "scrape indeed" to job postings, jobs, python and, tellingly, "how often does indeed scrape jobs", because Indeed is itself an aggregator that crawls employer sites. Those searchers want listings with salaries in a table for labour-market analytics, wage tracking and recruiting research. That is the job this post measures.

## Plain HTTP with a browser fingerprint gets the whole home page

We fetched `indeed.com` from a United States residential exit three ways: as a pure HTTP client through our [SEO audit](https://quanticdata.io/seo-audit/), as a plain HTTP client that presents a real Firefox TLS fingerprint, and rendered in a browser.

| Fetch | Status | Bytes | Words | Time | Canonical |
| --- | --- | --- | --- | --- | --- |
| Plain HTTP, 26 September, first request | 200 | n/a | 1,026 | n/a | indeed.com |
| Plain HTTP, browser TLS fingerprint, 28 September | 200 | 601,347 | 2,394 | 9.4 s | indeed.com |
| Rendered in a browser, 28 September | 200 | 1,066,178 | 683 | 52.1 s | indeed.com |
| Jobs collector, "data engineer", New York | done | n/a | 10 listings | 7.3 s | n/a |

Two numbers carry the whole decision. The plain fetch returns 3.5 times the words of the rendered one, in a fifth of the time, for 56 percent of the bytes. Indeed server-renders its search interface, popular categories, the salary and company links and the footer; the browser then replaces most of that with an application shell and a search box. The rendered word count is not what a job seeker sees, it is what the shell had painted when the page settled, and it is a third of the HTML you already had.

The thing that decides whether the plain fetch works is the TLS handshake, not the IP. Indeed decides at the handshake which client it serves the page to. The same residential exit that receives 19 words when it presents a generic client receives 601,347 bytes and 2,394 words when it presents a Firefox fingerprint. Our [web scraping API](https://quanticdata.io/web-scraping-api/) does that by default; if you run your own client, use a TLS library that impersonates a current browser, or you will spend your residential bandwidth on 19-word responses.

## The exit country picks the site, not the language

We ran the identical audit through a United Kingdom residential exit. Indeed did not localise the page; it redirected it. `indeed.com` became `uk.indeed.com/?r=us`, canonical `https://uk.indeed.com/`, 216 words with and without JavaScript, a WebSite JSON-LD block, and a meta description promising "CVs" where the US one promises "resumes".

| Exit | Final URL | Words, no JavaScript | Words, rendered | Description says |
| --- | --- | --- | --- | --- |
| United States | www.indeed.com | 2,394 | 683 | resumes |
| United Kingdom | uk.indeed.com/?r=us | 216 | 216 | CVs |

Indeed runs a separate site per country, with its own listings, salary formats and currency, and the exit country decides which one you land on. A pool that rotates across countries will silently mix US dollar listings from indeed.com with pound listings from uk.indeed.com and Indian rupee listings from in.indeed.com, and the `?r=us` parameter in the redirect is the only trace that the request started somewhere else. Pin the country to the market you are measuring, and if you want several markets, run them as several jobs with several exits. The collector takes the same decision as an input: its `country` field picks the local site and the proxy exit together.

## Ten listings with salaries as numbers in 7.3 seconds

We ran the [Indeed jobs collector](https://quanticdata.io/collectors/indeed-jobs-api/) once, query "data engineer", location "New York", country US, capped at ten. It returned ten listings in 7.3 seconds, each with title, company, location, posting age, remote flag, snippet, the raw salary string and, parsed from it, `salary_min`, `salary_max` and `salary_period`, plus the company's Indeed rating and review count and whether the listing was sponsored.

Three things in those ten rows matter more than the fact that it worked. Three of the ten were sponsored, and the collector flags them; if you are measuring wage levels, sponsored rows are paid placement, not a sample of the market. Salaries came back as ranges from $80,000 to $275,000 a year, and one was a single figure, $128,294, which the collector returns with min equal to max rather than as a missing range. And the company rating field was 0 with 0 reviews for four of the ten, which is a company with no Indeed reviews, not a company rated zero; a pipeline that averages that column without checking the count will invent a bad employer.

For the same role on other boards, the [LinkedIn jobs collector](https://quanticdata.io/collectors/linkedin-jobs-api/) and the [Google Jobs collector](https://quanticdata.io/collectors/google-jobs-api/) take the same query and location shape, so a three-source salary comparison is three calls with one input.

## Indeed's robots.txt is a three-tier policy

`indeed.com/robots.txt` is 13,695 bytes and unusually explicit about who is who. Generic bots are allowed in, with pagination permitted only up to `start=90`, ten pages of results, and the radius, alert and RSS parameters disallowed. A second block lists the retrieval and grounding agents by name, ChatGPT-User, PerplexityBot, Claude-User, OAI-SearchBot, Google-Extended, and gives them the same access as Googlebot. A third block, headed "Rules for Foundational (Training) bots", names GPTBot, ClaudeBot, CCBot, Bytespider, DeepSeekBot, GrokBot and Diffbot and disallows them from `/jobs`, `/viewjob`, `/cmp/`, `/q-` and `/l-`: every listing and every company page. A fourth block fully disallows Scrapy by name, alongside legacy crawlers.

That is the clearest statement of a platform's position we have read this year: search engines and answer engines may index and cite listings, training crawlers may not read them, and a client that announces itself as a scraping framework is refused at the door. Our [AI crawler user-agent list](https://quanticdata.io/blog/ai-crawler-user-agent-list/) shows how the same names are treated elsewhere. And the Terms of Service back the file: the Site Rules say do not access the site through any means other than the public interfaces Indeed provides, do not access any data by automated means without permission, and, in the section on AI connectors, that the prohibitions against scraping, bots and other automated activity remain in full effect.

So be accurate about what a proxied fetch is. Indeed publishes its listings to anyone with a browser, and a residential exit with a browser fingerprint reads what a browser reads; that is a technical fact, and every number here came from one. Indeed's terms say that automated collection needs permission; that is a contractual fact, and the sanctioned route is the partner programme at docs.indeed.com, whose GraphQL APIs manage job postings, candidates and employers for integrators and whose Publisher JavaScript plugin puts Indeed search on your own site. The two facts do not line up, and no proxy makes them.

## Cost per thousand pages

Prices from our [pricing page](https://quanticdata.io/pricing/): residential Basic $0.80/GB, the [web scraping API](https://quanticdata.io/web-scraping-api/) from $0.0002 per page ($0.001 rendered), the jobs collector $0.001 per delivered listing. A gigabyte is counted as 10^9 bytes.

| Approach | Bytes per page | Pages per GB | Cost per 1,000 pages | What you get |
| --- | --- | --- | --- | --- |
| Plain HTTP, browser TLS, residential Basic | 601,347 | 1,663 | $0.48 | 2,394 words, full server-rendered page |
| Rendered, residential Basic | 1,066,178 | 938 | $0.85 | 683 words, the application shell |
| Web scraping API, plain fetch | n/a | n/a | $0.20 | Markdown or HTML, browser fingerprint included, failures never billed |
| Jobs collector | n/a | n/a | $1.00 | 1,000 listings with parsed salary min, max and period |

Rendering costs 1.77 times the bytes and 5.5 times the time for 29 percent of the words. That is the sentence to put in front of anyone who says a job board needs a headless browser. Byte figures are decoded bodies and exclude TLS overhead. The collector row costs twice the raw page and returns the thing the raw page does not: a salary as two integers and a period, which is what a wage-tracking pipeline actually stores. A search results page holds a fixed number of listings; the collector bills per listing delivered, so a run that returns fewer rows costs less, and a run that returns none costs nothing.

## Where we stop

Everything above is about public listings and public company pages: what Indeed serves any visitor, for labour-market research, wage tracking, aggregation you have permission for, and checking how a posting appears in another market. It does not cover accounts. We will not help with automating applications, creating multiple accounts, mass-messaging candidates or scraping the resume database; Indeed's Site Rules forbid fake accounts and automated account creation, and its Smart Sourcing terms say scraping the resume database ends access. Job seekers' resumes are personal data in every jurisdiction, and no proxy changes that. For the sister site of the same operator, whose measurement points the same way, see what we measured on [Glassdoor through residential proxies](https://quanticdata.io/blog/glassdoor-proxies/).

## The setting that works on Indeed

- **Network:** [residential proxies](https://quanticdata.io/residential-proxies/), Basic line at $0.80/GB. A residential exit with a browser TLS fingerprint received the full home page on the first request in the United States and the UK site from the United Kingdom; the fingerprint decided, not the address, so Premium at $2.20/GB, mobile at $2.30/GB and ISP at $2.50 per IP per month buy nothing here.

- **Fetch mode:** `engine: tls`, plain HTTP with a current browser fingerprint. 1,026 words on the first request on 26 September, 601,347 bytes and 2,394 words in 9.4 seconds on 28 September. Rendered: 1,066,178 bytes and 52 seconds for 683 words.

- **Country:** pin `country=us` for indeed.com. From a UK exit the same URL redirects to uk.indeed.com, 216 words, CVs instead of resumes, pounds instead of dollars.

- **When the proxy is not enough:** the [indeed_jobs collector](https://quanticdata.io/collectors/indeed-jobs-api/), 10 listings with parsed salary ranges in 7.3 seconds at $0.001 per listing, up to 300 per run. For a raw page as Markdown, the [web scraping API](https://quanticdata.io/web-scraping-api/) from $0.0002 per page, plain fetch, browser fingerprint included.

- **Free tier:** every account gets $2 of free API usage per month, which is 2,000 parsed listings from the collector or 10,000 plain-fetch pages before you pay anything.

### Sources & further reading

- [indeed.com/robots.txt (fetched 28 September 2026)](https://www.indeed.com/robots.txt)

- [Indeed Terms of Service](https://www.indeed.com/legal)

- [Indeed Partner Documentation](https://docs.indeed.com/)

## FAQ

Quick answers on indeed proxies.

[Something else? Ask us →](mailto:hello@quanticdata.io)

### Do I need a headless browser to scrape Indeed?

No, and it costs you words. On 28 September 2026 a plain HTTP fetch with a browser TLS fingerprint returned 601,347 bytes and 2,394 words in 9.4 seconds; the rendered page cost 1,066,178 bytes and 52 seconds for 683 words. Two days earlier the plain fetch returned 1,026 words on the first request. Indeed server-renders the page; the browser replaces it with a shell.

### Why does my Indeed scraper get 19 words instead of the page?

Because the TLS handshake does not look like a browser. The same residential exit that receives 19 words with a generic client receives 601,347 bytes and 2,394 words with a Firefox fingerprint. Use a client that impersonates a current browser at the TLS layer, or an API that does it for you, before you buy more IPs.

### Does the exit country change what Indeed returns?

It changes the site. From a UK exit, indeed.com redirected to uk.indeed.com/?r=us with 216 words, a canonical of uk.indeed.com and a description promising CVs instead of resumes. Each country site has its own listings and currency, so pin one country per job.

### How do I get Indeed salaries as numbers?

Use the jobs collector. Ten "data engineer" listings in New York came back in 7.3 seconds with salary_min, salary_max and salary_period parsed from the raw string, from $80,000 to $275,000 a year, at $0.001 per listing. Three of the ten were flagged as sponsored and four had a company rating of 0 with 0 reviews, which means no reviews, not a zero rating.

### Is scraping Indeed allowed?

Indeed's robots.txt lets generic crawlers page to start=90, names AI retrieval agents as allowed, disallows AI training crawlers from every listing and company page, and refuses Scrapy by name. Its Site Rules say not to access the site outside its public interfaces or collect data by automated means without permission. The sanctioned route is the partner programme and its GraphQL APIs at docs.indeed.com.

### Which proxy type does Indeed need?

Residential Basic at $0.80/GB was enough: the decisive factor in our fetches was the TLS fingerprint, not IP reputation, and nothing in the test rewarded a mobile or ISP address. At 601,347 bytes a page that is 1,663 pages per gigabyte, $0.48 per thousand; the rendered route costs $0.85 per thousand for a third of the words.

## Send the handshake of a browser, not the browser

Every number here came from one platform: fetch any URL over plain HTTP with a browser fingerprint or through a real browser, compare the two views, and run the collector when you want salaries as numbers. Every account gets $2 of free API usage each month, and failed requests are never billed.

[Start free — $2/month included](https://quanticdata.io/signup/)[Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Related reading

[Social proxies LinkedIn Proxies: 1,993 Words, No Browser A LinkedIn company page measured through residential exits on 28 September 2026: 1,993 words and 373,575 bytes over plain HTTP, 1,920 words and 825,521 bytes rendered. The follower count sits in the meta description, the Organization schema in the head, and a German exit rewrites the number as 7.122.892 Follower:innen. The collector returns the company row in 4.3 seconds. Read →](https://quanticdata.io/blog/linkedin-proxies/) [Social proxies Reddit Proxies: 574 Words Without a Browser Reddit measured through residential exits on 28 September 2026: a subreddit listing answers a plain HTTP client with 574 words and 566,030 bytes, and the same URL rendered in a browser with 39 words and no canonical. The rate limit is printed in the response headers, 200 requests per window. Comment threads need the collector: 20 comments in 7.9 seconds. Read →](https://quanticdata.io/blog/reddit-proxies/) [Social proxies Trustpilot Proxies: 2,553 Words, Browser On Trustpilot measured through residential exits on 26 and 28 September 2026: the home page hands a plain HTTP client 19 words in 991 bytes and a rendered browser 2,553 words, then 3,588 on a second day. A company review page renders to 4,389 words in 1,631,458 bytes, with a status code that does not describe the body. The reviews collector returned 10 reviews with ratings, dates, verification and the company reply in 14.8 seconds. Read →](https://quanticdata.io/blog/trustpilot-proxies/)

## Also on this site

Quantic**Data**

Residential proxies & web data APIs for AI.

#### Proxies

- [Residential Basic](https://quanticdata.io/residential-proxies/#basic)

- [Residential Premium](https://quanticdata.io/residential-proxies/#plans)

- [Cheap Residential](https://quanticdata.io/cheap-residential-proxies/)

- [Mobile Proxies](https://quanticdata.io/mobile-proxies/)

- [Datacenter Proxies](https://quanticdata.io/datacenter-proxies/)

- [ISP Proxies](https://quanticdata.io/isp-proxies/)

- [Rotating Proxies](https://quanticdata.io/rotating-proxies/)

- [Sneaker Proxies](https://quanticdata.io/sneaker-proxies/)

- [SOCKS5 Proxies](https://quanticdata.io/socks5-proxies/)

- [IPv6 Proxies](https://quanticdata.io/ipv6-proxies/)

- [Proxy locations](https://quanticdata.io/proxies/)

#### Data APIs

- [MCP Server](https://quanticdata.io/mcp-server/)

- [Web Scraper API](https://quanticdata.io/web-scraping-api/)

- [SERP API](https://quanticdata.io/serp-api/)

- [Collectors](https://quanticdata.io/collectors/)

- [Web Data for AI](https://quanticdata.io/web-data-api-for-ai/)

- [Quantic AI](https://quanticdata.io/ai-web-scraping-service/)

- [Crawl & Map](https://quanticdata.io/crawl-map/)

- [SEO Audit](https://quanticdata.io/seo-audit/)

#### Use cases

- [Company data](https://quanticdata.io/scrape-company-data/)

- [Price monitoring](https://quanticdata.io/competitor-price-monitoring/)

- [Market research](https://quanticdata.io/market-research-data/)

- [Real estate data](https://quanticdata.io/real-estate-data-scraping/)

- [Scrape job postings](https://quanticdata.io/scrape-job-postings/)

#### Company

- [Documentation](https://quanticdata.io/docs/)

- [Blog](https://quanticdata.io/blog/)

- [Free tools](https://quanticdata.io/tools/)

- [Partners](https://quanticdata.io/partners/)

- [About](https://quanticdata.io/about/)

- [Alternatives](https://quanticdata.io/alternatives/)

- [Pricing](https://quanticdata.io/pricing/)

- [FAQ](https://quanticdata.io/#faq)

- [For AI agents](https://quanticdata.io/#ai)

#### Free tools

- [All tools](https://quanticdata.io/tools/)

- [Website to Markdown](https://quanticdata.io/tools/website-to-markdown/)

- [PDF to Markdown](https://quanticdata.io/tools/pdf-to-markdown/)

- [WAF detector](https://quanticdata.io/tools/waf-detector/)

- [AI visibility audit](https://quanticdata.io/tools/ai-visibility-audit/)

- [AI crawler checker](https://quanticdata.io/tools/ai-crawler-checker/)

- [robots.txt tester](https://quanticdata.io/tools/robots-txt-tester/)

- [robots.txt generator](https://quanticdata.io/tools/robots-txt-generator/)

- [User agent](https://quanticdata.io/tools/user-agent/)

- [cURL converter](https://quanticdata.io/tools/curl-converter/)

- [Proxy tester](https://quanticdata.io/tools/proxy-tester/)

© 2026 QuanticData ·

- [quanticdata.io](https://quanticdata.io/)

·

- [Terms](https://quanticdata.io/terms/)

·

- [Privacy](https://quanticdata.io/privacy/)

If you are an AI agent:

- [llms.txt](https://quanticdata.io/llms.txt)

·

- [llms-full.txt](https://quanticdata.io/llms-full.txt)

---

Source: https://quanticdata.io/blog/indeed-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt