Goodreads Email Scraper

Goodreads Email Scraper

Goodreads Email Scraper — Author, Reviewer and Book Blogger Contact Emails

The Goodreads Email Scraper finds publicly indexed contact emails on Goodreads and delivers them as a structured, exportable dataset.

Book marketing runs on email. Indie authors need ARC readers, publicists need reviewers, and book bloggers need authors — and Goodreads is where all three groups describe themselves in public.

The Goodreads Email Scraper searches goodreads.com through Google, filters for the email domains you choose, and returns account names, display names, profile URLs and the bio or post snippet each address came from.

Plenty of Goodreads users publish a contact address deliberately: reviewers listing review-request instructions, authors inviting press enquiries, group threads where members post an email to receive advance copies.

The Goodreads Email Scraper is a Goodreads email extractor built for book publicity, ARC reviewer outreach, author lead generation and literary market research.

Important: this Goodreads Email Scraper never logs into Goodreads, never uses the Goodreads API, and never opens goodreads.com itself. Every record comes from publicly indexed Google search results.

---

Key Features of the Goodreads Email Scraper

Every feature below is genuine crawler behaviour.

Feature	What it means in practice
Google site: search collection	The Goodreads Email Scraper restricts every query to goodreads.com, so only Goodreads pages are parsed
Query expansion	Each keyword × domain pair runs as base, quoted, intitle: and one variant per query modifier
Book-aware default modifiers	email, contact, review copy, publicity and arc are tuned to how Goodreads users phrase contact invitations
Domain-filtered extraction	Only addresses ending in your customDomains list are kept
Global deduplication	An email is written once per run, across every query and page
Obfuscation-aware parser	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 address in the same block
Structural HTML parsing	Finds the <h3> title then the smallest surrounding block — independent of Google's CSS class names
Whole-page fallback parser	A markup change degrades output to "emails without account metadata" rather than "no emails"
Concurrency	An asyncio worker pool runs queries in parallel with a shared stop signal on maxEmails
Retry logic	Up to 3 attempts per page, exponential backoff, a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Blocked-query requeue	Blocked or failed queries get one more attempt at the end of the run
Resumable state	Key-value-store checkpoints keyed by an input hash, flushed on PERSIST_STATE, MIGRATING and ABORTING
Streaming dataset writes	Each lead is pushed to the Apify dataset the moment it is extracted
Run summary	Pages fetched, blocked pages, retries and emails per page are logged

---

How the Goodreads Email Scraper Works

The Goodreads Email Scraper pipeline has six steps and no hidden machinery. No browser, no JavaScript rendering, no authentication, no cookies.

1. Read input. Keywords, optional location, email domains and run limits are loaded.

2. Build queries. Google queries are composed with the site: operator, for example site:goodreads.com book blogger "@gmail.com" "review copy".

3. Fetch search results. Pages are requested asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, with proxy rotation and retry logic on every request.

4. Parse result blocks. The Goodreads Email Scraper locates each <h3> heading, walks up to the tightest enclosing block, and reads title, site label and snippet.

5. Extract and normalise emails. A domain-filtered regex pulls candidate addresses; normalisation, obfuscation handling and the junk filter clean the rest.

6. Deduplicate and push. Unique addresses stream into the dataset immediately, so you can export while the run continues.

Base queries execute before expanded variants, so the earliest rows the Goodreads Email Scraper writes are usually the most on-target.

---

What Data Does the Goodreads Email Scraper Extract?

Each dataset item is one unique email address described by 14 structured fields.

Alongside the address you get the account label Google printed, a parsed display name, the handle where Goodreads exposes one, a canonical profile URL and the snippet the address appeared in.

The snippet is unusually valuable here. On Goodreads it often contains the reviewer's genre preferences or the author's publicity terms, which lets you segment before you write a single email.

Provenance is included: the keyword and the exact Google query behind each lead, plus a UTC timestamp.

The Goodreads Email Scraper collects nothing beyond these fields — no shelves, no ratings, no friend lists, no private data.

---

Goodreads Email Scraper Input Schema

Every field below is taken verbatim from the Goodreads Email Scraper input schema.

Field	Type	Default	Description
keywords	array (required)	["author", "book blogger"]	Search terms describing the Goodreads accounts you want (niche, genre, role)
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are collected; leading @ 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 (US, GB, DE…)
expandQueries	boolean	true	Search each keyword × domain pair with several phrasings
queryModifiers	array	["email", "contact", "review copy", "publicity", "arc"]	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

JSON input example

