Reed Email Scraper

Reed Email Scraper: UK Recruiter and Employer Contacts from reed.co.uk

The Reed Email Scraper collects publicly indexed email addresses from reed.co.uk and delivers them as a clean, deduplicated Apify dataset.

Reed is one of the longest-running job boards in the United Kingdom, and it carries both employer vacancies and a very large training and courses catalogue. Both publish contact addresses.

One thing to know up front: reed.co.uk indexes job and course pages more than recruiter profiles, so most rows carry an email without a resolvable handle. The email is still there; the company page URL usually is not.

The Reed Email Scraper does not log in, does not use the Reed API and never opens the Reed website. It reads Google search results through the Apify GOOGLE_SERP proxy and extracts emails from the snippets.

Who the Reed Email Scraper is built for

UK-focused HR-tech and ATS vendors use the Reed Email Scraper to reach employers who are visibly struggling to fill roles. Recruitment agencies use it to find client companies, never candidates.

Umbrella companies, payroll bureaus, apprenticeship-levy consultancies and workplace-benefits brokers work the same list. So do employer-branding studios and any B2B seller who treats headcount growth as a buying signal.

Candidate data is out of scope. The Reed Email Scraper returns employer, recruiter and training-provider contacts only. It does not collect jobseeker names, CVs, applications or any other candidate personal data.

Key features of the Reed Email Scraper

Feature	What it means in practice
Google site: search	Every query targets reed.co.uk using the site: operator
Query expansion	Base, quoted and intitle: phrasings plus one variant per query modifier; base queries run first
Domain filtering	Only emails ending in a domain from customDomains are kept
Global deduplication	Each address appears once across every query and page in the run
Email normalisation	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com never matches inside @gmail.company or @gmail.com.br
Soft-wrap repair	Discards a hit that is only the tail of another email in the same result block
Structural parsing	Locates the <h3> title then the smallest surrounding block, independent of Google CSS class names
Whole-page fallback	A Google markup change degrades to "emails without account details", not "no emails"
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty
Retries and re-queue	Up to 3 attempts per page with exponential backoff and a fresh proxy session; failed queries retry once at the end
Resumable state	Key-value store state keyed by an input hash, saved on PERSIST_STATE, MIGRATING and ABORTING
Async concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Streaming output	Leads reach the dataset as they are found, so aborted runs are still useful
Run summary	Pages fetched, blocked pages, retries and emails per page are logged

Everything listed ships in the Reed Email Scraper today. No hidden modes, no paid add-ons.

How the Reed Email Scraper works

No browser, no JavaScript rendering, no authentication, no cookies. Six steps, start to finish.

1. The Reed Email Scraper reads keywords, location, email domains and limits from your input.
2. It builds Google queries with the site: operator, for example site:reed.co.uk recruiter "@gmail.com" "Manchester".
3. It fetches result pages asynchronously with aiohttp through the Apify GOOGLE_SERP proxy.
4. It parses each result block structurally rather than by CSS class name.
5. It extracts emails with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight to the dataset.

Google caps a single query at roughly 300 results, so query expansion is how the Reed Email Scraper widens coverage. Keep expandQueries on.

Measured Reed Email Scraper performance

In a real ten-page run the Reed Email Scraper returned 10 result blocks, resolved 2 account identities, produced 2 profile URLs and yielded 2 unique emails.

That is a modest result and worth being plain about. Reed is not the highest-yield source in this family, and the low identity count follows directly from the indexing pattern described above.

Reed still earns a place in a UK programme because the addresses it does surface are genuine employer and provider contacts. Pair the Reed Email Scraper with the Totaljobs Email Scraper, which shows a similar shape but higher email yield.

Results vary with keywords, domains and location. That run is one observation and no volume is guaranteed.

Reed Email Scraper input fields

Field	Type	Default	Meaning
keywords	array (required)	["recruiter", "hiring"]	Search terms describing the reed.co.uk pages you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; the leading @ is optional
maxEmails	integer 1-10000	20	Stop once this many unique emails have been collected
countryCode	string	""	Two-letter country code for the search proxy
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "apply", "recruiter", "hiring"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	How many queries run in parallel

Only keywords is required, so the Reed Email Scraper will run on defaults while you experiment.

Tuning Reed Email Scraper location and countryCode for the UK

Reed is a single-country board, so set countryCode to GB and leave it there. That one change materially improves the relevance of what the Reed Email Scraper returns.

location then does the real segmentation work. London, Manchester, Birmingham, Leeds, Glasgow, Bristol and Cardiff each surface a different employer set.

Do not overlook regional phrases. Milton Keynes, Reading, Newcastle upon Tyne and Belfast pull SMEs that a London-weighted query never reaches.

Keyword choice matters more than usual because Reed mixes jobs with training. recruitment agency, apprenticeship, training provider, CIPD and payroll each isolate a distinct cohort.

Because yield is the constraint here, widen customDomains. Add @outlook.com, @hotmail.co.uk, @btinternet.com and @yahoo.co.uk alongside the defaults.

Example Reed Email Scraper input

