Advanced Yellowpages Scraper
Pricing
from $1.50 / 1,000 results
Advanced Yellowpages Scraper
Yellowpages Scraper is a robust tool designed to scrape business information from Yellowpages. It efficiently extracts essential details such as business names, addresses, phone numbers, categories, and more.
Pricing
from $1.50 / 1,000 results
Rating
5.0
(2)
Developer
codemaster devops
Maintained by CommunityActor stats
11
Bookmarked
141
Total users
1
Monthly active users
2 hours ago
Last modified
Categories
Features
Share
Yellow Pages Scraper
Extract public yellowpages.com (US) business listings: name, phone, address, website, categories, rating, review count and public review snippet when present. Rows include source URL, fetch time, extraction method and deduplication key. Missing source fields are omitted.
Quick start
{"runMode": "compliant","startUrls": [{ "url": "https://www.yellowpages.com/los-angeles-ca/dentists" }],"maxItems": 10,"maxPages": 4,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"],"apifyProxyCountry": "US"}}
Fresh inputs use compliant mode, the category-page example, 10 results, 4 page attempts, and US residential proxies. API input {} uses the same runtime defaults. Explicit custom URLs/searches replace the sample; explicit proxy choices are preserved. Residential traffic is billable. To opt out deliberately, set proxyConfiguration to { "useApifyProxy": false }.
After rebuilding from this branch, use Reset input in the Apify Input form to load its current prefilled example. A build does not overwrite previously saved Actor inputs, task inputs, or an earlier run's input. Replace any old authorized-mode sample unless you intend to supply your real legal-basis reference. The run_start log reports proxy mode, groups and country; channel: "http" describes the crawler, not proxy usage.
The compliant label describes a URL guard, not a legal determination. It blocks /search, including pagination into that path. Review the site's terms and your intended use. Search/location requires runMode: "authorized" and your actual uppercase PREFIX-IDENTIFIER legalBasisReference. A reference does not grant permission.
HTTP, credentials in URLs, custom ports, and domains outside yellowpages.com are rejected. allowedHosts narrows supported hosts; it does not enable unrelated sites. HTTP redirects are disabled. Browser resources use the same policy, which may reduce rendered coverage. DNS answers are not pinned; trusted Yellow Pages DNS/proxy resolution remains a boundary.
Output and diagnostics
Observed sample from private verification run fLh6m60K0kOeGd7rg:
{"name": "Jose T. Sauz D.d.s","phone": "(213) 483-8754","website": "http://josetsauzdds.localsearch.com/","sourceUrl": "https://www.yellowpages.com/los-angeles-ca/dentists","channel": "http"}
Export the default dataset as JSON, CSV or Excel. confidence identifies extraction method, not verification. reviewSnippet is an excerpt, not full review history. Phone normalization removes non-digits, including extension separators; it is not E.164 validation.
The Output tab links to listings and RUN_SUMMARY. Summary fields include parsed rows, pages, attempted requests, duplicates, failures, stop reason, and per-run failure dataset ID. Technical errors are kept out of business rows. All-failed runs fail visibly; mixed outcomes retain a partial summary. Unknown markup is an error; an explicit .no-results marker indicates an expected empty page.
Limits and reliability
maxItemscaps rows.maxPagescaps combined HTTP/browser navigation attempts including retries. Browser resources/proxy traffic are additional work. Small page budgets may leave no attempt for fallback.- HTTP runs first; blocked responses are then processed with Playwright. Fallback is best effort and cannot guarantee access through challenges.
- Pagination follows next-page links with URL/compliance checks. Retries and concurrency are bounded.
- State includes counters and emitted keys. Use fresh storage when upgrading from counters-only checkpoints. Dataset writes and checkpoints are not a cross-store transaction: abrupt crashes can produce duplicates on resurrection. Consumers should deduplicate by
dedupKey. - Abort/migration handlers persist diagnostics and request teardown. Hosted cancellation verification is tracked separately in
audit/STATUS.md.
Coverage and limitations
Supports US listing markup and business JSON-LD, including nested graph/item-list structures. Detail pages without supported JSON-LD may fail. Ghana, Nigeria, Kenya, Uganda and Canada are not implemented in the active runtime. Legacy regional configuration is not connected to the crawler.
No email discovery, mailbox verification, full review collection, geocoding, or paid enrichment. withCoordinatesPlaceholder emits null coordinates; withTimestamp adds a timestamp. Neither performs enrichment. No HTTP server or Standby interface.
Public pages need no login. Optional proxy credentials belong in proxy configuration, never start URLs. Code does not call Actor.charge or add per-result billing events. Charges depend on live Apify pricing and compute/proxy usage, even for zero rows. Begin with small budgets. No enrichment provider is called.
Development and support
Use Node 22 or 24. Run npm ci, npm test, npm run lint, apify validate-schema, then apify run --input-file audit/sample-input.json. Set APIFY_LOCAL_STORAGE_DIR to isolated task storage to preserve evidence. CI verifies without deploying production.
For challenges or zero rows, inspect RUN_SUMMARY, failure dataset and logs. Proxies cannot guarantee access. Avoid unchanged retries of deterministic errors. Report sanitized input, run ID and summary in GitHub issues, without tokens or proxy passwords.