{
  "keywords": ["romantasy reviewer", "indie author", "book blogger"],
  "location": "United Kingdom",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 500,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "review copy", "publicity", "arc"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

---

Goodreads Email Scraper Output Schema

Every dataset item produced by the Goodreads Email Scraper carries all 14 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 (handle or display name)
fullName	Display name parsed from a profile-style title; empty for post captions
username	URL-safe handle when Goodreads 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 or post snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain (e.g. @gmail.com)
possiblyTruncated	true when Google's snippet ellipsis touched the email — verify before sending
foundAt	ISO 8601 UTC timestamp

JSON output example

{
  "network": "Goodreads",
  "keyword": "romantasy reviewer",
  "query": "site:goodreads.com romantasy reviewer \"@gmail.com\" arc",
  "title": "Hannah Pryce (Bristol, United Kingdom)'s Reviews - Goodreads",
  "accountName": "Hannah Pryce",
  "fullName": "Hannah Pryce",
  "username": "48210377-hannah-pryce",
  "profileUrl": "https://www.goodreads.com/user/show/48210377-hannah-pryce",
  "url": "https://www.goodreads.com/user/show/48210377-hannah-pryce",
  "description": "Romantasy and dark academia. Open to ARC requests, EPUB only, honest reviews. Contact: hannah.reads.arc@gmail.com",
  "email": "hannah.reads.arc@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T13:26:05Z"
}

---

How to Use the Goodreads Email Scraper

Step 1 — open the Actor. Launch the Goodreads Email Scraper from the Apify Store.

Step 2 — use genre-level keywords. cozy mystery reviewer, YA fantasy blogger and historical fiction author outperform books by a wide margin.

Step 3 — pick email domains. @gmail.com covers most reviewers. Add @outlook.com, @hotmail.com and @yahoo.com for broader coverage of long-standing accounts.

Step 4 — keep the book-specific modifiers. review copy, publicity and arc are what make the Goodreads Email Scraper surface reviewers actively inviting contact.

Step 5 — run and export. Take the dataset as JSON, CSV or XLSX, or pull it via the Apify API into your mailing tool.

Reviewers overlap heavily across platforms, so many teams pair the Goodreads Email Scraper with the Substack Email Scraper for book newsletters and the Tumblr Email Scraper for fandom-side book bloggers.

---

Use Cases for the Goodreads Email Scraper

Use case	How the Goodreads Email Scraper helps
ARC and review-copy campaigns	Find reviewers who publicly invite advance copy requests
Indie author book launches	Build a genre-matched reviewer list before release day
Book publicity and PR	Assemble press contacts for a title or an imprint
Literary agent prospecting	Identify authors publishing enquiry addresses
Book blogger outreach	Contact bloggers whose stated genres match your catalogue
Bookstagram and BookTok crossover	Locate reviewers who list contact details on Goodreads
Audiobook promotion	Reach reviewers open to audio review copies
Publisher market research	Study how a genre's readers describe what they want
Blurb and endorsement requests	Reach authors in an adjacent subgenre
CRM enrichment	Attach Goodreads profile URLs to reviewer records you already hold

Book publishing is one of the few niches where cold email is genuinely welcome — provided the pitch matches the reviewer's stated genre.

That is precisely what the Goodreads Email Scraper enables, because the description field tells you what each reviewer actually reads.

---

Why Choose This Goodreads Email Scraper

It is tuned for books. The default query modifiers reflect real Goodreads phrasing: review copy, publicity, ARC.

It is honest about its source. The Goodreads Email Scraper reads Google's public index. No API key, no login, no private data.

It is resilient. Structural parsing plus a whole-page fallback keeps the crawler producing data when Google's markup shifts.

It is resumable. Aborts and migrations are checkpointed, keyed by a hash of your input.

It is precise. Domain filtering, boundary-correct matching, obfuscation handling and the junk filter keep the dataset clean.

It has siblings. The same engine drives the Medium Email Scraper for essayists and the Reddit Email Scraper for book communities like r/books and r/fantasy.

---

Limitations

These constraints are real. None of them are bugs.

• Only publicly indexed emails. If an address is not in Google's index, the Goodreads Email Scraper cannot find it. Private data is never accessed.
• Google's ~300-result cap. A single query returns roughly 300 results at most. Query expansion exists to work around this — keep expandQueries on.
• possiblyTruncated. A true value means Google's snippet ellipsis may have clipped the address. Verify those rows before sending.
• Apify GOOGLE_SERP proxy required. The Goodreads Email Scraper cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans are limited to 100 emails per run; paid plans are uncapped.
• username and profileUrl availability. Populated only when Google's result exposes a handle. Some Goodreads rows show a display name only, leaving username and profileUrl empty. That is a Google limitation, not a defect.
• No guaranteed volume. Yield varies with genre keywords, email domains and location.

The Goodreads Email Scraper is independent and not affiliated with, endorsed by or officially supported by Goodreads or Amazon.

---

Related Actors

Actor	What it collects
Goodreads Email and Phone Number Scraper	Emails and phone numbers from Goodreads
Goodreads Phone Number Scraper	Public phone numbers from Goodreads
Behance Email Scraper	Public contact emails from Behance
Bigo Live Email Scraper	Public contact emails from Bigo Live
Bluesky Email Scraper	Public contact emails from Bluesky
Bumble Email Scraper	Public contact emails from Bumble
Clubhouse Email Scraper	Public contact emails from Clubhouse
Dailymotion Email Scraper	Public contact emails from Dailymotion
DeviantArt Email Scraper	Public contact emails from DeviantArt
Discord Email Scraper	Public contact emails from Discord
Dribbble Email Scraper	Public contact emails from Dribbble
Facebook Email Scraper	Public contact emails from Facebook
Hinge Email Scraper	Public contact emails from Hinge
Instagram Email Scraper	Public contact emails from Instagram
KakaoTalk Email Scraper	Public contact emails from KakaoTalk
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LINE Email Scraper	Public contact emails from LINE
LinkedIn Email Scraper	Public contact emails from LinkedIn
Mastodon Email Scraper	Public contact emails from Mastodon
Medium Email Scraper	Public contact emails from Medium
Mixcloud Email Scraper	Public contact emails from Mixcloud
Patreon Email Scraper	Public contact emails from Patreon
Pinterest Email Scraper	Public contact emails from Pinterest
Quora Email Scraper	Public contact emails from Quora
Reddit Email Scraper	Public contact emails from Reddit
Rumble Email Scraper	Public contact emails from Rumble
Snapchat Email Scraper	Public contact emails from Snapchat
SoundCloud Email Scraper	Public contact emails from SoundCloud
Substack Email Scraper	Public contact emails from Substack
Telegram Email Scraper	Public contact emails from Telegram
Threads Email Scraper	Public contact emails from Threads
TikTok Email Scraper	Public contact emails from TikTok
Tinder Email Scraper	Public contact emails from Tinder
Tumblr Email Scraper	Public contact emails from Tumblr
Twitch Email Scraper	Public contact emails from Twitch
Vimeo Email Scraper	Public contact emails from Vimeo
VK Email Scraper	Public contact emails from VK
WeChat Email Scraper	Public contact emails from WeChat
Weibo Email Scraper	Public contact emails from Weibo
X Email Scraper	Public contact emails from X

Goodreads Email Scraper Example Run

A small press is launching a debut cosy fantasy and needs 200 genre-matched reviewers.

They run the Goodreads Email Scraper with keywords: ["cozy fantasy reviewer", "fantasy book blogger"], customDomains: ["@gmail.com", "@outlook.com"], the default book modifiers, and maxEmails: 400.

Query expansion multiplies two keywords into a dozen phrasings, and the crawler paginates through Google collecting reviewer bios and thread posts.

They discard rows flagged possiblyTruncated, read the description field to filter for reviewers who accept EPUB ARCs, and export the shortlist as CSV.

---

Goodreads Email Scraper FAQ

Does the Goodreads Email Scraper log into Goodreads?

No. It never logs in, never uses the Goodreads API, and never opens goodreads.com. All data comes from publicly indexed Google search results.

Where do the emails come from?

From Google result titles, site labels and snippets — typically reviewer bios, author pages and group threads where someone published a contact address themselves.

Can it find author emails specifically?

It finds whatever Google has indexed. Use author-oriented keywords and the publicity modifier to bias results toward author pages rather than reviewer profiles.

Do I need an Apify proxy?

Yes. The Goodreads Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

How many emails can I collect per run?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by maxEmails and Google's index.

Why is username empty on some rows?

Google did not expose a handle in that result. Those rows still carry accountName, fullName and the snippet. It is a Google limitation, not a scraper defect.

What does possiblyTruncated: true mean?

Google's snippet ellipsis touched the address, so it may be incomplete. Verify those rows before sending.

Should I keep query expansion enabled?

Yes. Google caps a single query at roughly 300 results, and expansion is how the Goodreads Email Scraper reaches past that ceiling.

Can I change the query modifiers?

Yes. Replace review copy, publicity and arc with terms fitting your campaign — beta reader, blog tour or street team, for example.

Does the Goodreads Email Scraper deduplicate?

Yes, globally. Each address appears once per run no matter how many queries surfaced it.

What happens if a run is interrupted?

Progress is checkpointed in the key-value store, keyed by a hash of your input, and flushed on PERSIST_STATE, MIGRATING and ABORTING. Restarting resumes.

Is this affiliated with Goodreads?

No. The Goodreads Email Scraper is independent and is not affiliated with, endorsed by or officially supported by Goodreads or Amazon.

How should I use the results responsibly?

Follow GDPR, CAN-SPAM and local law. Reviewers publish contact details for relevant requests — respect stated genres, formats and opt-outs.

---

Leave a review

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

Support

Questions, bug reports or a custom build request? Email neurodata.apify@gmail.com and include your run ID so the Goodreads Email Scraper logs can be checked.