{
  "keywords": ["recruiter", "hiring", "recruitment agency", "training provider"],
  "location": "Manchester",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com", "@hotmail.co.uk"],
  "maxEmails": 250,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "apply", "recruiter", "hiring"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Reed Email Scraper output fields

Every dataset item the Reed Email Scraper writes carries all fourteen fields below.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints
fullName	Display name parsed from a profile-style title; empty for listing snippets
username	URL-safe handle when Reed exposes one; otherwise null
profileUrl	Canonical company URL when a handle is known; otherwise empty
url	Direct reed.co.uk link when exposed, else the profile URL
description	Snippet text, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain
possiblyTruncated	true when Google's snippet ellipsis touched the email
foundAt	ISO 8601 UTC timestamp

Example Reed Email Scraper output

[
  {
    "network": "Reed",
    "keyword": "recruitment agency",
    "query": "site:reed.co.uk \"recruitment agency\" \"@gmail.com\" \"Manchester\"",
    "title": "Warehouse Operative - Trafford Park | Reed.co.uk",
    "accountName": "Pennine Staffing",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.reed.co.uk/jobs/warehouse-operative-trafford-park/54120118",
    "description": "Immediate starts across Trafford Park. Send your CV to pennine.staffing@gmail.com to register.",
    "email": "pennine.staffing@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T11:20:41Z"
  },
  {
    "network": "Reed",
    "keyword": "training provider",
    "query": "site:reed.co.uk intitle:\"training provider\" \"@outlook.com\"",
    "title": "Northgate Skills Academy | Courses | Reed.co.uk",
    "accountName": "Northgate Skills Academy",
    "fullName": "Northgate Skills Academy",
    "username": "northgate-skills-academy",
    "profileUrl": "https://www.reed.co.uk/company/northgate-skills-academy",
    "url": "https://www.reed.co.uk/company/northgate-skills-academy",
    "description": "Accredited health and safety and CIPD courses across the North West. Enquiries to enquiries.northgate@outlook.com",
    "email": "enquiries.northgate@outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T11:22:09Z"
  }
]

The first row is the common case for the Reed Email Scraper: a usable email with username set to null and profileUrl empty. The second, with a resolved handle, is the exception.

Use cases for the Reed Email Scraper

Buyer	How they use the Reed Email Scraper
UK HR-tech and ATS vendors	Reach employers reposting the same vacancy month after month
Recruitment and staffing agencies	Build a client prospect list by city and sector
Umbrella and payroll providers	Target agencies placing contractors at volume
Apprenticeship-levy consultancies	Contact employers advertising trainee and apprentice roles
Benefits and insurance brokers	Approach UK SMEs visibly growing headcount
Employer-branding agencies	Pitch to firms whose Reed adverts read as boilerplate
Training and e-learning vendors	Reach providers already selling courses through Reed
Workforce researchers	Track which UK regions and sectors are advertising hardest

Building a UK prospect list with the Reed Email Scraper

Begin narrow. Run the Reed Email Scraper with two or three precise keywords, check relevance, then widen rather than starting broad.

Because yield is modest, give the run room. Raise maxEmails, keep maxPagesPerQuery at 30 and leave query expansion on.

Export CSV or JSON from the Apify console, or pull the dataset into your CRM via the Apify API. Filter out any row where possiblyTruncated is true before sending.

Expect to enrich. Since most rows lack a profileUrl, use accountName and the description snippet to identify the company before outreach.

Scheduling the Reed Email Scraper weekly keeps the list fresh, because UK vacancies turn over quickly and a stale advert is a weak hiring signal.

Responsible use of the Reed Email Scraper

The Reed Email Scraper collects only addresses already publicly visible in Google's index. That does not make every downstream use lawful.

UK B2B email marketing sits under UK GDPR and PECR; recipients elsewhere in Europe bring EU GDPR, and US contacts fall under CAN-SPAM.

In practice: a genuine business purpose, accurate sender identity, a clear and working unsubscribe path, and prompt honouring of opt-outs. This is general guidance, not legal advice, and you should take your own.

These are business contacts published for recruitment and course enquiries. Treating them as a consumer list is the quickest route to complaints.

Limitations of the Reed Email Scraper

• reed.co.uk indexes job and course pages more than recruiter profiles, so most rows carry an email without a resolvable handle. Expect username: null and an empty profileUrl on the majority of rows.
• Measured yield is modest: 10 blocks produced 2 identities and 2 unique emails in a real run.
• The Reed Email Scraper only finds addresses that are publicly visible in Google's index.
• Google caps a single query at roughly 300 results, which is why query expansion exists.
• possiblyTruncated: true means Google's snippet ellipsis touched the email and it may be cut off. Verify before sending.
• username and profileUrl populate only when Google's result exposes a handle. This is a Google limitation, not a bug.
• The Actor requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
• Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
• Results vary with keywords, domains and location. No volume is guaranteed.
• Candidate and jobseeker personal data is out of scope by design.

Reed Email Scraper FAQ

How many results should I expect from the Reed Email Scraper?

A measured ten-block run produced 2 identities, 2 profile URLs and 2 unique emails. Reed is a modest-yield source, so raise maxEmails, widen customDomains and expect to run several keyword sets.

Does the Reed Email Scraper collect candidate or jobseeker data?

No. It returns employer, recruiter and training-provider contacts only. It does not gather jobseeker names, CVs, applications or any other candidate personal data.

Why are most username values null?

Because reed.co.uk indexes job and course pages more than recruiter profiles, so most rows carry an email without a resolvable handle. The email is still valid.

Does the Reed Email Scraper log into Reed?

No. There is no login, no Reed API call and no visit to reed.co.uk. Everything comes from publicly indexed Google search results.

Which domain does the Reed Email Scraper search?

reed.co.uk only. Reed is a UK-focused board, so set countryCode to GB.

How do I improve Reed Email Scraper yield?

Widen customDomains with @outlook.com, @hotmail.co.uk and @yahoo.co.uk, use more specific keywords, raise maxEmails and keep expandQueries on.

Can the Reed Email Scraper target a specific UK city?

Yes. Set countryCode to GB and put a city or region in location. Running the Reed Email Scraper once per city consistently beats one national sweep.

Which other UK Actors should I run alongside it?

The Totaljobs Email Scraper has the same shape but better email yield, and the JobServe Email Scraper covers UK contract and IT roles.

What does possiblyTruncated mean?

Google's snippet ended in an ellipsis that touched the email, so the address may be incomplete. Treat those rows as needing verification.

Can I resume an interrupted run?

Yes. State is kept in the key-value store keyed by an input hash, and saves fire on Apify's PERSIST_STATE, MIGRATING and ABORTING events.

Is the Reed Email Scraper affiliated with Reed?

No. It is an independent tool and is not endorsed by or affiliated with Reed.

Is there a cap on emails per run?

Free Apify plans stop at 100 emails per run. Paid plans are uncapped and maxEmails accepts 1 to 10000.

What if Google changes its layout?

A whole-page fallback parser takes over, so the Reed Email Scraper degrades to emails without account details rather than to no emails at all.

Related Actors

Building wider UK or international coverage? These 27 sibling Actors run the same engine against other boards. UK teams usually add the Totaljobs Email Scraper first, then the Monster Email Scraper for its UK domain, and the Glassdoor Email Scraper for the strongest all-round employer coverage in the family.

Actor	What it collects
Reed Email and Phone Number Scraper	Emails and phone numbers from Reed
Reed Phone Number Scraper	Public phone numbers from Reed
CareerBuilder Email Scraper	Public contact emails from CareerBuilder
CV-Library Email Scraper	Public contact emails from CV-Library
Dice Email Scraper	Public contact emails from Dice
Fiverr Email Scraper	Public contact emails from Fiverr
FlexJobs Email Scraper	Public contact emails from FlexJobs
Freelancer Email Scraper	Public contact emails from Freelancer
Glassdoor Email Scraper	Public contact emails from Glassdoor
Guru.com Email Scraper	Public contact emails from Guru
Hired Email Scraper	Public contact emails from Hired
Indeed Email Scraper	Public contact emails from Indeed
JobServe Email Scraper	Public contact emails from JobServe
Jobspresso Email Scraper	Public contact emails from Jobspresso
JobStreet Email Scraper	Public contact emails from JobStreet
Ladders Email Scraper	Public contact emails from Ladders
Monster Email Scraper	Public contact emails from Monster
PeoplePerHour Email Scraper	Public contact emails from PeoplePerHour
Remote.co Email Scraper	Public contact emails from Remote.co
Remote OK Email Scraper	Public contact emails from Remote OK
Remotive Email Scraper	Public contact emails from Remotive
SEEK Email Scraper	Public contact emails from SEEK
SimplyHired Email Scraper	Public contact emails from SimplyHired
The Muse Email Scraper	Public contact emails from The Muse
Toptal Email Scraper	Public contact emails from Toptal
Totaljobs Email Scraper	Public contact emails from Totaljobs
Upwork Email Scraper	Public contact emails from Upwork
We Work Remotely Email Scraper	Public contact emails from We Work Remotely
ZipRecruiter Email Scraper	Public contact emails from ZipRecruiter
CV-Library Email and Phone Number Scraper	Emails and phone numbers from CV-Library
Fiverr Email and Phone Number Scraper	Emails and phone numbers from Fiverr
FlexJobs Email and Phone Number Scraper	Emails and phone numbers from FlexJobs
Freelancer Email and Phone Number Scraper	Emails and phone numbers from Freelancer
Glassdoor Email and Phone Number Scraper	Emails and phone numbers from Glassdoor
Guru Email and Phone Number Scraper	Emails and phone numbers from Guru
Hired Email and Phone Number Scraper	Emails and phone numbers from Hired
Indeed Email and Phone Number Scraper	Emails and phone numbers from Indeed
JobServe Email and Phone Number Scraper	Emails and phone numbers from JobServe
Jobspresso Email and Phone Number Scraper	Emails and phone numbers from Jobspresso
JobStreet Email and Phone Number Scraper	Emails and phone numbers from JobStreet
Ladders Email and Phone Number Scraper	Emails and phone numbers from Ladders
Monster Email and Phone Number Scraper	Emails and phone numbers from Monster

Leave a review

If the Reed Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.