Tencent Maps Business Scraper for China

Search public Tencent Maps by city and keyword to extract structured local business listings, addresses, coordinates and source URLs, with optional repeat-run market change analysis. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify.

Why use this Actor

Teams tracking Chinese local markets need to know which businesses move in Tencent Maps search and how tracked brands gain or lose visibility, not only receive a static POI export.

Key features

• Buyer-native inputs aligned to Tencent Maps 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:

{
  "keywords": [
    "咖啡"
  ],
  "cities": [
    "深圳"
  ],
  "maxResults": 20,
  "trackedBrands": [
    "星巴克"
  ]
}

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

• keywords — Keywords: Chinese business/category search terms.
• cities — Cities: Chinese city names.
• maxResults — Maximum results: Maximum normalized places returned across all city/keyword combinations.
• trackedBrands — Tracked brands: Optional brand/name fragments used for visibility-share and top-rank monitoring.
• diagnostic — Diagnostic mode: Emit bounded browser-transport diagnostics only when no POIs can be normalized. Keep off for production runs.

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.001500 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

Business use and first result

For: China location and retail research.

Why run it: Search available public Tencent Maps results by keyword and city and compare observed local listings.

What to inspect: Business identifiers, addresses, coordinates and source URLs when accessible.

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: Tencent public results and frontend contracts can change; city coverage varies.

Search public Tencent Maps by city and keyword to extract structured local business listings, addresses, coordinates and source URLs, with optional repeat-run market change analysis.

Turn public Tencent Maps search results into repeatable local-market intelligence rather than another static POI export.

Why use this Actor

Tencent Maps is useful for understanding local visibility in China, but a one-time place list does not tell you whether a brand is gaining or losing search presence. This Actor is designed for recurring city/category monitoring: capture one search-market snapshot, reuse it in the next run, and receive exact rank changes, tracked-brand visibility share, and deterministic actions.

Key features

• Logged-out public Tencent Maps browser-search extraction with no Tencent API key or account credentials.
• Stable Tencent uid, business name, address, coordinates, current search-market rank, and available public place fields.
• Multi-city and multi-keyword inputs for repeatable market coverage.
• Optional trackedBrands list for brand visibility monitoring.
• trackedBrandSharePct and per-place visibilityScore for each city/category market.
• Reusable previousSnapshot input keyed by Tencent uid + city + keyword.
• Exact previousRank and rankDelta calculations between runs.
• Deterministic NEW_LISTING, RANK_GAIN, RANK_LOSS, DEFEND_TOP3, and MONITOR actions.
• Fails closed when the public browser transport produces no real POIs. Diagnostic placeholders are never treated as production results.

Output

Each dataset row includes uid, name, address, city, keyword, latitude/longitude, available rating/review/phone fields, marketRank, previousRank, rankDelta, isTrackedBrand, trackedBrandSharePct, visibilityScore, agentAction, source surface, and timestamp.

Example workflow

Run keywords: ["咖啡"], cities: ["深圳"], and trackedBrands: ["星巴克", "瑞幸"] to capture the current coffee-search market. Store those rows. On the next scheduled run, pass them as previousSnapshot. A Starbucks location moving from rank 8 to rank 3 receives rankDelta: 5 and RANK_GAIN; a tracked brand holding a top-three position can receive DEFEND_TOP3.

Use cases

Use it for China local SEO, retail-network monitoring, restaurant and hotel market mapping, competitor visibility tracking, branch expansion research, franchise territory review, category landscaping, lead discovery, EV-charging network intelligence, pharmacy coverage, shopping-center monitoring, and recurring brand-share briefs.

Pricing

The product uses one primary pay-per-result event: one normalized Tencent Maps business-intelligence row. The factory target is USD 0.0015 per result before canonical plan-tier pricing adjustments. Final release pricing remains governed by the factory's pricing and margin gates.

Inputs

• keywords: one or more Chinese business/category queries.
• cities: one or more Chinese city names.
• maxResults: maximum normalized rows returned across the run.
• trackedBrands: optional name fragments used for brand-share and top-rank monitoring.
• previousSnapshot: optional prior output rows for exact rank movement.
• diagnostic: troubleshooting-only switch; keep disabled for production workflows.

Competitive positioning

A mature Tencent Maps Actor already exists for rich POI/deep-detail extraction. This product deliberately does not claim superiority by merely returning the same fields. Its differentiation is the recurring intelligence layer: exact prior-snapshot search-rank movement plus tracked-brand visibility/share scoring and deterministic actions in the same run.

Limitations

Tencent Maps frontend and network contracts can change. Search results represent the current public ranked search surface and are not intended to represent an exhaustive city census. Deep reviews, photos, mini-program data, and other detail-heavy surfaces are intentionally outside the present parity scope. The Actor does not bypass login, CAPTCHA, private sessions, or restricted APIs.

Technical approach

The Actor launches Chromium on Apify, opens the public map.qq.com interface, submits the same logged-out POI search a visitor can perform, and normalizes real public search responses. It does not require private Tencent cookies or an API key. The Actor throws on zero real POIs rather than converting a transport failure into a successful-looking dataset.

Data ethics

Use this Actor for legitimate public-business research and monitoring. Users remain responsible for applicable law, platform terms, rate discipline, and appropriate downstream use of local-business data.

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

{
  "keywords": [
    "咖啡"
  ],
  "cities": [
    "深圳"
  ],
  "maxResults": 20,
  "trackedBrands": [
    "星巴克"
  ]
}

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.