Baidu Maps Business Scraper for China

Search Baidu Maps by keyword and city and return structured China business listings, addresses, coordinates, ratings, prices and local opportunity signals for leads and market research.

Why use this Actor

International market researchers need structured China local-business intelligence that quantifies competitive density, pricing, reputation and POI change without manually navigating Baidu Maps.

Key features

• Buyer-native inputs aligned to Baidu Maps business scraper.
• Predictable structured output in the default Apify Dataset.
• Pay Per Event pricing tied to measurable result rows or reports.
• Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
  "queries": [
    "餐馆"
  ],
  "cityCode": 131,
  "latitude": 39.9042,
  "longitude": 116.4074,
  "radiusMeters": 1500,
  "maxResultsPerQuery": 3,
  "previousSnapshot": []
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• queries — POI keywords: Business or place categories to search on Baidu Maps.
• cityCode — Baidu city code: Baidu Maps numeric city code. Beijing is 131.
• latitude — Center latitude: Search center latitude.
• longitude — Center longitude: Search center longitude.
• radiusMeters — Radius meters: Approximate neighborhood radius.
• maxResultsPerQuery — Results per query: Maximum POI rows per search.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.004000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Get a result in your first run

Paste this minimal tested input into the Apify Console. Change the query, SKU or records to match your own authorized target.

{
  "queries": [
    "餐馆"
  ],
  "cityCode": 131,
  "latitude": 39.9042,
  "longitude": 116.4074,
  "radiusMeters": 1500,
  "maxResultsPerQuery": 3,
  "previousSnapshot": []
}

Evidence, not hype

On 28 October 2026, build latest successfully returned 3 dataset row(s) in run z6nZy0QVacvw4QGbA. The test returned structured records from a public-source workflow; results may change when the source changes.

Supported scope: Only business fields exposed publicly by Baidu Maps are reported.

---

Search Baidu Maps by keyword and city and return structured China business listings, addresses, coordinates, ratings, prices and local opportunity signals for leads and market research.

Business use and first result

For: China local business and market discovery.

Why run it: Collect publicly available Baidu Maps listings by city and keyword for location research.

What to inspect: Business name, address, coordinates, public rating or price fields when present.

First run: use the documented sample input below, inspect the Dataset rows and source links, then reuse the saved output for a later comparison only where snapshots are supported. Confirm the input scope and current Pay Per Event pricing before scheduling ongoing use.

Scope and limitations: Public mobile results do not guarantee complete local-business coverage.

Search Baidu Maps by keyword and city to extract structured China business listings, addresses, coordinates and local-market fields.

Why use this Actor

This Actor is built for users who need structured evidence and a decision layer rather than a pile of raw HTML. It extracts public-source data, normalizes the records, assigns deterministic scores that can be inspected, and emits compact actions suitable for people, APIs, MCP clients, and autonomous agents. The design favors lightweight HTTP execution where the source permits it and fails explicitly when a source blocks access instead of silently inventing rows. Snapshot input can be reused across scheduled runs to turn one-time extraction into monitoring.

Key features

• Server-rendered mobile Baidu Maps POI extraction.
• UID, name, distance, area, rating, average price, category, hours and highlights when public.
• Market-relative price position.
• Reputation and local-opportunity scores.
• Exact snapshot deltas for rating, price, hours and category.

Input

Provide POI keywords, Baidu city code, center latitude/longitude, radius and optional previous snapshot.

Output

Each row is a normalized Baidu POI with market-relative scores and agentAction.

Example

{
  "queries": [
    "餐馆"
  ],
  "cityCode": 131,
  "latitude": 39.9042,
  "longitude": 116.4074,
  "radiusMeters": 1500,
  "maxResultsPerQuery": 3,
  "previousSnapshot": []
}

The default dataset contains one billable decision-ready row per extracted entity. Aggregate summaries and reusable snapshots are stored in the default key-value store when applicable. Scores are deterministic heuristics, not claims of certainty.

Use cases

• China local competitor research.
• Restaurant/hotel/retail benchmarking.
• Site-selection research.
• Recurring POI change monitoring.

Pricing

Initial benchmark price: US$0.004 per qualified POI row before tier discounts.

The Actor uses pay-per-event pricing. The primary event is one qualified row written to the default dataset. The product is designed to keep platform cost materially below the event price at normal workloads; the factory rechecks margin from live validation runs before publication.

Limitations

Local results depend on city code, coordinates and Baidu public coverage. v1 does not promise every detail-page contact or review field.

Public web sources change. A successful extraction today is not a contractual guarantee that a source will preserve the same markup tomorrow. Anti-bot systems, regional network behavior, deleted content, private accounts, and login-only data can reduce coverage. This Actor does not bypass account access controls and does not claim access to private data. Use the output as operational evidence and revalidate high-stakes decisions against the original source.

Buyer-first quick start (November 2026)

This workflow is designed for one practical buyer question, with a small, reproducible first run and auditable Dataset output.

Example input

{
  "queries": [
    "餐馆"
  ],
  "cityCode": 131,
  "latitude": 39.9042,
  "longitude": 116.4074,
  "radiusMeters": 1500,
  "maxResultsPerQuery": 3,
  "previousSnapshot": []
}

Source and limitations

The first run uses a public-source request or user-provided authorized URLs/documents. Upstream websites can block or throttle requests; not every result is assured to be available. Verify source URLs and timestamps before acting. If the source is inaccessible, a failed or limited result is not evidence of zero market demand.

Repeatable workflow

Use the default test to understand the output, verify record identifiers and field coverage, then schedule a Task with a bounded input. Compare real earlier snapshots only when available. Check the current Apify Store Pay Per Event rate and set Apify run charge limits for recurring use. Source evidence does not establish paying customers, successful outbound sales, or revenue.