Baidu Search SERP & Competitor Rank Tracker

Search Baidu by keyword and return structured SERP positions, titles, URLs and domains with owned-vs-competitor visibility, share-of-voice and repeat-run rank change tracking for China SEO.

Quick start

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

{
  "queries": [
    "人工智能"
  ],
  "maxResultsPerQuery": 10,
  "ownedDomains": [],
  "competitorDomains": []
}

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 — Search queries: One or more Baidu search queries.
• maxResultsPerQuery — Results per query: Maximum number of public organic Baidu rows to retain for each query.
• ownedDomains — Owned brand domains: Domains treated as owned brand properties when calculating visibility and share-of-SERP.
• competitorDomains — Competitor domains: Known competitor domains to classify and alert on within current organic results.

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

Detailed documentation

Detailed documentation

Search Baidu by query and return structured SERP results, positions and domains, with optional owned-vs-competitor share and rank-change tracking.

Why use this Actor

Raw SERP extraction is useful, but it still leaves analysts or agents to perform the decision layer themselves. This Actor adds configurable owned-domain and competitor-domain classification, query-level share-of-SERP metrics, exact snapshot-to-snapshot rank arithmetic, and deterministic actions such as DEFEND_TOP3, RECOVER_RANK, COMPETITOR_ALERT, RISING, and MONITOR. The result is directly usable by dashboards, scheduled monitoring, n8n/Make workflows, alerting systems, data warehouses, and AI agents.

Key features

• Public Baidu desktop organic result extraction without customer Baidu credentials.
• Multiple queries per run with a configurable result limit.
• OWNED, COMPETITOR, or OTHER classification using domains you provide.
• brandSharePct and competitorSharePct calculated for every query snapshot.
• Exact previousRank and rankDelta when a prior snapshot is supplied.
• Deterministic monitoring actions and human-readable reasons.
• A reusable SNAPSHOT key-value record for scheduled comparisons.
• Direct-first transport with Apify Residential proxy fallback if Baidu verification appears.
• Structured dataset schema and overview view for exports and downstream automation.

Example

Input:

{
  "queries": ["人工智能", "新能源汽车"],
  "maxResultsPerQuery": 10,
  "ownedDomains": ["example.com"],
  "competitorDomains": ["competitor.cn"],
  "previousSnapshot": []
}

A result row includes the query, organic rank, title, Baidu result URL, extracted/display domain where available, ownership classification, brand and competitor share, previous rank, rank delta, action, reason, source surface, and timestamp. Save the SNAPSHOT output and pass those rows into the next scheduled run to activate change intelligence.

Use cases

Use it for China SEO rank monitoring, launch visibility, competitor top-five alerts, category and product keyword monitoring, reputation searches, campaign terms, partner visibility, localized keyword research, weekly or daily ranking deltas, and agentic SEO feeds. It is particularly useful when a team wants one stable dataset contract across many monitored Chinese search terms instead of manually comparing exports.

Pricing

The product uses one primary pay-per-result event. One charged event corresponds to one decision-ready Baidu organic visibility row. There is no separate start-event design in the QuantMatrix pricing model. Tiered PPE is applied where the Apify account supports it so higher-volume customers receive lower per-result pricing while the product preserves positive operating margin.

Limitations

The hardened surface is the public desktop Baidu SERP. Baidu can change markup or introduce verification, so parser and transport maintenance is expected. Some Baidu redirect result links can obscure the true destination domain when display-domain metadata is absent; those rows remain valid ranking evidence but may be classified as OTHER until a destination domain is visible. The Actor does not bypass account authentication, private content, CAPTCHA challenges, or restricted interfaces. Query responsibly and comply with applicable terms and law.

Output fields

Core fields include recordId, query, rank, previousRank, rankDelta, title, url, displayUrl, domain, snippet, ownership, brandSharePct, competitorSharePct, agentAction, agentReason, sourceSurface, and scrapedAt. The schema is intentionally compact enough for agents while still retaining the evidence needed for audit and human review.

Monitoring workflow

For a recurring monitor, run the Actor on the same query set, persist the SNAPSHOT record, and feed it back as previousSnapshot on the next run. Ranking improvements become positive deltas; losses become negative deltas. Owned losses can trigger RECOVER_RANK, top-three owned positions can trigger DEFEND_TOP3, and known competitors entering the top five can trigger COMPETITOR_ALERT. No opaque AI judgment is required for these actions, which makes the output reproducible and suitable for automated governance.