# Indeed Hiring Signals Scraper (`mighty_monk/indeed-hiring-signals-scraper`) Actor

Scrape public Indeed job search results for hiring signals. Extract job listings and aggregate company-level hiring signals (open roles, titles, locations) for cold email and lead gen triggers.

- **URL**: https://apify.com/mighty\_monk/indeed-hiring-signals-scraper.md
- **Developed by:** [Harsh](https://apify.com/mighty_monk) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 job or hiring signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does Indeed Hiring Signals Scraper do?

**Indeed Hiring Signals Scraper** turns public [Indeed](https://www.indeed.com) job search results into **structured hiring signals** you can use for cold email, outbound, and lead generation. Search for roles like **SDR**, **sales development**, **account executive**, or **growth marketer**, then get clean job rows plus optional **company-level aggregates** (`openRolesCount`, titles, locations, `signal: "hiring"`).

Run it on the **Apify platform** for API access, scheduling, integrations (Make, Zapier, n8n), proxy rotation, and monitoring—no browser farm to maintain.

Ideal trigger for campaigns in the style of Nick Abraham-style autopilot outbound: **companies hiring SDRs often need lead gen help**.

### Why use Indeed Hiring Signals Scraper?

- **Cold email triggers** — Target companies actively hiring SDRs, BDRs, AEs, or growth roles.
- **Agency / freelancing pipeline** — Spot teams scaling sales and pitch outbound, RevOps, or creative services.
- **Market research** — Track which titles and locations are heating up for a niche.
- **Enrichment workflows** — Pipe `company` + `jobUrl` into Clay, Instantly, Smartlead, or your CRM.
- **Fast HTTP scraping** — Cheerio-based (no full browser) with multi-selector fallbacks and graceful block handling.

### How to use Indeed Hiring Signals Scraper

1. Open the Actor on Apify and click **Try for free**.
2. Enter one or more **queries** (e.g. `SDR`, `account executive`).
3. Optionally set **locations** (`United States`, `Remote`, `New York, NY`).
4. Set **maxJobsPerQuery** (per query × location pair).
5. Keep **proxy** enabled for best reliability against Indeed rate limits.
6. Run the Actor and download the dataset as JSON, CSV, Excel, or HTML.

### Input

See the **Input** tab for the full form. Main fields:

| Field | Type | Description |
| --- | --- | --- |
| `queries` | string\[] | Job keywords (required). Example: `["SDR", "sales development"]` |
| `locations` | string\[] | Locations. Empty string = nationwide. Default: `["United States"]` |
| `maxJobsPerQuery` | integer | Cap per query×location (default `50`) |
| `maxConcurrency` | integer | Concurrent HTTP requests (default `3`) |
| `maxRequestRetries` | integer | Retries per request (default `3`) |
| `requestDelayMs` | integer | Used to derive rate limiting (default `1000`) |
| `proxyConfiguration` | object | Apify Proxy settings |
| `emitCompanySignals` | boolean | Also emit aggregated `company_signal` rows (default `true`) |

Example input:

```json
{
    "queries": ["SDR", "sales development", "account executive", "growth marketer"],
    "locations": ["United States", "Remote"],
    "maxJobsPerQuery": 25,
    "maxConcurrency": 3,
    "requestDelayMs": 1000,
    "proxyConfiguration": { "useApifyProxy": true },
    "emitCompanySignals": true
}
```

### Output

Each dataset item is either a **job** or a **company\_signal**. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. The run also writes `JOBS.csv` and `SUMMARY.md` to the default key-value store.

#### Job record

```json
{
    "type": "job",
    "title": "Sales Development Representative",
    "company": "Acme SaaS",
    "companyUrl": "https://www.indeed.com/cmp/Acme-SaaS",
    "location": "Austin, TX",
    "salary": "$55,000 - $70,000 a year",
    "jobType": "Full-time",
    "descriptionSnippet": "Outbound SDR role focusing on B2B SaaS lead generation.",
    "jobUrl": "https://www.indeed.com/viewjob?jk=abc123def456",
    "postedAt": "2 days ago",
    "query": "SDR",
    "locationQuery": "United States",
    "scrapedAt": "2026-07-20T12:00:00.000Z",
    "error": null
}
```

#### Company signal record

```json
{
    "type": "company_signal",
    "company": "Acme SaaS",
    "openRolesCount": 2,
    "titles": ["Account Executive", "Sales Development Representative"],
    "locations": ["Austin, TX", "New York, NY"],
    "signal": "hiring",
    "scrapedAt": "2026-07-20T12:00:00.000Z",
    "error": null
}
```

### Data table

| Field | Description |
| --- | --- |
| `type` | `job` or `company_signal` |
| `title` | Job title |
| `company` | Employer name |
| `companyUrl` | Indeed company page when available |
| `location` | Job location text |
| `salary` | Salary snippet from search results |
| `jobType` | Full-time / Part-time / Contract / etc. |
| `descriptionSnippet` | Short snippet from the SERP |
| `jobUrl` | Public Indeed job URL |
| `postedAt` | Relative or absolute posted time |
| `query` | Search query that found the job |
| `locationQuery` | Location used in the search |
| `openRolesCount` | (signal) Distinct open roles for company |
| `titles` | (signal) Distinct titles |
| `locations` | (signal) Distinct locations |
| `signal` | Always `hiring` for aggregates |
| `scrapedAt` | ISO timestamp |
| `error` | Error message when a row partially failed |

### How much does it cost to scrape Indeed hiring signals?

**Pay-per-event (PPE):** **$0.002 per dataset item** (each job or company\_signal row), plus a tiny Actor-start fee.

Examples (compute/proxy extra on platform usage):

| Jobs + signals | Approx. PPE result cost |
| --- | --- |
| 100 rows | ~$0.20 |
| 1,000 rows | ~$2.00 |
| 10,000 rows | ~$20.00 |

Apify Free plan includes monthly free usage; paid plans unlock higher limits and residential proxies for harder targets.

### Tips for better hiring signals

- Use **role-intent queries**: `SDR`, `BDR`, `"sales development"`, `"account executive"`, `"growth marketer"`, `"demand generation"`.
- Pair with **geo** filters your ICP cares about (`Remote`, metro areas, or country).
- Keep **maxConcurrency** low (1–5) and enable **Apify Proxy RESIDENTIAL** — Indeed often blocks datacenter IPs with HTTP 403.
- Prefer **company\_signal** rows for prioritization: sort by `openRolesCount` and outreach the busiest hiring teams first.
- Deduplicate is automatic by Indeed job key (`jk`) across pages and queries.

### FAQ, disclaimers, and support

**Is scraping Indeed legal?**\
You are responsible for complying with Indeed’s Terms of Service, applicable laws, and robots.txt. Use data ethically (e.g. B2B outreach), and do not collect personal data beyond what is publicly listed for legitimate business purposes.

**Why do I get zero results?**\
Indeed frequently returns HTTP 403 or captchas to datacenter IPs. Use Apify Proxy with **RESIDENTIAL** groups (default), lower concurrency, and increase `requestDelayMs`.

**Does this scrape full job descriptions?**\
This Actor focuses on **search-result hiring signals** (title, company, location, salary snippet, snippet text). It does not visit every job detail page, which keeps runs faster and cheaper for outbound triggers.

**Need a custom solution?**\
Open an issue on the Actor’s Issues tab, or contact the developer for custom lead gen / enrichment workflows.

# Actor input Schema

## `queries` (type: `array`):

Indeed search keywords that signal hiring intent (e.g. SDR, sales development, account executive, growth marketer).

## `locations` (type: `array`):

Locations to search (e.g. United States, Remote, New York, NY). Empty location searches nationwide on Indeed.

## `maxJobsPerQuery` (type: `integer`):

Maximum number of unique jobs to scrape for each query×location combination.

## `maxConcurrency` (type: `integer`):

Maximum concurrent HTTP requests. Keep low (1–5) to reduce Indeed rate limits and blocks.

## `maxRequestRetries` (type: `integer`):

How many times to retry a failed HTTP request before giving up.

## `requestDelayMs` (type: `integer`):

Approximate delay between requests used to compute rate limiting (max requests per minute).

## `proxyConfiguration` (type: `object`):

Apify Proxy settings. Indeed frequently blocks datacenter IPs — use RESIDENTIAL for best results.

## `emitCompanySignals` (type: `boolean`):

When true, also push aggregated company\_signal rows (company, openRolesCount, titles, locations, signal: hiring).

## Actor input object example

```json
{
  "queries": [
    "SDR",
    "sales development",
    "account executive",
    "growth marketer"
  ],
  "locations": [
    "United States",
    "Remote"
  ],
  "maxJobsPerQuery": 50,
  "maxConcurrency": 3,
  "maxRequestRetries": 3,
  "requestDelayMs": 1000,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "emitCompanySignals": true
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `jobsCsv` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "SDR",
        "sales development",
        "account executive",
        "growth marketer"
    ],
    "locations": [
        "United States",
        "Remote"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mighty_monk/indeed-hiring-signals-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "queries": [
        "SDR",
        "sales development",
        "account executive",
        "growth marketer",
    ],
    "locations": [
        "United States",
        "Remote",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("mighty_monk/indeed-hiring-signals-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "SDR",
    "sales development",
    "account executive",
    "growth marketer"
  ],
  "locations": [
    "United States",
    "Remote"
  ]
}' |
apify call mighty_monk/indeed-hiring-signals-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=mighty_monk/indeed-hiring-signals-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xvYvkTcy37HLOnaox/builds/voWZo4jHXBgewdLDv/openapi.json