How to Scrape Indeed Jobs to CSV with UScraper

Prerequisites and policy checks

You need UScraper installed as a local desktop app, the current Indeed Job Scraper workflow, and a folder where CSV exports can be saved. Run the default search once before changing anything. That baseline tells you whether the page is accessible, whether Indeed is returning normal job cards, and whether the export columns still match the rendered layout.

Also decide why you are collecting the data. Hiring teams usually need a small market snapshot: job titles, salaries, locations, hiring companies, and application links for a specific role. Researchers may compare "part time jobs", "weekend jobs", "seasonal jobs", or local searches such as "Indeed jobs Atlanta" and "Indeed jobs Austin". Those searches have high demand, but volume does not remove compliance work.

Review the current Indeed Partner Docs, Indeed legal terms, and robots.txt before running automation. Browser visibility is not the same as permission to automate, store, resell, or republish data.

Treat this as a controlled research workflow. If Indeed shows verification, CAPTCHA, access-denied, or login-only screens, pause the run instead of trying to bypass the control.

What the Indeed job scraper template does

The JSON workflow is the source of truth. It starts at an Indeed search URL, waits for the page to load, injects JavaScript that turns visible job cards into structured .uscraper-job-row elements, exports those elements to CSV, checks whether the Next Page link exists, and loops until pagination ends.

The default search is web developer jobs on Indeed. To change the target, edit the q parameter for the keyword and the l parameter for location. For example, a recruiter could test part time jobs in Dallas, weekend jobs in NYC, seasonal retail roles, or remote UI developer listings. Validate one small search first, then repeat with additional keyword and location pairs.

How to scrape Indeed job listings to CSV

Do not scale the run until the first CSV matches what you see on the page. Indeed can show different cards by region, query, personalization state, and access conditions, so validation is part of the workflow rather than a final clean-up task.

CSV export shape from the JSON workflow

There is no bundled CSV sample, so use the workflow definition and your first dry run together. The export block includes headers and appends rows. If you repeat a search, archive the old CSV or dedupe by Job_ID and Job_URL.

The sample row above is intentionally labeled as a fallback because the provided JSON includes blocked-environment examples. Live runs should be checked against the browser before those rows are used for recruiting analysis, salary research, or lead lists.

{
  "project": {
    "name": "Indeed Job Scraper",
    "description": "Best-effort Indeed keyword job scraper"
  },
  "blocks": [
    {
      "title": "Navigate",
      "config": {
        "url": "https://www.indeed.com/jobs?q=web%20developer&l="
      }
    },
    {
      "title": "Structured Export",
      "config": {
        "rowSelector": ".uscraper-job-row",
        "fileName": "indeed-job-scraper-by-keywords.csv",
        "includeHeaders": true,
        "fileMode": "append",
        "columns": [
          { "name": "Job_Title", "attribute": "data-job-title" },
          { "name": "Company_Name", "attribute": "data-company-name" },
          { "name": "Salary", "attribute": "data-salary" },
          { "name": "Apply_Link", "attribute": "data-apply-link" }
        ]
      }
    }
  ]
}

Indeed jobs API vs scraping

Start with official channels when you need a durable integration. The Indeed Partner Docs cover partner API and job integration paths for products that manage postings, candidates, employers, or publisher experiences. That route is better for production systems, contractual use, and redistribution rights.

Use a supervised scraper when you need a short research pass, an exportable CSV for market review, or a no-code workflow your analyst can inspect. A local desktop app is also useful when you want to see the same browser state the export came from and keep files in your own project folder.

No option removes the need to follow source terms, privacy rules, and internal data-handling policy. The right tool depends on whether you are doing one research export, recurring recruiting intelligence, or a production data product.

Common issues and fixes

FAQ