Public Company Career Page Job Monitor

What this Actor does

Monitor public company career pages and extract structured job openings for recruiting and hiring intelligence.

It processes user-provided public URLs, prioritizes JSON-LD/schema.org JobPosting structured data, and can optionally use a conservative fallback for visible public job-card links on career pages. It normalizes useful fields, deduplicates rows, and saves structured records to the Apify dataset.

Why this Actor is useful

Teams pay for this kind of extraction when it saves manual research, creates repeatable monitoring, feeds spreadsheets or CRMs, and turns public pages into clean API-ready datasets.

Who this is for

• Recruiters
• Staffing agencies
• Job boards
• HR tech founders
• Hiring intelligence teams
• Career newsletter operators
• B2B sales teams targeting hiring companies

Common use cases

• Track new openings across target companies
• Feed job boards or hiring newsletters
• Find companies currently hiring for B2B sales outreach
• Monitor competitor hiring signals
• Build recurring hiring intelligence datasets

Input

• startUrls: Public URLs to extract from. Use only pages you are allowed to access without login or bypassing access controls.
• maxItems: Maximum number of rows to save.
• maxConcurrency: Number of pages processed in parallel. The default is intentionally conservative.
• extractionMode: Use structuredDataOnly or structuredDataWithFallback. The default enables the safe public job-card fallback.
• includeDescription: Include public job descriptions from JobPosting structured data when available.
• includeRawStructuredData: Adds the original JSON-LD object for audit/debugging.
• requestTimeoutSecs: Maximum time to spend on a single page.
• proxyConfiguration: Optional Apify proxy configuration where permitted by your source review.

Output

• companyName: Hiring company name when exposed in structured data.
• careerPageUrl: The career page or job page supplied or discovered as the source.
• jobTitle: Public job title.
• jobUrl: Public application or job detail URL.
• location: Job location as listed by the source.
• department: Department or team when available.
• employmentType: Employment type such as full-time, contract, or internship.
• remoteStatus: Remote or hybrid signal when available.
• postedDate: Posting date or valid-through date when available.
• detectedAt: Timestamp when this Actor extracted the row.
• sourceUrl: URL where the data was extracted.
• extractionMethod: structured_data for valid JobPosting schema, or fallback_public_job_card for visible public career-page job cards.
• confidenceScore: Heuristic confidence score based on structured data availability.
• missingFields: Output fields that were not available from the source page.

Sample input

{
  "startUrls": [
    {
      "url": "https://example.com/"
    }
  ],
  "maxItems": 25,
  "maxConcurrency": 3,
  "extractionMode": "structuredDataWithFallback",
  "includeDescription": false,
  "requestTimeoutSecs": 30,
  "includeRawStructuredData": false
}

Sample output

{
  "companyName": "Example Robotics Labs",
  "careerPageUrl": "https://example.com/",
  "jobTitle": "Senior Backend Engineer",
  "jobUrl": "https://example.com/company-careers/senior-backend-engineer",
  "location": "Austin, TX, US",
  "department": "Engineering",
  "employmentType": "FULL_TIME",
  "remoteStatus": "HYBRID",
  "postedDate": "2026-06-01",
  "detectedAt": "2026-06-12T00:00:00.000Z",
  "sourceUrl": "https://example.com/",
  "extractionMethod": "structured_data",
  "confidenceScore": 0.95,
  "missingFields": []
}

How to use

Run this Actor on Apify with public URLs, export the dataset as JSON, CSV, Excel, or through the Apify API, then connect the output to Google Sheets, Make, Zapier, a webhook, your CRM, or an internal dashboard. For monitoring, save the input as an Apify task and schedule recurring runs.

Best practices

• Start with a small set of reviewed public URLs.
• Prefer pages with schema.org JSON-LD structured data.
• Use structuredDataOnly when you want the highest precision and can tolerate empty output.
• Use structuredDataWithFallback when reviewed public career pages show visible job cards but no JobPosting schema.
• Keep maxConcurrency low for smaller websites.
• Review source website rules before scheduling recurring runs.
• Keep includeRawStructuredData off unless you need audit details.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, collect private data, gather sensitive personal data, or support spam or abuse. You are responsible for following applicable laws and source website rules.

Limitations

• Output quality depends on public structured data available on the source pages.
• Fallback extraction is intentionally conservative and only looks for visible public job-card/link patterns. It does not claim universal career page support.
• Some fields may be empty when the source does not publish them.
• The Actor does not claim support for any specific third-party platform.
• Website markup and access policies can change.

Troubleshooting

• Empty output usually means the page has no public JobPosting JSON-LD/schema.org data.
• Invalid URL errors mean one or more input URLs are malformed.
• Slow runs can usually be improved by lowering maxConcurrency.
• Missing fields are source-data limitations, not inferred values.

Changelog

• v0.2.0: Production-readiness pass with improved positioning, samples, schema descriptions, and responsible-use notes.
• v0.1.0: Initial dry-run factory generated MVP.