Jobsite UK Jobs Scraper

Scrape job postings from Jobsite.co.uk — title, employer + logo, location with lat/lng, structured salary band (min / max / currency / period), datePosted, validThrough, employment type, industry, and a populated applyUrl when the role is direct-apply. One flat row per job from rich JobPosting JSON-LD plus structured salary metadata.

Why this actor

Jobsite.co.uk is one of the UK's longest-running general-purpose job boards, with ~45,000 live postings at any time across every sector. This actor delivers clean structured rows fast:

• Efficient JSON listing pagination at 50 items per page, with totalItems reported up-front so we know exactly when we've reached the end of the result set
• Server-side filters — postedWithin (1 / 3 / 7 / 14 days), companyTypes (direct employer / agency), salary (minimum), and jobType (permanent / contract / temporary / part-time / work-from-home) all honoured server-side, identical to the web page
• Apify Residential GB for the per-job detail fetch (/job-ad/{id}) — the only proxy pool that consistently returns 200 OK on UK job-board detail pages
• JobPosting JSON-LD parsing — every row carries the full 14-field JSON-LD detail plus structured salary metadata (min/max/currency/period) so you don't have to regex it client-side
• applyUrl populated when directApply: true (≈ 60–70 % of jobs) — the candidate-facing apply URL, not just the search-page URL
• Mixed input — listing URLs auto-paginate + emit one row per detail; direct detail URLs scrape one row each

Use cases

• Recruitment market intelligence — salary benchmarking by region/role, employer activity tracking on Jobsite's general UK pool
• Sales prospecting — find companies hiring in your target verticals + locations, with employer name + logo + Jobsite company page URL on every row
• HR competitive analysis — compare your salary bands against the Jobsite market signal
• ATS / job-aggregator integration — clean structured input for downstream pipelines (structured salary, lat/lng, applyUrl)
• Geospatial analytics — every row carries location.lat + location.lng from JSON-LD PostalAddress.geo

Input

Field	Type	Required	Notes
startUrls	string[]	yes	Mix of listing URLs (https://www.jobsite.co.uk/jobs/in-london, /jobs/{keyword}/in-{location}) and direct detail URLs (/job/{title-slug}/{org-slug}-job{id}). Filters supported in the query string: ?postedWithin=1|3|7|14, ?companytypes=1|2, ?salary={int}, ?jobType=permanent|contract|temporary|partTime|workFromHome.
maxItems	integer	no	Maximum job rows emitted per listing URL. 3 listings × maxItems: 100 → up to 300 total rows. Direct detail URLs always emit 1 row each. Each row = one paid dataset item. Default 1000. Free-tier users have a hidden global ceiling of 100 rows.
maxConcurrency	integer	no	Parallel HTTP requests for detail-page fetches. Sweet spot 3–5 via Apify Residential GB. Default 4.
maxRequestRetries	integer	no	Per-URL retry budget on proxy CONNECT failures, HTTP/2 stream resets, and network errors. Each retry rotates the proxy session with mild exponential backoff. Default 6.
proxy	object	no	Apify Residential GB required for the detail-page fetch. Default is wired correctly — don't override unless you know what you're doing.

Example input

{
  "startUrls": [
    "https://www.jobsite.co.uk/jobs/software-engineer/in-london",
    "https://www.jobsite.co.uk/jobs/in-manchester?postedWithin=7&companytypes=2"
  ],
  "maxItems": 200,
  "maxConcurrency": 4,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "GB" }
}

Output schema

Every row has rowType: "job". 14 fields from JSON-LD + structured salary band + lat/lng + applyUrl.

{
  "rowType":           "job",
  "sourceSearchUrl":   "https://www.jobsite.co.uk/jobs/in-london",
  "jobId":             "107245246",
  "jobUrl":            "https://www.jobsite.co.uk/job/regional-optimization-lead/bp-energy-job107245246",
  "sourceSite":        "jobsite.co.uk",
  "title":             "Regional Optimization Lead",

  // ── JobPosting JSON-LD ──
  "description":       "<p>Entity: Supply, Trading & Shipping…</p>",
  "datePosted":        "2026-05-07T02:51:32.477Z",
  "validThrough":      "2026-06-18T02:51:32.477Z",
  "employmentType":    "FULL_TIME",
  "industry":          "Management, Management-Area Management",
  "directApply":       true,
  "jobLocationType":   null,
  "applicantLocationRequirements": [],

  // ── Employer ──
  "employer": {
    "name":            "BP Energy",
    "url":             "https://www.jobsite.co.uk/jobs/bp-energy?cmpId=1428985&cmp=1",
    "logoUrl":         "https://www.jobsite.co.uk/CompanyLogos/2e66e5e85ad5408380e06078af3eb663.png"
  },

  // ── Location ──
  "location": {
    "text":            "St James, London, WC2N 5DU, GB",
    "locality":        "St James",
    "region":          "London",
    "postalCode":      "WC2N 5DU",
    "country":         "GB",
    "lat":             51.50445,
    "lng":             -0.13601
  },

  // ── Salary ──
  "salary": {
    "rawText":         "£70,967 to £83,926 per annum",
    "min":             70967,
    "max":             83926,
    "currency":        "GBP",
    "period":          "annum"
  },

  // ── Apply flow ──
  "applyUrl":          "https://www.jobsite.co.uk/job/regional-optimization-lead/bp-energy-job107245246",
  "applyType":         "internal",

  "scrapedAt":         "2026-05-21T20:25:31.012Z"
}

