Rotten Tomatoes Email Scraper

Rotten Tomatoes Email Scraper

The Rotten Tomatoes Email Scraper collects publicly indexed contact emails from Rotten Tomatoes critic and title pages. It searches Google for rottentomatoes.com results and extracts the addresses those pages already print.

One thing to say up front before you run the Rotten Tomatoes Email Scraper: Rotten Tomatoes publishes critic and title pages that rarely include an email, so expect low volume. The site is a review aggregator, not a contact directory, and most critic pages list outlet and review links rather than an address.

That said, the pages do resolve cleanly. In a measured live run, ten parsed Google result blocks produced ten identified critics or titles, ten profile URLs and seven unique emails, so the Rotten Tomatoes Email Scraper does return usable rows when the keywords are right.

The Actor never logs into Rotten Tomatoes, never calls a Fandango or Rotten Tomatoes API and never opens the website. Every field comes from a public Google result block: title, snippet and site label.

What the Rotten Tomatoes Email Scraper is for

Film and TV publicists spend real effort assembling critic lists for screeners, embargo notices and festival invitations. The Rotten Tomatoes Email Scraper is a way to seed that list from the largest public index of working critics.

Its audiences are film and TV publicists, festival programmers, independent distributors, entertainment PR firms, and media researchers studying critic coverage. For all of them the Rotten Tomatoes Email Scraper answers one question: which critics on this site have published a way to reach them?

Treat it as a discovery layer rather than a finished media list. It surfaces names, outlets and profile URLs reliably, and an email whenever the indexed text happens to carry one.

Who gets the most out of it

Audience	What they use the Rotten Tomatoes Email Scraper for
Film publicists	Seed a critic list for screener and embargo outreach
Independent distributors	Find reviewers covering a genre before a release
Festival programmers	Identify critics who cover festival titles
Entertainment PR firms	Build outlet-by-outlet coverage maps
Awards campaigners	Track which critics publish reachable contact details
Media researchers	Measure contact transparency across the critic pool

How the Rotten Tomatoes Email Scraper works

The pipeline is short and fully inspectable. The Rotten Tomatoes Email Scraper builds Google queries with the site: operator, fetches result pages through the Apify GOOGLE_SERP proxy using async aiohttp, and reads emails from the returned text.

A base query looks like site:rottentomatoes.com film critic "@gmail.com", with your location phrase appended when you supply one.

Each page is parsed structurally rather than by CSS class name. The parser finds the <h3> result title, walks up to the smallest surrounding block, and reads title, snippet and site label from that block.

Emails are matched with a domain-filtered regex, normalised, deduplicated globally, and pushed to the dataset immediately. There is no browser, no JavaScript rendering, no authentication and no cookies in the Rotten Tomatoes Email Scraper.

Query expansion

Google caps one query at roughly 300 results, so coverage comes from query diversity rather than pagination depth. The Rotten Tomatoes Email Scraper runs a base query first, then a quoted variant, an intitle: variant, and one variant per query modifier.

The default modifiers are email, contact, press, booking and submissions. On a low-yield platform those modifier variants matter more than usual, because they push queries toward the rare pages that do carry an address.

Turning expandQueries off is a bad idea here. Without expansion the Rotten Tomatoes Email Scraper has only one query per keyword and domain pair to work with.

Email extraction quality

Matching is case-insensitive and understands obfuscated forms such as name [at] domain [dot] com, name (at) domain, name @ domain.com and domain .com. Zero-width characters and the full-width ＠ sign are handled.

A junk filter rejects placeholders like email@, yourname@, test@ and xxx@, along with single-character local parts. Boundary-correct matching means @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 address in the same block, so the Rotten Tomatoes Email Scraper writes fewer, cleaner rows.

Rotten Tomatoes Email Scraper features

Every feature below is shared engine behaviour, applied to rottentomatoes.com pages.

