Zomato Email Scraper

Zomato Email Scraper

The Zomato Email Scraper collects publicly indexed contact emails connected to zomato.com, the restaurant discovery platform that dominates India and has a large footprint in the UAE. It builds Google queries with the site:zomato.com operator, fetches them through the Apify GOOGLE_SERP proxy, and extracts emails from the result blocks. No login, no browser, no Zomato API — only what Google has already published in its index.

Start with the honest part. Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle. In a live test run, roughly 10 parsed results produced 8 unique emails but only 2 rows with a usable venue identity and 2 resolvable profile URLs.

So the Zomato Email Scraper is email-dense and identity-thin. If your workflow keys on the address itself — deduplication, CRM matching, cold outreach — that trade is fine. If you need a clean restaurant name on every row, plan enrichment or use a sibling Actor alongside it.

What one run of the Zomato Email Scraper produces

Each dataset row is one unique email plus whatever context Google printed around it. You get the raw title, an account label where one exists, a cleaned snippet, the exact query used and a truncation flag. The Zomato Email Scraper pushes rows to the Apify dataset as they are found, so you can export CSV, JSON or Excel mid-run.

Exporting and integrating the Zomato Email Scraper dataset

Because rows are written incrementally, an aborted or migrated run still leaves a usable dataset behind. Export from the Apify console, pull the dataset over the API, or schedule the Zomato Email Scraper and push results straight into your CRM.

How the Zomato Email Scraper works: Google SERP parsing, not an API

The Zomato Email Scraper runs the same six steps on every query it builds.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the site: operator, for example site:zomato.com dhaba "@gmail.com" catering.
3. It fetches result pages through the Apify GOOGLE_SERP proxy using async aiohttp requests.
4. It parses each result block structurally — locating the <h3> and the smallest surrounding block — rather than by CSS class name.
5. It extracts emails with a domain-filtered regex and normalises obfuscated forms.
6. It deduplicates globally and pushes each lead to the dataset immediately.

There is no browser, no JavaScript rendering, no authentication and no cookies. The Zomato Email Scraper never signs into Zomato and never requests pages from Zomato's own servers. Everything it returns was already public in Google's search index.

Local keywords and countryCode in the Zomato Email Scraper

countryCode and locally-worded keywords are the two real levers you have on this platform, and most disappointing runs come from ignoring both. Zomato's index is concentrated in India and the UAE, and Google personalises results by country vantage point.

Set countryCode to IN for India or AE for the UAE, and run them as separate jobs. A default or US-vantage search will bury zomato.com pages behind global results and cut your row count sharply.

Keyword suggestions for the Zomato Email Scraper

The shipped defaults — restaurant and cafe — are broad starting points. Local format and cuisine words match far more of the index.

Keyword	Why it works on Zomato
dhaba	The Indian roadside diner format, densely listed
biryani	One of the highest-volume cuisine terms in the index
thali	Everyday dining pages across tier-1 and tier-2 cities
tiffin	Meal-subscription and home-kitchen businesses
cloud kitchen	Delivery-only operators, a fast-growing segment
bakery	Bakeries and dessert shops with catering inboxes
sweet shop	Mithai businesses that publish bulk-order addresses
shawarma	A high-density UAE term when countryCode is AE

Pair a cuisine or format noun with an intent modifier — biryani catering, cloud kitchen owner — instead of searching a bare noun.

Email domains worth testing for the Zomato Email Scraper

The default customDomains are @gmail.com and @yahoo.com. Gmail dominates Indian small-business contact details and should stay. The rest are suggestions based on how these markets publish addresses, not guarantees of volume.

Domain	Why add it
@gmail.com	Keep — the default business inbox across India and the UAE
@rediffmail.com	Long-established Indian provider, common on older listings
@yahoo.co.in	The Indian Yahoo address
@hotmail.com	Widely used by older UAE and Indian businesses
@outlook.com	Increasingly common for newer restaurant groups

Each extra domain multiplies the query count, because the Zomato Email Scraper searches every keyword against every domain. Three or four domains per run is a good balance.

Zomato Email Scraper features

Everything listed below is implemented in the Zomato Email Scraper today.

Feature	What it means in practice
Query expansion	Base, quoted, intitle: and one variant per modifier; base queries run first
Global deduplication	An email found by several queries is stored exactly once
Email normalisation	Understands name [at] domain [dot] com, name (at) domain, name @ domain, 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 will 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 parsing	Independent of Google's obfuscated CSS class names
Whole-page fallback	A markup change degrades to "emails without account details" rather than "no emails"
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Retries	Up to 3 attempts per page with exponential backoff and a fresh proxy session per request
Failed-query requeue	Blocked or failed queries are re-queued once at the end of the run
Concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Resumable state	Key-value store state keyed by an input hash; saves on PERSIST_STATE, MIGRATING and ABORTING
Run summary	Logs pages fetched, blocked pages, retries and emails per page

