Skip to content

Free, open-source Google Maps scraper for lead generation (Python, no API key, no Docker). Exports name, phone, email, website, rating and Instagram/Facebook/LinkedIn/TikTok/YouTube/X links to CSV. 100 places with emails in 44 s; --grid beats Google's 120 cap. MX email check, ad-pixel detection. Skill for Claude Code, Codex and Cursor.

3.9 KB
Raw Blame

Scrape restaurants from Google Maps: a lead list recipe

This recipe shows how to scrape restaurants from Google Maps for one city with the Google Maps Scraper Kit, including cafes and pizza places in the same run. You get a CSV of food businesses with phone, email, website, address and rating, free and local, with no API key.

Step 1: Run one search

Start the engine, then test with one search at the default depth:

python3 scripts/engine.py start
python3 scripts/scrape.py "restaurants in Austin TX" --city "Austin, TX" --depth 5

With Docker, docker compose up -d starts the same engine instead of the first line.

Check the preview and the email found-rate line before you scale up.

Step 2: Cover the food categories you sell to

Food businesses sit in many Google Maps categories. A search for restaurants may miss cafes and pizza places. Add each term with --keyword to run them as one job and one CSV:

python3 scripts/scrape.py "restaurants in Austin TX" --keyword "cafes in Austin TX" \
  --keyword "pizza in Austin TX" --city "Austin, TX"

For a whole city past the ~120 per search cap, add --grid 3. It splits the city into 9 map tiles, runs them one at a time and dedupes on place_id.

Step 3: Add price range for qualification

Google's search results carry no price range at the moment, so price_range comes back empty. Qualify with status (open or closed now), open_hours and reservations (table-booking links) instead. --full keeps all raw columns, including these three. Weekly opening hours work headless when Google supplies them:

python3 scripts/scrape.py "restaurants in Austin TX" --city "Austin, TX" --full

To keep the file lean, pick your own columns with --fields (the six social columns still follow unless you add --no-socials):

python3 scripts/scrape.py "restaurants in Austin TX" --city "Austin, TX" \
  --fields "title,phone,emails,website,category,status,open_hours,reservations,review_rating"

Example output

Illustrative rows only:

title phone emails category status reservations review_rating
Example Kitchen +1 512-555-0101 [email protected] Restaurant Open · Closes 10 PM example.com/book 4.6
Sample Slice +1 512-555-0102 [email protected] Pizza restaurant Open · Closes 11 PM 4.4
Demo Coffee House +1 512-555-0103 Cafe Closed · Opens 7 AM 4.7

Columns that matter for restaurant outreach

  • category: splits restaurants, cafes and pizza places so you can tailor each message.
  • status: whether the venue is open right now, so you can time a call. Needs --full or --fields.
  • open_hours: the week's opening hours, when Google supplies them. Needs --full or --fields.
  • reservations: table-booking links. A listing with one takes bookings online. Needs --full or --fields.
  • review_rating: a signal of reputation. review_count works headless and supports --min-reviews filtering.
  • phone, emails and website: the contact channels.

What to expect

  • Emails appear only when a business publishes one on its website. Many venues will have an empty cell.
  • price_range and menu stay empty: Google's search results carry no price range or menu link at the moment. Not every listing has reservations either.
  • A grid or many keywords is a large job. Run one job at a time and add proxies for repeated runs.
  • Heavy use without proxies can get your IP temporarily rate-limited by Google for minutes to hours.
  • Phones and emails are personal data, so read Responsible use before outreach.

Related