Yelp Business Scraper
Pricing
from $1.51 / 1,000 item extracteds
Yelp Business Scraper
Find and export public Yelp business listings, profiles, ratings, locations, contact details, hours, and search provenance.
Pricing
from $1.51 / 1,000 item extracteds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
7 days ago
Last modified
Categories
Features
Share
Use Yelp Business Scraper to discover public business records by service and location, or look up known Yelp business URLs and aliases. Retain canonical identity, profile links, exposed ratings, categories, address and contact context, available hours and media, and search provenance. This is a business-record export rather than review text, reviewer profiles or an independent verification of a business.
Quick start
Begin with a focused service and city, a small per-search result cap and a low page cap. The existing San Francisco plumbers example is:
{"searchQueries": ["plumbers"],"searchLocations": ["San Francisco, CA"],"maxResultsPerSearch": 20,"maxPagesPerSearch": 2,"sortBy": "recommended"}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose an example to start with a small, preconfigured search:
- Search Yelp businesses for local leads — Find up to 25 plumbers in San Francisco with available contact details and search context.
- Find a Yelp business by name — Search for Gary Danko in San Francisco with a five-business cap. This is a name search, not an exact URL lookup.
- Compare Yelp businesses by rating — Request Yelp's rating order for up to 25 sushi businesses in Austin, then review the returned ratings and review totals.
What you get
One deduplicated business row with stable Yelp ID, alias, source URL and available profile fields. Search-derived rows retain the observed query, location and rank context. Optional fields remain null or empty when Yelp does not expose them, and published ratings or status labels are source claims rather than a full business assessment.
Who is it for?
- Local-market analysts inspecting defined service and city samples.
- Directory-data teams matching known businesses to canonical Yelp identities.
- Local SEO researchers reviewing observed categories, ratings and source visibility.
- Data developers exporting business records for separate review or enrichment workflows.
How you can use the data
- Review a small service-market sample. Use the existing plumbers/San Francisco query or the Austin electricians/plumbers recipe, keeping query and location beside each record. Each query combines with every location, so per-search limits do not make one shared batch cap.
- Resolve a known business deliberately. Use the existing gary-danko-san-francisco alias or profile URL and retain businessId, alias and canonical url. Exact lookup is different from proving current ownership, contact accuracy or whether a venue remains open.
- Compare observed public reputation context. Retain rating, reviewCount, categories and priceRange for a defined search sample, keeping optional gaps. A price tier is not a quoted bill, and the business record does not contain the individual reviews behind an aggregate rating.
- Prepare a review-workflow handoff. Feed canonical business URLs to the separate Yelp Reviews Scraper when review records are needed. Keep your own cross-run business IDs and timestamps for comparisons, rather than asking this Actor to provide a complete review archive or automatic change history.
Input settings
| Field | Type | Description |
|---|---|---|
searchQueries | string[] | Categories, services, or business names. |
searchLocations | string[] | Cities, regions, or postal codes. Each query is combined with each location. |
startUrls | request[] | Public Yelp business or search URLs. |
businessAliases | string[] | Yelp aliases such as gary-danko-san-francisco. |
maxResultsPerSearch | integer | Unique businesses per query/location, from 1 to 240. |
maxPagesPerSearch | integer | Pagination cap from 1 to 24. |
sortBy | string | recommended, rating, or review_count. |
priceLevels | integer[] | Optional Yelp price levels 1–4. |
Provide both searchQueries and searchLocations when using search mode. You can combine search, URL, and alias inputs in one run. Duplicate businesses are saved once.
Input options
Find local service providers
{"searchQueries":["electricians","plumbers"],"searchLocations":["Austin, TX"],"maxResultsPerSearch":25}
Look up known profiles
{"businessAliases":["gary-danko-san-francisco"],"maxResultsPerSearch":1}
Use public Yelp URLs
{"startUrls":[{"url":"https://www.yelp.com/biz/gary-danko-san-francisco"}]}
Output data
The existing illustrative row contains historical source values rather than a current business or rating lookup:
{"businessId": "RR5cJHVh-R9f5DNqZ-XAJA","alias": "discount-plumbing-rooter-services-san-francisco-2","name": "Discount Plumbing Rooter Services","url": "https://www.yelp.com/biz/discount-plumbing-rooter-services-san-francisco-2","rating": 4.5,"reviewCount": 1305,"categories": ["Plumbing"],"searchQuery": "plumbers","searchLocation": "San Francisco, CA","searchRank": 1,"collectedAt": "2026-08-13T12:00:00.000Z"}
Every dataset row uses one stable business shape. Source-dependent optional fields may be null or empty when Yelp does not publish them.
| Group | Fields |
|---|---|
| Identity | businessId, alias, name, url, alternateNames, businessType |
| Status | isAd, isClaimed, isClosed, isTemporarilyClosed |
| Address | addressLine1, addressLine2, city, state, postalCode, country, neighborhoods |
| Coordinates | latitude, longitude |
| Classification | categories, cuisine |
| Contact and price | phone, website, priceRange |
| Reputation | rating, reviewCount, healthScore |
| Hours and features | hours, specialHours, amenities, businessHighlights |
| About | about, specialties, history, yearEstablished |
| Links and media | menuUrl, reservationUrl, primaryPhoto, images, mediaCount |
| Provenance | searchQuery, searchLocation, searchRank, sourceUrl, collectedAt |
This Actor returns business discovery/profile records, not review bodies or reviewer profiles.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
A run has a start event and an item event for each unique business saved. A started run can retain its start charge even when no businesses are found. Failed targets and duplicates do not create item charges. Extraction stops when the remaining result budget is exhausted, keeping completed records available.
Keep per-search result and page caps small, accounting for every query/location combination.
Current rates and account-tier discounts are shown on the live Pricing tab. Platform usage can also apply.
Tips for best results
- Use specific service and city terms. Keep the intended market with your result sample.
- Begin with a low result and page cap. Yelp can expose fewer businesses than the requested maximum.
- Use known aliases for known identities. A canonical match does not verify every profile claim.
- Inspect optional fields. Category and regional coverage differ, including contact and hours information.
- Keep aggregate ratings separate from reviews. Business rows contain context rather than review bodies or reviewer profiles.
- Preserve run-summary outcomes. Useful completed records can remain when another source fails.
Limits and caveats
Yelp can limit available search results. Each search is capped at 240 businesses and 24 pages, and every query is combined with every supplied location. A run accepts at most 240 combined search-page and profile-lookup operations. Inputs that exceed that combined limit are rejected before extraction. Businesses are deduplicated across the run, so stored provenance is the observed contributing context rather than a complete list of every search a business could match.
The Actor exports public business discovery and profile records, not review bodies or reviewer profiles. Source-dependent contact, hours, category, location, status and media fields can be absent or change over time. A rating, healthScore or claimed-business flag is not an independently verified assessment or ownership check.
Completed businesses remain available when another target fails. The default key-value-store RUN_SUMMARY reports failed targets, empty-result reasons, duplicates, saved rows and pending work. An explicitly reported no-match result or unavailable page can finish with an empty dataset. Blocking and unexplained empty responses are not treated as confirmed no matches, and inaccessibility does not establish that a business is deleted or private.
Processing has a four-minute limit, so a larger input may not finish. Deadline, essential storage and billing failures fail the run while preserving records already saved. PENDING_WORK lists unprocessed work for review. Automatic replay of the same started run is stopped to avoid repeating completed work. Review its existing output before starting a separate, smaller run, which has its own charges.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~yelp-business-scraper/runs?token=<APIFY_API_TOKEN>' \-H 'Content-Type: application/json' \-d '{"searchQueries":["sushi"],"searchLocations":["Austin, TX"],"maxResultsPerSearch":20}'
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/yelp-business-scraper').call({searchQueries: ['sushi'],searchLocations: ['Austin, TX'],maxResultsPerSearch: 20,});const { items } = await client.dataset(run.defaultDatasetId).listItems();
Python
from apify_client import ApifyClientclient = ApifyClient("<APIFY_API_TOKEN>")run = client.actor("fetch_cat/yelp-business-scraper").call(run_input={"searchQueries": ["sushi"],"searchLocations": ["Austin, TX"],"maxResultsPerSearch": 20,})items = client.dataset(run["defaultDatasetId"]).list_items().items
MCP and AI agents
You can ask your AI assistant to collect data with Yelp Business Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Yelp Business Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/yelp-business-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Yelp Business Scraper by Fetch Cat, or give it the identifier fetch_cat/yelp-business-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s Yelp Business Scraper to collect up to 5 plumbers in San Francisco, CA with a one-page cap and recommended order. Keep canonical IDs, Yelp URLs and missing optional fields without verifying business quality.”
- “Retrieve the public business alias gary-danko-san-francisco with a one-result cap. Keep canonical identity and available profile context without collecting review bodies or reviewer profiles.”
- “Collect up to 3 electricians and up to 3 plumbers in Austin, TX with a one-page cap per search. Keep query/location provenance and source ratings without assuming a single three-row batch or complete city coverage.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
What data can I export with Yelp Business Scraper?
You can export identity, location, categories, ratings, review totals, public contact details, hours, media, and search provenance for each discovered business.
Can I run Yelp Business Scraper through an API, schedule, or MCP client?
Yes. Use the Apify API example above, create a schedule in Console, or connect through the linked Apify MCP endpoint with the same JSON input.
How much does it cost to use Yelp Business Scraper?
Each run charges one start event and one item event per unique business saved. Current rates and account-tier discounts are shown on the Actor's Pricing tab.
Does this scrape Yelp reviews?
No. It exports one row per business. Use Yelp Reviews Scraper for public review records.
Why are some contact or hours fields empty?
Yelp does not publish every field for every business or region. The Actor keeps the business row and uses null or an empty array for unavailable optional data.
Can I search multiple locations?
Yes. Every search query is combined with every supplied location, and businesses are deduplicated across the run.
What happens if one search fails?
Completed businesses remain in the dataset. An isolated target failure is reported in the run summary. If all extractions fail, or a deadline, essential storage or billing failure stops the work, the run fails rather than presenting the sample as complete.
Why did an unsupported connection setting fail?
This Actor does not accept custom connection or proxy overrides. Remove the unsupported setting and use the supported input fields above. The input help explains the existing connection behavior and limits.
Related Actors
- Yelp Reviews Scraper — Collect available public Yelp business reviews and ratings.
- Google Maps Reviews Scraper — Collect public Google Maps review text, ratings and available reviewer fields.
- Google Maps Lead Finder — Collect public Google Maps business listings and optionally published business-website contacts.
- Tripadvisor Reviews Scraper — Collect available public Tripadvisor review text, ratings and visit details.
- Trustpilot Reviews Scraper — Collect public Trustpilot business reviews, ratings and available company details.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