Zomato Email Scraper input fields

These are the exact input fields the Zomato Email Scraper accepts, with the defaults it ships with.

Field	Type	Default	Meaning
keywords	array (required)	["restaurant","cafe"]	Search terms describing the venues 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 — use IN or AE
expandQueries	boolean	true	Search each keyword x domain in several phrasings
queryModifiers	array	["email","contact","catering","reservations","owner"]	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 Zomato Email Scraper input

{
  "keywords": ["biryani", "cloud kitchen", "bakery"],
  "location": "Bengaluru",
  "customDomains": ["@gmail.com", "@rediffmail.com", "@yahoo.co.in"],
  "maxEmails": 300,
  "countryCode": "IN",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "catering", "bulk order", "owner"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

City-level prospecting with location

location is the most valuable field in the Zomato Email Scraper for anyone with a territory, because restaurants are an inherently local sale. It appends a quoted phrase to every query, so you can build one dataset per city instead of one undifferentiated national list.

Useful values on this platform include Bengaluru, Mumbai, Delhi NCR, Hyderabad, Pune, Chennai, Dubai, Abu Dhabi — and, for tighter targeting, area names such as Koramangala, Bandra or Al Barsha. Run one city per job, tag the dataset, and hand each rep a list they can actually route.

Leave location empty for a first exploratory run, then narrow. On an identity-thin platform, city segmentation is often the only geographic signal you get, so it is worth capturing at query time.

Zomato Email Scraper output fields

Every dataset item the Zomato Email Scraper writes carries all fourteen of these fields.

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 or snippet text, 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 Zomato Email Scraper output

[
  {
    "network": "Zomato",
    "keyword": "biryani",
    "query": "site:zomato.com biryani \"@gmail.com\" catering \"Bengaluru\"",
    "title": "Meghana Foods Menu - Koramangala, Bengaluru | Zomato",
    "accountName": "Zomato",
    "fullName": "Meghana Foods Menu - Koramangala, Bengaluru",
    "username": "bangalore",
    "profileUrl": "https://www.zomato.com/bangalore",
    "url": "https://www.zomato.com/bangalore",
    "description": "Biryani, Andhra. Bulk and catering orders: meghana.catering@gmail.com",
    "email": "meghana.catering@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:02:18Z"
  },
  {
    "network": "Zomato",
    "keyword": "cloud kitchen",
    "query": "site:zomato.com cloud kitchen \"@rediffmail.com\" owner \"Bengaluru\"",
    "title": "Reviews - Spice Route Cloud Kitchen | Zomato",
    "accountName": "",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Ordered twice this month. Owner responds fast on spiceroute.blr@rediffmail.com",
    "email": "spiceroute.blr@rediffmail.com",
    "emailDomain": "@rediffmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T10:04:51Z"
  },
  {
    "network": "Zomato",
    "keyword": "bakery",
    "query": "site:zomato.com bakery \"@gmail.com\" contact \"Bengaluru\"",
    "title": "Order Online - Sunrise Bakery, Indiranagar | Zomato",
    "accountName": "",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Cakes and bakes. Wholesale enquiries sunrisebakery.blr@gmail.com",
    "email": "sunrisebakery.blr@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:05:37Z"
  }
]

Two of the three rows above have username: null and an empty profileUrl, which is representative. That is the yield note in practice: Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle.

Note the first row's profileUrl shape too. Where Zomato does expose a resolvable path, the handle Google prints in its breadcrumb is usually the city segment, so the canonical link the Zomato Email Scraper can build is https://www.zomato.com/{city} rather than a per-venue page.

What a measured Zomato Email Scraper run looked like

Per roughly 10 parsed results in a live test: 2 rows with a usable identity, 2 resolvable profile URLs, 8 unique emails. Email density is high; account context is thin.

Plan your enrichment around that shape. Match on email rather than accountName, and use keyword, query and location as your segmentation signals instead.

Restaurant lead generation use cases for the Zomato Email Scraper

Here is where the Zomato Email Scraper fits into real B2B prospecting and market research workflows.

Use case	How to configure it
POS and payments sales in India	keywords: ["restaurant","cloud kitchen"], countryCode: "IN", city in location
Food distribution and wholesale	keywords: ["biryani","thali","bakery"] with a bulk order modifier
Packaging and disposables suppliers	Target cloud kitchen and tiffin, the most delivery-intensive formats
Catering and events sourcing	Lean on the catering modifier; restaurants publish these inboxes deliberately
Restaurant equipment sales	keywords: ["dhaba","sweet shop"] for owner-operated venues
UAE market entry	countryCode: "AE", location: "Dubai", keywords: ["shawarma","restaurant"]
Hospitality recruitment	Use the owner modifier to reach decision-maker inboxes
Local agency client acquisition	One city per run; pitch delivery-menu, photography or SEO work
CRM enrichment	Match your existing venue list on email and backfill missing addresses
Keyword research	Analyse keyword and query to see which phrasings surface public contacts

Practical Zomato Email Scraper recipes

India baseline. Local cuisine keywords, countryCode: "IN", one city in location, maxEmails: 300. This is the configuration most likely to return a large dataset.

Email-first workflow. Because identity coverage is thin, treat the dataset as an address list with metadata, not a venue directory. Deduplicate on email, then enrich names separately.

Domain sweep. Run @gmail.com, @rediffmail.com and @yahoo.co.in as three separate jobs. Per-domain visibility tells you where a market actually publishes contact details.

Widen before you deepen. More cuisine keywords and modifiers beat more pages per query, because Google caps a single query at roughly 300 results. Raise maxPagesPerQuery last.

Pair for coverage. Run the Uber Eats Email Scraper and Tripadvisor Restaurants Email Scraper beside this one to cover the same cities from platforms with different indexing behaviour.

Responsible use, GDPR and CAN-SPAM

An email that identifies a natural person is personal data even when it was published publicly. Public availability is not consent to send. If you contact EU residents the GDPR applies; commercial email into the United States falls under CAN-SPAM; India's DPDP Act and the UAE's data protection law cover the markets this Actor targets.

Practical steps that keep a Zomato Email Scraper workflow defensible:

• Prefer role addresses (info@, catering@, orders@) over addresses naming an individual.
• Keep provenance for every lead — the query, url and foundAt fields exist for exactly this.
• Give a clear sender identity, a stated purpose and a working opt-out in every message.
• Honour opt-outs immediately and check suppression lists before each follow-up.
• Be careful with review-page rows: the address may belong to a reviewer rather than the venue, so read description before sending.
• Delete data you are not actively using rather than warehousing scraped lists.

This is operational guidance, not legal advice.

Related Actors

The Zomato Email Scraper is one of 35 Actors in a Travel, Hospitality and Food family that all share this engine. For stronger venue identity, the OpenRice Email Scraper and Resy Email Scraper resolve profile URLs far more often; for the same restaurant motion in the West, use the OpenTable Email Scraper.

Actor	What it collects
Zomato Email and Phone Number Scraper	Emails and phone numbers from Zomato
Zomato Phone Number Scraper	Public phone numbers from Zomato
Airbnb Email Scraper	Public contact emails from Airbnb
Booking.com Email Scraper	Public contact emails from Booking.com
Caviar Email Scraper	Public contact emails from Caviar
ChowNow Email Scraper	Public contact emails from ChowNow
Contiki Email Scraper	Public contact emails from Contiki
Craigslist Email Scraper	Public contact emails from Craigslist
Delivery.com Email Scraper	Public contact emails from Delivery.com
DoorDash Email Scraper	Public contact emails from DoorDash
EatStreet Email Scraper	Public contact emails from EatStreet
G Adventures Email Scraper	Public contact emails from G Adventures
GetYourGuide Email Scraper	Public contact emails from GetYourGuide
Grubhub Email Scraper	Public contact emails from Grubhub
Hostelbookers Email Scraper	Public contact emails from Hostelworld
HotelsCombined Email Scraper	Public contact emails from HotelsCombined
Intrepid Travel Email Scraper	Public contact emails from Intrepid Travel
Just Eat Email Scraper	Public contact emails from Just Eat
Klook Email Scraper	Public contact emails from Klook
OpenTable Email Scraper	Public contact emails from OpenTable
Resy Email Scraper	Public contact emails from Resy
TheFork Email Scraper	Public contact emails from TheFork
Toast Restaurant Email Scraper	Public contact emails from Toast
TourRadar Email Scraper	Public contact emails from TourRadar
Traveloka Email Scraper	Public contact emails from Traveloka
Tripadvisor Attractions Email Scraper	Public contact emails from Tripadvisor
Tripadvisor Hotels Email Scraper	Public contact emails from Tripadvisor
Tripadvisor Restaurants Email Scraper	Public contact emails from Tripadvisor
Uber Eats Email Scraper	Public contact emails from Uber Eats
Viator Email Scraper	Public contact emails from Viator
Wanderlog Email Scraper	Public contact emails from Wanderlog
Wego Email Scraper	Public contact emails from Wego
Airbnb Email and Phone Number Scraper	Emails and phone numbers from Airbnb
Booking.com Email and Phone Number Scraper	Emails and phone numbers from Booking.com
Caviar Email and Phone Number Scraper	Emails and phone numbers from Caviar
ChowNow Email and Phone Number Scraper	Emails and phone numbers from ChowNow
Contiki Email and Phone Number Scraper	Emails and phone numbers from Contiki
Craigslist Email and Phone Number Scraper	Emails and phone numbers from Craigslist
Delivery.com Email and Phone Number Scraper	Emails and phone numbers from Delivery.com
DoorDash Email and Phone Number Scraper	Emails and phone numbers from DoorDash
EatStreet Email and Phone Number Scraper	Emails and phone numbers from EatStreet
G Adventures Email and Phone Number Scraper	Emails and phone numbers from G Adventures

Zomato Email Scraper limitations

Read these before planning anything around the output.

• Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle. This is the defining limitation, and it is why every recommendation above is email-first.
• Weak account identity. In a live test only about 2 of 10 parsed results carried a usable accountName or fullName. Expect emails with thin context.
• Publicly indexed emails only. The Zomato Email Scraper finds addresses already visible in Google's index. Anything behind a contact form or login is unreachable.
• Google's ~300-result cap. A single query returns roughly 300 results at most, which is why expandQueries defaults to true.
• possiblyTruncated. When true, Google's snippet ellipsis touched the email and it may be cut off. Verify before sending.
• username and profileUrl are frequently empty. Where populated, the handle is usually a city segment rather than a venue slug. That is a Google and platform limitation, not a bug.
• Apify GOOGLE_SERP proxy required. The Zomato Email Scraper cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans stop at 100 emails per run. Paid plans are uncapped.
• No guaranteed volume. Results vary with keywords, domains, location and Google's index on the day.
• Not affiliated with Zomato. This is an independent tool, not supported, endorsed by or connected to Zomato.

Zomato Email Scraper FAQ

Common questions about the Zomato Email Scraper, its inputs and its output.

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

In a live test, roughly 10 parsed results produced 8 unique emails but only 2 identified venues and 2 profile URLs. Expect good email density and thin account context. Total volume depends on your keywords, domains and countryCode, and no row count is guaranteed.

Why do so many rows have no restaurant name?

Because Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle. Google prints a page title rather than a venue label, and there is nothing for the Actor to resolve.

Does the Zomato Email Scraper log into Zomato?

No. It never logs in, never calls a Zomato API and never opens zomato.com in a browser. It reads Google results through the Apify GOOGLE_SERP proxy.

What should I set countryCode to?

IN for India, AE for the UAE. Run them separately. Google personalises results by country, and a local vantage point is what surfaces Zomato pages properly.

Which keywords work best?

Local format and cuisine words: biryani, dhaba, thali, tiffin, cloud kitchen, bakery, sweet shop. Pair them with catering, contact or owner modifiers.

Which email domains should I add?

Keep @gmail.com, then test @rediffmail.com, @yahoo.co.in and @outlook.com. These are suggestions based on Indian and UAE market habits, not guarantees.

How do I use location for city-level prospecting?

Put a city or area name in it — Bengaluru, Mumbai, Dubai, Koramangala — and run one job per territory. On an identity-thin platform this is often your only reliable geographic segmentation.

Whose emails am I actually finding?

Mostly business inboxes published for catering, bulk orders and reservations, but review pages can also surface a reviewer's address. Read description before you send.

Does the Zomato Email Scraper verify deliverability?

No. It extracts and normalises what Google indexed. Check rows flagged possiblyTruncated before using them.

Can I resume an interrupted run?

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

What happens when Google blocks a request?

Block, CAPTCHA and consent pages are detected rather than treated as empty. Pages get up to three attempts with exponential backoff, and failed queries are re-queued once at the end of the run.

Is scraping Zomato contact emails legal?

The Zomato Email Scraper only reads publicly indexed Google results. Whether you may then contact those addresses is a separate DPDP, GDPR and CAN-SPAM question. See the responsible use section and take your own legal advice.

Leave a review

If the Zomato 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, a bug, or you need a custom build of the Zomato Email Scraper? Contact neurodata.apify@gmail.com.