Feature	What it means in practice
Google site:rottentomatoes.com search	Covers critic, celebrity, movie and TV paths in one pass
Query expansion	Base, quoted, intitle: and one variant per modifier; base runs first
Global deduplication	Each email appears once across every query and page
Obfuscation handling	Reads [at], (at), spaced @, [dot] and full-width ＠ forms
Junk filter	Drops placeholder and single-character addresses
Structural block parsing	Independent of Google's CSS class names
Whole-page fallback parser	A layout change degrades to emails without account details, not to zero
Block detection	CAPTCHA, unusual-traffic and consent pages are retried, not counted as empty
Retries with backoff	Up to 3 attempts per page, fresh proxy session each request
Requeue of failures	Blocked or failed queries are retried once at the end of the run
Resumable state	Progress stored in the key-value store, keyed by a hash of your input
Migration-safe saves	State saves on PERSIST_STATE, MIGRATING and ABORTING
Concurrency control	An asyncio worker pool with a shared stop signal on maxEmails
Run summary logging	Pages fetched, blocked pages, retries and emails per page

Input for the Rotten Tomatoes Email Scraper

Only keywords is required. Every other input to the Rotten Tomatoes Email Scraper has a default tuned for this platform.

Field	Type	Default	Meaning
keywords	array (required)	["film critic", "reviewer"]	Search terms describing the critics or titles 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 in several phrasings
queryModifiers	array	["email","contact","press","booking","submissions"]	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

An independent distributor preparing a horror release:

{
  "keywords": ["horror film critic", "genre reviewer", "festival critic"],
  "location": "",
  "customDomains": ["@gmail.com", "@outlook.com", "@yahoo.com"],
  "maxEmails": 100,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "press", "screener", "submissions"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Genre and beat keywords beat generic ones. documentary critic gives the Rotten Tomatoes Email Scraper more to work with than critic.

Output from the Rotten Tomatoes Email Scraper

Every dataset item the Rotten Tomatoes Email Scraper writes carries all fourteen fields below, and nothing else.

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/caption 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 row

{
  "network": "Rotten Tomatoes",
  "keyword": "horror film critic",
  "query": "site:rottentomatoes.com horror film critic press \"@gmail.com\"",
  "title": "Dana Whitfield | Rotten Tomatoes",
  "accountName": "Dana Whitfield",
  "fullName": "Dana Whitfield",
  "username": "dana-whitfield",
  "profileUrl": "https://www.rottentomatoes.com/celebrity/dana-whitfield",
  "url": "https://www.rottentomatoes.com/celebrity/dana-whitfield",
  "description": "Genre film critic and festival reporter. Screener requests: danawhitfield.reviews@gmail.com",
  "email": "danawhitfield.reviews@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T12:41:18Z"
}

Rotten Tomatoes exposes readable slugs on celebrity and critic paths, so the Rotten Tomatoes Email Scraper usually resolves username and profileUrl. All ten rows in the live test run had a usable profile URL.

Use cases for the Rotten Tomatoes Email Scraper

Most teams run the Rotten Tomatoes Email Scraper in one of these shapes.

Use case	How to run it
Screener outreach	Genre keywords plus press and screener modifiers
Embargo list building	Beat keywords, maxEmails around 100
Festival press invitations	Keywords like festival critic, film journalist
Awards campaign mapping	Track which critics list a reachable address
Distributor prospecting	Genre-by-genre runs before a slate announcement
Coverage research	Compare critic contact rates by beat or country

Examples: running the Rotten Tomatoes Email Scraper

Genre screener list. Keywords horror film critic, thriller reviewer. Domains @gmail.com and @outlook.com, maxEmails 100.

International critic sweep. The same keywords with countryCode set to GB and local domains added. The Rotten Tomatoes Email Scraper then favours UK-indexed results.

Documentary campaign. Keywords documentary critic, nonfiction reviewer, modifiers narrowed to press, contact, screener.

Title-side research. Keywords naming a genre or franchise, to see which title pages carry a press or distribution address at all. This is where the Rotten Tomatoes Email Scraper is most clearly a research tool rather than a lead source.

Tips for better results with the Rotten Tomatoes Email Scraper

Because volume is low here, keyword precision matters more than on the podcast Actors. Use beat and genre language a critic page would actually contain.

Add plenty of domains. Working critics frequently use a publication domain rather than a free provider, and the Rotten Tomatoes Email Scraper only keeps addresses on domains you list.

Leave expandQueries on and keep maxPagesPerQuery at the default. Depth costs little, and a low-yield platform is exactly where the Rotten Tomatoes Email Scraper benefits from it most.

Raise maxEmails above what you actually need. The Rotten Tomatoes Email Scraper stops on that ceiling, and on this platform you are far more likely to exhaust the query set than to hit it.

If your real goal is volume rather than critics specifically, the podcast Actors are a better source. The iTunes Podcast Host Email Scraper had the highest measured yield in this family.

Limitations of the Rotten Tomatoes Email Scraper

Rotten Tomatoes publishes critic and title pages that rarely include an email, so expect low volume. This is the single most important constraint on the Actor.

The Rotten Tomatoes Email Scraper only finds pages whose email is publicly visible in Google's index. A critic reachable only through their outlet's contact form will not appear.

Google caps a single query at roughly 300 results, which is why query expansion exists and is on by default.

username and profileUrl are only populated when Google's result exposes a usable handle. Some rows carry only accountName and fullName; that is a Google limitation, not a bug.

Rows flagged possiblyTruncated: true may have had the address clipped by Google's snippet ellipsis. Verify those before sending.

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, and no volume is guaranteed. The seven-emails-from-ten-blocks figure was one measured run, not a promise.

The Rotten Tomatoes Email Scraper is not affiliated with, endorsed by or supported by Rotten Tomatoes or Fandango.

Responsible use

Critics are individuals, and a screener pitch to the wrong inbox is exactly the kind of unsolicited mail that damages a campaign. Anything the Rotten Tomatoes Email Scraper returns is personal data and should be handled that way. Under GDPR you need a lawful basis for processing personal data and must honour deletion requests.

Under CAN-SPAM your commercial email needs accurate headers, a real physical address and a working opt-out. Keep pitches relevant to the critic's actual beat and easy to unsubscribe from.

This is general guidance, not legal advice. Confirm your own obligations before running a campaign.

Related Actors

Actor	What it collects
Rotten Tomatoes Email and Phone Number Scraper	Emails and phone numbers from Rotten Tomatoes
Rotten Tomatoes Phone Number Scraper	Public phone numbers from Rotten Tomatoes
ArtStation Email Scraper	Public contact emails from ArtStation
arXiv Email Scraper	Public contact emails from arXiv
Blogger Email Scraper	Public contact emails from Blogger
Crunchyroll Email Scraper	Public contact emails from Crunchyroll
Digg Email Scraper	Public contact emails from Digg
Flipboard Email Scraper	Public contact emails from Flipboard
iHeartRadio Email Scraper	Public contact emails from iHeartRadio
IMDb Email Scraper	Public contact emails from IMDb
Internet Archive Email Scraper	Public contact emails from Internet Archive
iTunes Podcast Host Email Scraper	Public contact emails from Apple Podcasts
Netflix Shows Email Scraper	Public contact emails from Netflix
Scribd Email Scraper	Public contact emails from Scribd
Spotify Email Scraper	Public contact emails from Spotify
Spotify Playlist Email Scraper	Public contact emails from Spotify
TuneIn Email Scraper	Public contact emails from TuneIn
Wikipedia Contact Email Scraper	Public contact emails from Wikipedia
WordPress Blog Email Scraper	Public contact emails from WordPress.com
ArtStation Email and Phone Number Scraper	Emails and phone numbers from ArtStation
arXiv Email and Phone Number Scraper	Emails and phone numbers from arXiv
Blogger Email and Phone Number Scraper	Emails and phone numbers from Blogger
Crunchyroll Email and Phone Number Scraper	Emails and phone numbers from Crunchyroll
Digg Email and Phone Number Scraper	Emails and phone numbers from Digg
Flipboard Email and Phone Number Scraper	Emails and phone numbers from Flipboard
iHeartRadio Email and Phone Number Scraper	Emails and phone numbers from iHeartRadio
IMDb Email and Phone Number Scraper	Emails and phone numbers from IMDb
Internet Archive Email and Phone Number Scraper	Emails and phone numbers from Internet Archive
Apple Podcasts Email and Phone Number Scraper	Emails and phone numbers from Apple Podcasts
Netflix Email and Phone Number Scraper	Emails and phone numbers from Netflix
Scribd Email and Phone Number Scraper	Emails and phone numbers from Scribd
Spotify Email and Phone Number Scraper	Emails and phone numbers from Spotify
Spotify Email and Phone Number Scraper	Emails and phone numbers from Spotify
TuneIn Email and Phone Number Scraper	Emails and phone numbers from TuneIn
Wikipedia Email and Phone Number Scraper	Emails and phone numbers from Wikipedia
ArtStation Phone Number Scraper	Public phone numbers from ArtStation
arXiv Phone Number Scraper	Public phone numbers from arXiv
Blogger Phone Number Scraper	Public phone numbers from Blogger
Crunchyroll Phone Number Scraper	Public phone numbers from Crunchyroll
Digg Phone Number Scraper	Public phone numbers from Digg
Flipboard Phone Number Scraper	Public phone numbers from Flipboard
iHeartRadio Phone Number Scraper	Public phone numbers from iHeartRadio

FAQ about the Rotten Tomatoes Email Scraper

How many results should I expect from the Rotten Tomatoes Email Scraper?

Expect low volume. Rotten Tomatoes publishes critic and title pages that rarely include an email. A measured live run still produced ten identified critics, ten profile URLs and seven unique emails from ten parsed blocks, but yield swings hard with your keywords and domains, and no volume is guaranteed.

Why does it resolve names and URLs so well but return fewer emails?

Because identity is on the page and contact details usually are not. Rotten Tomatoes prints a critic's name, outlet and review history, so the Rotten Tomatoes Email Scraper can almost always build username and profileUrl even when there is no address to find.

Is this a critic contact database?

No. It is a discovery tool that reports emails present in Google's public index. Treat it as a seed for a media list you still verify and enrich.

Does the Rotten Tomatoes Email Scraper log into Rotten Tomatoes?

No. There is no login, no API call, no browser and no cookies. Everything comes from public Google search results.

Can I collect emails on a publication domain?

Yes, and you should. Add domains like @variety.com or @indiewire.com to customDomains; only addresses ending in a listed domain are kept.

What does possiblyTruncated: true mean?

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

Why is username sometimes null?

Google did not expose a usable handle for that result. The Rotten Tomatoes Email Scraper still writes accountName, fullName, description and the email.

Will it run without the Apify proxy?

No. The Rotten Tomatoes Email Scraper depends on the Apify GOOGLE_SERP proxy and will not start without Apify proxy credentials.

Is there a free-plan limit?

Yes. Free Apify plans stop at 100 emails per run. Paid plans are uncapped, subject to your maxEmails setting.

Can I resume an interrupted run?

Yes. State is stored in the key-value store keyed by a hash of your input, and saved on Apify's PERSIST_STATE, MIGRATING and ABORTING events.

What should I run if I need higher volume?

The podcast Actors. iTunes Podcast Host Email Scraper, iHeartRadio Email Scraper and TuneIn Email Scraper all measured higher, because podcast pages publish contact details deliberately.

Is it affiliated with Rotten Tomatoes?

No. It is an independent tool reading public search results, not an official or endorsed product.

Leave a review

If the Rotten Tomatoes 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 request for a custom build of the Rotten Tomatoes Email Scraper? Email neurodata.apify@gmail.com.