UK Job Market Stats – Reed job counts and pay by region
Pricing
from $1.50 / 1,000 listing analyzeds
UK Job Market Stats – Reed job counts and pay by region
Counts of UK job postings on Reed.co.uk by ITL1 region and job category: how many are live, how many state pay, and the median advertised pay per unit. Aggregates only, no postings or names. Read live from list pages on each run.
Pricing
from $1.50 / 1,000 listing analyzeds
Rating
0.0
(0)
Developer
Yusuke Suda
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
How many jobs are advertised on Reed.co.uk in each of the 12 UK regions (ITL1: London, South East, ... Scotland, Northern Ireland) and in 13 job categories, how many of them state pay, and the median advertised pay, with yearly, hourly and daily pay kept apart. One run gives you today's numbers; schedule it daily for a series.
Example
| Site | Region | Postings | With pay | Median pay (lower bound) |
|---|---|---|---|---|
| reed.co.uk | London | 227 | 110 | £70,001 per year |
| reed.co.uk | South East | 170 | 86 | £38,000 per year |
| reed.co.uk | North West | 159 | 107 | £70,001 per year |
Default input, run on 20 October 2026: 1,000 listings read in 1.4 minutes, 184 aggregate rows; at $1.50 per 1,000 listings read the run cost $1.50.
The £70,001 medians are real but come from one advertiser: that day it had posted 263 near-identical solicitor jobs at £70,001–80,000 all over the UK among the newest 1,000 postings. A newest-first sample shows such bursts; a larger maxListings dilutes them.
What you get, and what you don't
- Counts, not listings. The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts, no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
- List pages only. The run reads the site's public search-result pages, paced as the site's own Actor in this catalogue is (one request every 2 seconds), and never opens a listing's own page.
- A sample of the newest listings. The site lists newest first; the run counts up to
maxListingsof them. The summary row says how many were read and, where the site shows it, the site's own total. - Medians need 5 values. A median is shown only where at least 5 postings have the value; otherwise it is empty.
- The last row of every run is a
summaryper site: postings read, the site's own total where shown, whether the run stopped atmaxListings, and any warning (an unknown place, a blocked page).
Input
| Field | What it does |
|---|---|
maxListings | Postings to read and count at most (default 1,000, up to 10,000). |
region | One region only (see below). Empty: the whole country. |
category | One job category only: it, finance_admin_hr, sales_customer, production, engineering_technical, transport_logistics, construction, health_care, education, hospitality_food, cleaning_security, management, other. |
keyword | Count only the postings the site finds for this word. |
Example: {"region": "Scotland", "category": "health_care", "maxListings": 2000}. An input the run cannot use (an unknown region, a keyword with no result) ends
SUCCEEDED with no rows and the reason in the status message and the run report (RUN_REPORT).
Output
| Field | Meaning |
|---|---|
level | region (one row per region), region_category (per region and job category) or summary. |
date | Day of the run (UTC). |
source | The site counted. |
region | Region, abroad or unmapped. |
category | Job category (all on region rows). |
postings | Postings read in this group. |
postings_with_pay | Of them, postings that state pay. |
pay_unit, currency | The pay period and currency of this row's median. A group with several units has one row per unit. |
postings_with_this_unit | Postings with pay in this unit and currency. |
median_pay_lower | Median of the lower bound of the advertised pay; empty below 5 postings. |
How the counts are made
The location Reed shows is placed in one of the 12 ITL1 regions with a table of about 1,200 UK towns and boroughs. A place not in the table stays unmapped (2.5 % in the example run). With region set, the run searches that region's largest towns on Reed and keeps only the postings our table places in the region.
In the example run 59 % of the postings stated pay. The median is of the lower bound of the range, per unit (year, hour, day, week, month) and currency: a region with yearly and hourly pay gets one row for each.
Job categories are found from keywords in the job title (English and the site's language), first match wins, other when nothing matches: approximate. Share of other in the example run: 10 %.
Pricing
$1.50 per 1,000 postings read (event listing-analyzed), no start fee. The aggregate rows themselves
are free: a default run reads up to 1,000 postings and costs at most $1.50. Set a maximum charge per run
in the run options to cap it.
Good to know
- The data is what Reed.co.uk shows on its public list pages on the day of the run.
- Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its
date. - Questions or a missing region: open an issue on this Actor.