Naukri.com Job Scraper avatar

Naukri.com Job Scraper

Pricing

$1.00 / 1,000 results

Go to Apify Store
Naukri.com Job Scraper

Naukri.com Job Scraper

Scrape Naukri.com job listings by title and location. Get structured records with company, salary, experience, skills, and direct application URLs — ready for job boards, market analysis, and recruitment workflows.

Pricing

$1.00 / 1,000 results

Rating

0.0

(0)

Developer

Data Dino

Data Dino

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Share

Naukri.com Job Listings Scraper

Search Naukri.com for job listings by title and location, returning structured job records with company, salary, experience, skills, and direct application URLs. This actor stays undetected by navigating Naukri the way a real user does — keeping your runs reliable even as the site evolves and other scrapers get blocked.

It is built for recruiters, job-market analysts, researchers, and developers who need dependable Naukri.com data without worrying about bot detection taking their pipeline offline.

Why use this actor?

  • Stays undetected, stays working — avoids the bot-detection traps that take other scrapers offline. When Naukri changes its anti-scraping measures, this actor keeps delivering because it behaves like a real visitor.
  • No proxy required at small scale — other Naukri scrapers require Apify Residential proxies to avoid IP blocking. This actor works without proxy configuration for small to medium runs.
  • Free and open source — no per-result pricing, no result caps, no trial limits. Use it for research, analytics, or personal job search without a usage meter.
  • Simple mental model — just a job title and location. Three input fields, no complex filter builders or search URL construction required.
  • Structured output — every job listing returns 11 clean fields: title, company, description, logo, experience, location, posted date, salary, job ID, direct URL, and skills.

What you can collect

Each output record includes the following fields scraped directly from the Naukri.com search results page:

CategoryFields
Job identitytitle (job title), job_id (Naukri job ID), job_url (direct listing URL)
Companycompany (company name), logo_url (company logo image URL)
Descriptionjob_description (snippet from search results)
Classificationexperience (e.g. "3-5 Yrs"), location (e.g. "Hybrid - Hyderabad, Pune, Bengaluru"), posted_date (e.g. "2 days ago")
Compensationsalary (text as shown on Naukri, "N/A" when not disclosed)
Skillsskills (comma-separated skill tags)

Input

Provide a job title in searchTerm. Optionally set a location and a maxResults ceiling.

FieldTypeRequiredDefaultDescription
searchTermStringYesThe job title or keyword to search for on Naukri.com (e.g. "Python Developer", "Data Scientist").
locationStringNoIndiaLocation filter for the job search. Free-text; accepts city, state, or country names (e.g. "Bangalore", "Mumbai", "USA").
maxResultsIntegerNo20Maximum number of job listings to return. Range: 1–100.

Example input

{
"searchTerm": "Python Developer",
"location": "India",
"maxResults": 20
}

To search in a specific city:

{
"searchTerm": "Data Scientist",
"location": "Bangalore",
"maxResults": 50
}

Output

The actor pushes one dataset item per job listing. A representative result looks like this:

{
"title": "Python developer",
"company": "Infosys",
"job_description": "Preferred candidate profile Experience with frameworks such as Django, Flask, or FastAP...",
"logo_url": "https://img.naukimg.com/logo_images/groups/v1/13832.gif",
"experience": "3-5 Yrs",
"location": "Hybrid - Hyderabad, Pune, Bengaluru",
"posted_date": "2 days ago",
"salary": "N/A",
"job_id": "050826011769",
"job_url": "https://www.naukri.com/job-listings-python-developer-infosys-hyderabad-pune-bengaluru-3-to-5-years-050826011769",
"skills": "Python, Python Framework, Django, Flask, Framework, Python Development, Development"
}

Fields that are not present on the page are returned as "N/A". The job_url links directly to the Naukri.com listing page.

Built for practical workflows

  • Job market research — track job title frequency, salary trends, and skill demand across locations and companies.
  • Recruitment and sourcing — collect structured job listings for analysis, candidate matching, or competitive intelligence.
  • Skill gap analysis — extract skill tags from listings to map emerging technology requirements across industries.
  • Company hiring trends — aggregate listings by company to identify active hiring patterns and growth areas.
  • Personal job search — collect and organize listings with direct application URLs for offline review.
  • Restricted environments — operate reliably behind strict network policies or in regions where other scrapers get blocked.

How to run

  1. Open the actor in Apify.
  2. Enter a job title in searchTerm (required).
  3. Optionally set a location and a maxResults (defaults: "India", 20).
  4. Start the run.
  5. Review the dataset or export it as JSON, CSV, Excel, or another supported format.

Important limitations

  • Single page per run — the actor scrapes one search results page. maxResults is capped at 100 because Naukri.com search pages rarely exceed that many listings on a single page. Multi-page pagination is not yet supported.
  • No advanced filters — the actor does not support freshness (last 1/3/7/15/30 days), experience range, salary range, work mode (office/remote/hybrid), company type, role category, industry, department, or education filters. Use the searchTerm and location fields only.
  • No AmbitionBox enrichment — company ratings, reviews, and salary benchmarks from AmbitionBox are not included in the output.
  • No search URL input mode — the actor constructs the search URL from searchTerm and location. Pasting a pre-built Naukri search URL is not supported.
  • No direct job ID fetch — the actor cannot look up a specific job by its Naukri job ID. It always performs a keyword search.
  • Single-threaded execution — the actor runs one search at a time. Bulk collection across many search terms or locations requires multiple runs.
  • Speed trade-off — the anti-detection approach means each run takes a few seconds per page rather than being instant. This is a practical trade-off for reliability and works well for runs up to 100 results, but it is not designed for high-throughput bulk collection.
  • Naukri.com only — Naukrigulf.com is not supported.
  • Text-only job descriptions — the description field contains a text snippet from the search results page, not the full HTML job description found on the detail page.

The actor is read-only and uses only the public Naukri.com website. Use the collected information in accordance with Naukri.com's terms of service and your organization's data-use policies.