How to Scrape Indeed Jobs from RSS to CSV

Download path: start from the Indeed Scraper template, then keep this tutorial open while you configure the workflow and audit the first CSV.

Prerequisites and policy checks

You need UScraper installed as a local desktop app, the downloadable workflow from the template library, and a folder where the CSV can be saved. You also need a small, specific research question: for example, "software engineer roles in the United States", "remote data analyst jobs", or "contract recruiter listings in Chicago." A focused search is easier to validate than a broad crawl.

Review the current Indeed legal terms, Indeed Terms FAQ, and robots.txt before running automation. Indeed's robots file includes rules that matter to RSS, job detail, and paginated job-search URLs, so do not treat a feed URL as automatic permission to collect, store, republish, or resell job data.

Browser visibility is not the same as permission. If Indeed shows verification, CAPTCHA, login, access-denied, or empty-result screens, pause the run and document what happened.

---

How the Indeed scraper workflow works

The JSON export is the source of truth. The bundled Navigate block opens five RSS URLs for the sample query software engineer in the United States, using start=0, start=10, start=20, start=30, and start=40. After each page loads, the workflow injects JavaScript that tries to parse RSS item records, cleans title and description text, detects salary or job-type phrases when present, and creates one visible .uscraper-rss-item element per row.

If no feed items are found, the workflow still exports one row with scrape_status set to blocked_or_no_items. That behavior is intentional. A failed run should leave evidence instead of silently creating an empty spreadsheet.

Export shape from the workflow definition

There is no bundled CSV sample for this post. Use the workflow definition and your first dry run together: the JSON defines the intended columns, while your local CSV confirms what Indeed returned for the exact keyword, location, session, and date.

The authoritative JSON excerpt looks like this when reduced to the blocks and export columns that matter for setup:

{
  "project": {
    "name": "Indeed Scraper",
    "description": "Uses Indeed RSS search URLs with start-offset pagination, normalizes available feed items into rows, and exports job data or a diagnostic row."
  },
  "blocks": [
    {
      "title": "Navigate",
      "config": {
        "urls": [
          "https://www.indeed.com/rss?q=software+engineer&l=United+States&start=0",
          "https://www.indeed.com/rss?q=software+engineer&l=United+States&start=10",
          "https://www.indeed.com/rss?q=software+engineer&l=United+States&start=20"
        ]
      }
    },
    {
      "title": "Structured Export",
      "config": {
        "rowSelector": ".uscraper-rss-item",
        "fileName": "indeed-scraper.csv",
        "includeHeaders": true,
        "fileMode": "append",
        "columns": ["job_title", "job_url", "company", "location", "salary", "job_type", "posted_date", "valid_date", "experience_level", "description", "guid", "source", "feed_page_url", "scrape_status"]
      }
    }
  ]
}

---

How to scrape Indeed jobs with the template

Common issues and fixes

Indeed scraper Python vs a local no-code workflow

If you searched for indeed scraper python, the trade-off is control versus setup time. Python is appropriate when you need unit tests, custom storage, queues, monitoring, and approved infrastructure. A local desktop app workflow is faster when the task is a supervised research export: edit a URL list, run a few pages, inspect rows, and hand a CSV to a recruiter or analyst.

---

FAQ

Is it legal to scrape Indeed jobs?

Indeed pages and feeds may be reachable in a browser, but automated collection can still be limited by Indeed terms, robots directives, privacy law, copyright, and how you reuse job-posting text. Review the current rules, avoid private or login-only data, do not bypass access controls, and get legal review before commercial use.

Do I need an Indeed API or account?

No Indeed account or API key is built into the template. It opens editable RSS search URLs and exports fields that are present. Use official or licensed access when you need contractual reuse rights, scheduled delivery, or production guarantees.

What does the Indeed scraper export?

The workflow exports indeed-scraper.csv with job_title, job_url, company, location, salary, job_type, posted_date, valid_date, experience_level, description, guid, source, feed_page_url, and scrape_status.

Why does scrape_status say blocked_or_no_items?

That status means no usable RSS items were found. Indeed may have returned an interstitial, CAPTCHA, empty feed, changed endpoint, or blocked automated access. Treat the row as a diagnostic and pause rather than trying to force a result.

Can I use this instead of an Indeed scraper Python script?

Yes, when the goal is a reviewed CSV export without maintaining code. Use Python instead when your team needs custom logic, automated tests, databases, scheduling, and approved production infrastructure.

Where does the CSV export go?

Structured Export writes indeed-scraper.csv to the local save folder configured in the workflow. The stock template does not upload your CSV to UScraper infrastructure unless you add a separate upload or sharing step.

Related templates and next steps

Use the Indeed Scraper template for the RSS workflow in this tutorial. If your workflow starts from direct job-detail URLs, read the Indeed job scraper by URL tutorial. For broader options, browse the UScraper blog and template library before choosing between a local workflow, Python, hosted scraping actors, or licensed access.