Yelp Business & Reviews Scraper — Phone, Website, Ratings

Turn Yelp into a B2B lead list. Search by keyword + location (e.g. plumbers in Austin, TX) and export every business with the fields a sales team actually needs: name, phone, website, rating, review count, address, category, and hours. No Yelp account, no API key — paste a search and get a ready-to-call lead list.

Why this actor?

Most Yelp scrapers break the moment Yelp tightens its bot protection — that's why the field averages 3 stars and rivals routinely return zero results on a hot day. This actor reaches Yelp through a managed-access browser (a real, resilient browser that handles the protected target reliably), so it keeps returning leads when request-based scrapers get blocked.

• Built for lead-gen — phone + website + address per business, not just raw listings
• Reliable access to a protected target — managed browser handles the challenge layer; runs on your Apify account, no proxy key to supply
• parse_confidence per record — know exactly how complete each lead is before you import it
• Flat schema — drops straight into a CRM, spreadsheet, or dialer

What you need

Nothing but a search. No Yelp developer account, no API key, no proxy of your own — just enter what you'd type into Yelp:

• Search terms — e.g. plumbers, HVAC contractors, dentists
• Location — e.g. Austin, TX, New York, NY, 90210

…or paste direct Yelp business URLs for targeted lookups.

Input

Field	Type	Description
searchTerms	string[]	Keywords: "plumbers", "pizza restaurants", "dentists"
location	string	City / state / zip: "Austin, TX", "90210"
businessUrls	string[]	Direct Yelp URLs or business aliases (instead of search)
maxResults	integer	Max per search term (0 = all, up to Yelp's ~240 cap)
includeDetails	boolean	Fetch each business page for website + hours
includeReviews	boolean	Add up to 3 recent review snippets per business
categories	string	Category alias filter, e.g. "plumbing"
sortBy	string	best_match / rating / review_count / distance

Phone ships on every search result. Website comes from the business page — turn on includeDetails to capture it.

Output (per business lead)

{
  "business_id": "WavvLdfdP6g8aZTtbBQHTw",
  "name": "Gary's Plumbing & Heating",
  "url": "https://www.yelp.com/biz/gary-s-plumbing-austin",
  "phone": "(512) 444-1234",
  "website": "garysplumbingatx.com",
  "address": "1234 Lamar Blvd",
  "city": "Austin",
  "state": "TX",
  "zip": "78703",
  "country": "US",
  "rating": 4.5,
  "review_count": 247,
  "price_range": "$$",
  "categories": "Plumbing, Water Heater Installation/Repair",
  "is_closed": false,
  "is_ad": false,
  "search_term": "plumbers",
  "hours_open": "Mon: 08:00-18:00; Sat: 09:00-14:00",
  "reviews_snippet": "[{\"text\": \"Great service, fast and fair...\"}]",
  "scraped_at": "2026-06-14T10:30:00+00:00",
  "parse_confidence": 1.0
}

website and hours_open are populated when includeDetails=true. reviews_snippet is populated when includeReviews=true.

Use cases

• Sales prospecting — build a call list of plumbers, contractors, dentists, salons in any city, with phone + website ready for outreach
• Local market research — compare competitor ratings, review counts and price ranges across a territory
• Lead enrichment — match a business name + city to its Yelp phone, website and rating
• Agency lead gen — pull targeted local-business lists to sell to clients

Pricing

Pay-per-lead: you're billed per business returned. No subscription, no minimums — a 500-lead pull costs the same whether you run it once or split it across the week. Compute runs on your own Apify account.

Frequently asked questions

Do I need a Yelp API key or account? No. You supply nothing but a search term and location. The actor reaches Yelp's public business pages for you.

Will it keep working when Yelp blocks other scrapers? That's the whole point. The actor uses a managed-access browser that handles Yelp's protection layer, so it stays reliable on days when request-based scrapers return nothing.

How do I get the website / contact field? Turn on includeDetails. Phone ships on every result; website lives on the business page, which includeDetails fetches.

What does parse_confidence mean? A 0.0–1.0 score per record. 1.0 means every expected field was populated; a lower score flags a lead with something missing (e.g. no phone), so you can filter before importing.

---

Not affiliated with Yelp Inc. Collects publicly available business information for legitimate lead-generation and research use; respect Yelp's terms and applicable law.

Integrations

Built for lead-gen teams and local-market researchers — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new lead into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push leads straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull leads mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Zoominfo Scraper
• 2GIS Places Scraper
• B2B Leads List Builder
• Company Lookup Scraper
• Email Finder
• Epa Data Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.