Apply flow — what applyUrl and applyType mean

Every row carries two apply-flow fields derived from the JSON-LD directApply flag:

directApply	applyType	applyUrl	Meaning
true	"internal"	= jobUrl	Jobsite hosts a one-click apply form on the job page itself. Send the candidate to applyUrl (which is the same as jobUrl) and they can apply without leaving Jobsite.
false	"external"	null	The actual apply destination is an external recruiter ATS (e.g. Workday, Greenhouse). Open jobUrl in a browser and click Apply to be redirected.
missing	"unknown"	null	JSON-LD didn't surface the flag. Treat the same as "external".

Practical rule of thumb: ≈ 60–70 % of Jobsite listings are directApply: true, so for that majority you get a usable applyUrl directly.

Notes & limitations

• Apify Residential GB is mandatory for the per-job detail fetch. UK-residential routing is the only path that consistently returns 200 OK on detail pages.
• employmentType fill ≈ 70%. Not every JobPosting JSON-LD declares it. We don't synthesize when missing.
• jobLocationType only set for remote/hybrid roles. Non-remote jobs leave it null — matches JSON-LD semantics.
• Salary fill ≈ 95% when surfaced. Structured min/max/currency/period available on most rows; when both layers lack salary, the field is null — we don't synthesize.
• No radius-based filter. Use a tighter where= location instead, or post-filter rows by location.lat/location.lng.
• No maximum-salary filter. Only minimum (?salary=N). For range filtering, do it client-side on the row's salary.max.

FAQ

Which Jobsite URLs work? Two types: listing URLs (/jobs/in-london, /jobs/software-engineer/in-manchester, /jobs/{company-slug}-jobs) which auto-paginate and emit one row per linked job, and direct detail URLs (/job/{title-slug}/{org-slug}-job{id}) which scrape one row each. You can mix both in the same startUrls array.

Why do I need Apify Residential GB? Jobsite's detail pages are gated to UK residential proxy pools. Datacenter IPs and non-GB residential routes consistently fail. Apify Residential GB is the only pool we've tested that returns clean 200 OK on every probe.

What's the difference between sourceSearchUrl, jobUrl, and applyUrl? Three distinct things:

• sourceSearchUrl — the search/listing page you pasted as input. Breadcrumb back to "where this row came from in your batch", not a URL anyone clicks to view the job.
• jobUrl — the per-job detail page on Jobsite. Use this to view the full listing in a browser.
• applyUrl — where the candidate clicks to apply. Equal to jobUrl when directApply=true (Jobsite hosts the form); null when directApply=false (external recruiter ATS).

What does each dataset-item charge cover? One job row with all 14 JSON-LD fields plus the structured salary band (min/max/currency/period) and structured location (lat/lng). maxItems is per listing URL, so a maxItems: 100 run with 2 listings = up to 200 charges. The Apify Store pricing event is apify-default-dataset-item — Apify auto-charges per row written to the default dataset.

Why does one search return fewer rows than the Jobsite page shows? Two possibilities: (1) maxItems cap. It's per-listing-URL — if you set maxItems: 100 and pasted one URL, that's the ceiling. (2) Filter combo narrows the pool. The Jobsite "10,000+ jobs in London" badge counts the unfiltered corpus; once you apply postedWithin=1 or companytypes=2, the actual filterable count is often a fraction of the headline number. The actor's log emits [INTERNAL] totalItems=N so you can see the real server-side count after filtering.

Support

• Bugs / feature requests — open an issue on the GitHub repo
• Custom exports / tailored fields — drop a note via the Apify Store contact form
• Other actors — see my Apify Store profile for the rest of the catalog

---

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Jobsite.co.uk or any of its parent / sister companies. All trademarks mentioned are the property of their respective owners.

The scraper extracts only publicly visible job postings from Jobsite.co.uk — no login, no CAPTCHA solving, no credential forgery. The actor uses a conservative concurrency cap (default 4 parallel requests) to avoid burdening Jobsite's infrastructure.

Users are responsible for:

• Complying with Jobsite.co.uk's Terms of Service
• Following UK GDPR + your jurisdiction's data-protection laws when storing or processing scraped postings
• Not contacting candidates listed by employers in scraped postings
• Not republishing scraped data in a way that competes commercially with Jobsite

---

SEO Keywords

jobsite scraper, scrape jobsite, jobsite uk scraper, jobsite.co.uk scraper, jobsite api, Apify jobsite, uk jobs scraper, uk job board scraping, jobpostings api, jobposting json-ld scraper, uk recruitment api, recruitment scraper uk, uk salary data, salary band extraction, uk job market data, hiring intelligence uk, employer hiring data, b2b sales prospecting uk, london jobs scraping, manchester jobs scraper, edinburgh jobs scraper, apify residential gb