Yalwa Email Scraper

Yalwa Email Scraper

The Yalwa Email Scraper searches publicly indexed Yalwa listings for business contact emails across yalwa.com and yalwa.co.uk. Set expectations before your first run: Yalwa has a small and ageing indexed footprint, so expect very low volume.

Our measured Google run of the Yalwa Email Scraper parsed a single result block. One. That is a thin source by any reasonable standard, and pretending otherwise would waste your time.

Use the Yalwa Email Scraper for citation audits and completeness sweeps. For actual list building, run the Fyple Email Scraper, the Brownbook Email Scraper or the Cylex Email Scraper instead.

What the Yalwa Email Scraper does

The Yalwa Email Scraper builds Google queries with the site: operator against yalwa.com and yalwa.co.uk. It parses each result block structurally, locating the <h3> title and the smallest surrounding block.

A domain-filtered regex then extracts any email present in the block text. Matches are normalised, deduplicated globally and pushed to your Apify dataset immediately.

The Yalwa Email Scraper never logs into Yalwa, never uses a Yalwa API and never opens the Yalwa website. There is no browser, no JavaScript rendering, no authentication and no cookies.

Where the Yalwa Email Scraper still has a job to do

Local SEO work is partly archaeology. Older free-listing directories like Yalwa still carry citations for businesses that have long since moved, rebranded or closed.

That is exactly what the Yalwa Email Scraper is good for. Finding a stale listing with an outdated address is a genuine finding for an agency cleaning up a client's citation profile.

Market researchers use it the same way, as one thin column in a directory coverage matrix rather than a source of volume.

Features of the Yalwa Email Scraper

Everything below is implemented in the Yalwa Email Scraper and applies to whatever Google returns.

Feature	What it means in practice
Google site: search over yalwa.com and yalwa.co.uk	Covers both Yalwa domains in one run
Query expansion	Base, quoted and intitle: variants plus one query per modifier; base queries run first
Domain filtering	Only emails ending in your customDomains values are kept
Global deduplication	Each email is emitted once per run across every query and page
Email normalisation	Handles name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠
Junk filter	Rejects email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same block
Structural block parsing	Works from the <h3> title, not Google's CSS class names
Whole-page fallback parser	A markup change degrades to "emails without account details", not "no emails"
Concurrency control	asyncio worker pool with a shared stop signal on maxEmails
Retries and block detection	Up to 3 attempts per page, exponential backoff, fresh proxy session per request, CAPTCHA and consent pages detected and retried
Failed-query requeue	Blocked or failed queries are retried once at the end of the run
Resumable state	Key-value store state keyed by an input hash, saved on PERSIST_STATE, MIGRATING and ABORTING
Run summary logging	Pages fetched, blocked pages, retries and emails per page

How the Yalwa Email Scraper works

A run of the Yalwa Email Scraper follows six steps, however little it finds.

1. Read your input: keywords, location, email domains and limits.
2. Build queries such as site:yalwa.co.uk driving instructor "@gmail.com" "Leeds".
3. Fetch Google result pages through the Apify GOOGLE_SERP proxy using async aiohttp.
4. Parse each result block structurally to isolate title, business label and snippet.
5. Extract and normalise emails with a domain-filtered regex.
6. Deduplicate globally and push each lead to the dataset immediately.

Step 3 is the constraint. With a small and ageing index there is very little for the Yalwa Email Scraper to parse in steps 4 to 6.

Input fields for the Yalwa Email Scraper

These are the exact inputs the Yalwa Email Scraper accepts, with its shipped defaults.

Field	Type	Default	Meaning
keywords	array (required)	["local business", "services"]	Search terms describing the businesses you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; @ optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "enquiries", "owner", "get a quote"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

Example input for the Yalwa Email Scraper

