Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
Structured output
Use Crawlora's Datasets API to query stored Google Maps business records that have already been collected and indexed. The search endpoint is designed for repeatable product workflows, enrichment, analytics, and exports where the Google Maps app's manual search and limited refinement controls are not enough.
Dataset workflows
The Google Maps app is built for interactive discovery. Crawlora dataset search is built for structured, repeatable queries over indexed records, including filters, facets, pagination, geo radius search, distance sorting, and API output that can feed products and analytics.
Browse dataset endpointsRequest schema
These parameters come from the active Search stored Google Maps businesses catalog entry.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| q | string | No | Full-text business search query, max 256 characters | - |
| category | string | No | Exact category filter, max 128 characters | - |
| country | string | No | Exact country filter, max 128 characters | - |
| state | string | No | Exact state filter, max 128 characters | - |
| county | string | No | Exact county filter, max 128 characters | - |
| city | string | No | Exact city filter, max 128 characters | - |
| town | string | No | Exact town filter, max 128 characters | - |
| min_rating | number | No | Minimum rating, 0 through 5 | - |
| min_review_count | integer | No | Minimum review count | - |
| has_website | boolean | No | Filter by website presence | - |
| has_phone | boolean | No | Filter by phone presence | - |
| lat | number | No | Latitude for radius filtering or distance sort | - |
| lon | number | No | Longitude for radius filtering or distance sort | - |
| radius_m | integer | No | Radius in meters, 1 through 50000; requires lat and lon when supplied | - |
| sort | string | No | Sort enum: relevance, updated_at_desc, rating_desc, review_count_desc, distance_asc | - |
| page | integer | No | Page number, defaults to 1 | - |
| page_size | integer | No | Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000 | - |
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"dataset": "google-map-businesses",
"items": [
{
"place_id": "ChIJ99URUeOAhYAR0J5ZUxTesDQ",
"name": "Hotel Zephyr San Francisco",
"category": [
"hotel"
],
"rating": 4.1,
"review_count": 3213
}
],
"page": 1,
"page_size": 20,
"total": 1,
"sort": "relevance"
}
}Endpoint catalog
/datasetsLists available read-only scraped datasets. Initial dataset id enum: `google-map-businesses`.
/datasets/google-map-businesses/searchSearches Google Maps business records stored in Elasticsearch. Sort enum: `relevance`, `updated_at_desc`, `rating_desc`, `review_count_desc`, `distance_asc`.
/datasets/google-map-businesses/nearbySearches stored Google Maps businesses near a coordinate in dataset id enum value `google-map-businesses`.
/datasets/google-map-businesses/facetsReturns terms aggregation counts for Google Maps businesses. Facet enum: `category`, `country`, `state`, `county`, `city`, `town`, `website_status`.
/datasets/google-map-businesses/items/{place_id}Returns one stored Google Maps business by Google place_id from dataset id enum value `google-map-businesses`.
Managed execution
Datasets endpoints query stored Crawlora data rather than fetching Google Maps live for each request. They are API-key protected read paths over indexed structured records, so there is no browser rendering, no proxy routing, and no live upstream page collection during a dataset search.
Reads from stored Google Maps business datasets
Uses indexed search and filtering for repeatable queries
Returns structured JSON records and metadata
Supports facets for category, geography, and website-status exploration
Supports geo radius search and distance sorting when coordinates are supplied
Does not trigger live scraping, browser execution, or proxy routing
Workflow comparison
Use this comparison when a manual map search is too limited for product, analytics, or enrichment workflows.
| Requirement | Google Maps app workflow | Crawlora dataset search |
|---|---|---|
| Search workflow | Manual, session-oriented exploration inside the app. | Repeatable API queries over stored structured records. |
| Filters | Limited visible filters and map UI refinements. | Query filters for category, country, state, county, city, town, rating, reviews, phone, website, and website status where available. |
| Facets | No API-style aggregation counts for planning and analysis. | Facet endpoints return counts for category, geography, and website-status fields. |
| Geo search | Interactive map movement is useful but hard to automate. | Nearby endpoint supports latitude, longitude, radius, and distance-sorted results. |
| Output | Results are optimized for viewing inside the app. | Responses are JSON for exports, enrichment, dashboards, and internal tools. |
| Execution | Live app interaction. | Stored dataset read path with no live scraping or proxy routing. |
Crawlora Datasets is not the Google Maps app and is not a live Google Maps proxy. Dataset endpoints query stored structured records that Crawlora has already collected and indexed. No proxy routing, browser rendering, or live upstream scraping is applied when a dataset search, facet, nearby, list, or detail request is executed. Customers are responsible for using returned data lawfully and in line with applicable terms and Crawlora terms.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Use live Google Maps endpoints when you need current place search or place detail collection.
OpenNormalize addresses and coordinates before dataset search or enrichment.
OpenRead the full stored dataset endpoint reference.
OpenTest stored Google Maps business search with sample filters.
OpenReview plans, credits, and API usage limits.
OpenFAQ
Answers for developers evaluating Crawlora Datasets for structured local business search.
Dataset search is an API for querying stored structured records, starting with the google-map-businesses dataset. It is designed for repeatable search, filtering, facets, geo queries, and JSON output.
No. Dataset search reads indexed stored records. It does not apply proxy routing, browser rendering, or live upstream scraping for each query.
The Google Maps app is optimized for manual interactive discovery. Crawlora dataset search is optimized for programmatic filtering, pagination, facets, geo radius queries, distance sorting, and JSON output for products or analytics.
The active dataset enum currently includes google-map-businesses, with list, search, nearby, facets, and detail endpoints in the public catalog.
Yes. The search endpoint supports filters such as category, country, state, county, city, town, minimum rating, minimum review count, website presence, phone presence, coordinates, radius, sort, page, and page_size where available.
Yes. The facets endpoint returns counts for supported fields such as category, country, state, county, city, town, and website_status.
Use live Google Maps endpoints when you need fresh live place search or place detail collection. Use Datasets when stored indexed records are enough and you need repeatable structured search.
Start building
Test /datasets/google-map-businesses/search in Playground, inspect filters and response fields in Docs, and use API-key protected JSON responses in your workflow.