Yellow Pages Scraper — US Local Business Directory

Pay-per-result: $1.50/1K businesses scraped. Phone numbers and ratings included. No proxy, no monthly fee.

Yellow Pages still indexes 20 million+ US local businesses. This scraper gives you clean, structured leads — name, phone, address, website, categories, rating — in seconds. Pay only for results you get.

Scrape yellowpages.com search results into clean, lead-gen-ready JSON. Extract business name, phone, address, website, categories, rating, review count, and years in business — with a parse_confidence score on every record.

What you get

Field	Description
business_name	Full business name
phone	Primary phone number
street	Street address
city	City
state	State (2-letter code)
zip	ZIP code
website	Business website URL (external, not a YP redirect)
categories	List of YP business categories
rating	Star rating (1.0–5.0, half-star precision)
review_count	Number of reviews
years_in_business	Years in business (from YP badge)
yp_url	Canonical Yellow Pages listing URL
is_ad	Whether this is a sponsored listing
parse_confidence	Parse quality score (1.0 = perfect)
warnings	List of machine-readable quality codes

Input

Parameter	Type	Default	Description
searchTerms	string	"plumbers"	Business type or keyword
location	string	"Austin, TX"	City, state, or ZIP
maxResults	integer	30	Max records to return
includeAds	boolean	false	Include sponsored listings
startPage	integer	1	Start page (for resuming runs)

Why this scraper is different

Most Yellow Pages scrapers on the market break within weeks because they anchor on CSS class names that change with every site deploy. This scraper uses structural HTML anchors (div.v-card, a.business-name, p.adr, div.result-rating class words) that are tied to semantic meaning, not generated class names. When YP updates their CSS, this parser keeps working.

Every record ships a parse_confidence score (0.0–1.0). Below 0.7 is a machine-readable signal that the page structure has drifted — your data pipeline can filter automatically.

	This actor	Generic YP scrapers
Parse method	Structural HTML anchors (resilient)	CSS class names (breaks on redeploy)
parse_confidence	Yes — per record	No
Address parsing	Dual-pattern (service-area + physical)	Often breaks on service-area listings
Proxy required	No	Often yes
is_ad flag	Yes (filter sponsored)	Rarely
years_in_business	Yes (unique YP data point)	Rarely
Price	$1.50/1K	$2-5/1K

Use with AI agents (MCP)

This scraper is callable as a tool by AI agents (Claude Desktop, Cursor, VS Code, n8n, LangGraph, CrewAI, or any MCP-compatible client) via Apify's hosted Model Context Protocol server. Any AI agent can look up US business contacts mid-conversation.

Point your MCP client at this tool:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.apify.com/?tools=bovi/yellowpages-scraper",
        "--header",
        "Authorization: Bearer <YOUR_APIFY_TOKEN>"
      ]
    }
  }
}

Pricing example

Pay-per-result: $1.50 per 1,000 business records ($0.0015/record). You only pay for actual results scraped — no monthly fee, no minimum.

Run size	Cost
100 businesses	$0.15
500 businesses	$0.75
1,000 businesses	$1.50
5,000 businesses	$7.50

Output sample

{
  "business_name": "Austin Plumbing Co",
  "phone": "(512) 555-0147",
  "street": "1423 S Lamar Blvd",
  "city": "Austin",
  "state": "TX",
  "zip": "78704",
  "website": "https://austinplumbing.com",
  "categories": ["Plumbers", "Drain Cleaning"],
  "rating": 4.5,
  "review_count": 87,
  "years_in_business": 12,
  "yp_url": "https://www.yellowpages.com/austin-tx/mip/austin-plumbing-co-123456",
  "is_ad": false,
  "parse_confidence": 1.0,
  "warnings": []
}

FAQ

Do I need a proxy or API key? No — Yellow Pages serves plain HTML without heavy bot protection. No proxy or API key required. The actor runs zero-COGS.

What export formats are available? JSON, CSV, Excel, and XML — downloadable from the dataset page or via the Apify REST API.

Can I schedule regular runs? Yes. Use Apify Scheduler (or n8n/Zapier) to run on a schedule and push new records to Google Sheets, a CRM, or a webhook.

What if the actor returns empty results? Confirm the searchTerms and location match Yellow Pages conventions (e.g. "Austin, TX" not "Austin Texas"). YP returns empty when there are no results for that exact search pair.

Use cases

• Lead generation: build targeted prospect lists (plumbers in Austin, dentists in Chicago)
• Local SEO research: audit competitors' listings, ratings, and categories
• Market research: map service providers in a region
• Data enrichment: match phone/address data to existing business lists

Technical notes

• No proxy required for most runs — YP is plain HTML without heavy access protection
• Handles both service-area listings (no street address) and physical locations
• Filters YP redirect links to return the actual business website URL
• Pagination via ?page=N — 30 results per page

Integrations

Built for lead-gen teams and local-market researchers extracting US business contacts and ratings by category and city — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item 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 results 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 this data 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:

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

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.