{
  "keywords": ["driving instructor", "man and van", "mobile hairdresser"],
  "location": "Leeds",
  "customDomains": ["@gmail.com", "@yahoo.co.uk", "@hotmail.co.uk"],
  "maxEmails": 50,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "enquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Location: the highest-leverage input in the Yalwa Email Scraper

On a source this thin, geography is your best chance of surfacing anything at all. Give the Yalwa Email Scraper a specific city rather than a country.

For the UK, probe "Leeds", "Sheffield", "Nottingham", "Bristol" or "Glasgow" with countryCode: "GB". For the US, try "Houston, TX", "Phoenix, AZ" or "Philadelphia, PA" with US.

Google caps a single query at roughly 300 results, but the Yalwa index limit will bind long before that ceiling matters.

If three or four city probes come back empty, stop and switch Actors rather than permuting more keywords.

Output fields from the Yalwa Email Scraper

When the Yalwa Email Scraper writes a row, that row 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 post captions
username	URL-safe handle when the platform exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio snippet, cleaned of labels and engagement 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 output from the Yalwa Email Scraper

This is the shape of a row on the rare occasion the Yalwa Email Scraper finds one. Most runs return one row or none.

[
  {
    "network": "Yalwa",
    "keyword": "driving instructor",
    "query": "site:yalwa.co.uk driving instructor \"@gmail.com\" \"Leeds\"",
    "title": "Northside Driving School - Leeds - Yalwa",
    "accountName": "Northside Driving School",
    "fullName": "Northside Driving School",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Manual and automatic lessons across north Leeds. Bookings northsidedriving.leeds@gmail.com",
    "email": "northsidedriving.leeds@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T20:18:35.412Z"
  }
]

Use cases for the Yalwa Email Scraper

Be honest about scope. These are the jobs the Yalwa Email Scraper can genuinely do.

Use case	Who runs it	Typical setup
Legacy citation audit	Local SEO consultant	Client name or trade plus location: "Leeds"
Directory coverage matrix	Market researcher	Same keyword across several sibling Actors
Stale-listing cleanup	Reputation manager	Check whether outdated details still sit on Yalwa
Long-tail completeness sweep	Local marketing agency	Run last, after the high-yield directories
Index-availability probe	Data engineer	One keyword, one city, maxEmails: 20
Configuration smoke test	Developer	Verify proxy and input wiring end to end

For real volume, the Fyple, Brownbook, Cylex, N49 and Yellow Pages Actors are the right choices.

What to expect from a Yalwa Email Scraper run

Our measured Google run of the Yalwa Email Scraper parsed 1 result block. Yalwa has a small and ageing indexed footprint, so expect very low volume.

For contrast, the same code returned 9 blocks and 9 unique emails on Brownbook, and 10 and 10 on N49 and Fyple. The difference is entirely the source.

If you need to answer "did we check Yalwa?", one run does it. If you need a thousand contacts, this is not the Yalwa Email Scraper.

Responsible use, GDPR and CAN-SPAM

Any address the Yalwa Email Scraper returns was published on a public business listing. Sending obligations remain yours, and this section is guidance rather than legal advice.

Because yalwa.co.uk covers Britain, GDPR and UK GDPR matter here: you need a lawful basis, a clear privacy notice and a route to erasure. PECR also governs UK electronic marketing.

CAN-SPAM applies to US recipients - accurate headers, an honest subject line, a physical postal address and a prompt opt-out. Ageing listings raise a practical risk too: an address may belong to someone who left the business years ago.

Suppress opt-outs, record provenance, verify before sending, and do not resell the raw dataset.

Limitations of the Yalwa Email Scraper

• Yalwa has a small and ageing indexed footprint, so expect very low volume. Our measured run of the Yalwa Email Scraper parsed 1 result block.
• Listings can be stale, so contact details may be years out of date. Verify before any high-value outreach.
• Only finds businesses whose email is publicly visible in Google's index.
• Google caps a single query at roughly 300 results, which is why query expansion exists - though the index limit binds first here.
• possiblyTruncated: true means Google's snippet ellipsis touched the address - verify before sending.
• username and profileUrl are populated only when Google's result exposes a handle. Expect many rows with username: null and an empty profileUrl. This is a Google limitation, not a bug.
• Requires the Apify GOOGLE_SERP proxy; the Yalwa Email Scraper 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, and no volume is guaranteed.

Yalwa Email Scraper FAQ

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

Very few. Our measured run parsed 1 result block. Yalwa has a small and ageing indexed footprint, so expect very low volume.

Is an empty dataset a bug?

No. It is a realistic outcome for the Yalwa Email Scraper given how little of Yalwa is indexed today.

What should I run instead for volume?

The Fyple Email Scraper, Brownbook Email Scraper, Cylex Actor and N49 Actor all returned 9 or 10 blocks in our measured runs. The Yalwa Email Scraper returned one.

Which domains does it search?

yalwa.com and yalwa.co.uk, both in the same run.

Does the Yalwa Email Scraper use a Yalwa API?

No. It never logs in, never calls an API and never opens the Yalwa website. Everything comes from publicly indexed Google results.

Will adding keywords or domains help?

Only marginally. Neither can expand an index that is genuinely small and ageing.

Why is username usually null?

Google rarely exposes an attributable handle for these pages. Those rows still carry accountName and any email found.

How reliable is the data?

Treat it as potentially stale. Yalwa listings can be years old, so verify anything you intend to act on.

Do I need Apify proxy credentials?

Yes. The Yalwa Email Scraper runs on the Apify GOOGLE_SERP proxy and cannot operate without it.

Does the free plan matter here?

Rarely. The 100-email run cap is almost never the binding constraint on the Yalwa Email Scraper.

Can a run resume after a migration?

Yes. State lives in the key-value store keyed by an input hash and is saved on PERSIST_STATE, MIGRATING and ABORTING events.

Related Actors

Actor	What it collects
Angi Email Scraper	Public contact emails from Angi
Bark Email Scraper	Public contact emails from Bark
Better Business Bureau Email Scraper	Public contact emails from Better Business Bureau
Bizapedia Email Scraper	Public contact emails from Bizapedia
Brownbook Email Scraper	Public contact emails from Brownbook
Callupcontact Email Scraper	Public contact emails from CallUpContact
Capterra Email Scraper	Public contact emails from Capterra
Clutch Email Scraper	Public contact emails from Clutch
Crunchbase Email Scraper	Public contact emails from Crunchbase
Cybo Email Scraper	Public contact emails from Cybo
Cylex Email Scraper	Public contact emails from Cylex
EC21 Email Scraper	Public contact emails from EC21
Europages Email Scraper	Public contact emails from Europages
ExportHub Email Scraper	Public contact emails from ExportHub
FindUsLocal Email Scraper	Public contact emails from FindUsLocal
Foursquare Email Scraper	Public contact emails from Foursquare
Fyple Email Scraper	Public contact emails from Fyple
G2 Email Scraper	Public contact emails from G2
Hotfrog Email Scraper	Public contact emails from Hotfrog
Houzz Email Scraper	Public contact emails from Houzz
Infobel Email Scraper	Public contact emails from Infobel
Kompass Email Scraper	Public contact emails from Kompass
Lacartes Email Scraper	Public contact emails from Lacartes
Manta Email Scraper	Public contact emails from Manta
MapQuest Email Scraper	Public contact emails from MapQuest
N49 Email Scraper	Public contact emails from N49
Porch Email Scraper	Public contact emails from Porch
Scoot Email Scraper	Public contact emails from Scoot
Thomasnet Email Scraper	Public contact emails from Thomasnet
Thumbtack Email Scraper	Public contact emails from Thumbtack
Touch Local Email Scraper	Public contact emails from Touch Local
TradeIndia Email Scraper	Public contact emails from TradeIndia
Trustpilot Email Scraper	Public contact emails from Trustpilot
Tupalo Email Scraper	Public contact emails from Tupalo
Yellow Pages Email Scraper	Public contact emails from Yellow Pages
Angi Email and Phone Number Scraper	Emails and phone numbers from Angi
Bark Email and Phone Number Scraper	Emails and phone numbers from Bark
Better Business Bureau Email and Phone Number Scraper	Emails and phone numbers from Better Business Bureau
Bizapedia Email and Phone Number Scraper	Emails and phone numbers from Bizapedia
Brownbook Email and Phone Number Scraper	Emails and phone numbers from Brownbook
CallUpContact Email and Phone Number Scraper	Emails and phone numbers from CallUpContact
Capterra Email and Phone Number Scraper	Emails and phone numbers from Capterra

Leave a review

If the Yalwa 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.