# Baidu Search SERP & Competitor Rank Tracker (`quanmatrix/baidu-serp-brand-intelligence`) Actor

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.

- **URL**: https://apify.com/quanmatrix/baidu-serp-brand-intelligence.md
- **Developed by:** [Rafael Barreto Haddad](https://apify.com/quanmatrix) (community)
- **Categories:** SEO tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.05 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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:

```json
{
  "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:

```json
{
  "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.

# Changelog

This Actor's version history is a separate document: https://apify.com/quanmatrix/baidu-serp-brand-intelligence/changelog.md

# Actor input Schema

## `queries` (type: `array`):

One or more Baidu search queries.

## `maxResultsPerQuery` (type: `integer`):

Maximum number of public organic Baidu rows to retain for each query.

## `ownedDomains` (type: `array`):

Domains treated as owned brand properties when calculating visibility and share-of-SERP.

## `competitorDomains` (type: `array`):

Known competitor domains to classify and alert on within current organic results.

## `previousSnapshot` (type: `array`):

Optional rows from a prior run used to calculate exact result rank changes.

## `previousAnalysis` (type: `object`):

Optional prior Gen2 output used to calculate decision-metric deltas and regression.

## `valuePerImpactUnitUsd` (type: `number`):

Optional user-supplied economic value per impact unit. Leave empty to avoid monetary estimation.

## `monthlyRuns` (type: `integer`):

Optional expected monthly run count used only with valuePerImpactUnitUsd for economic impact estimation.

## `mcpConnectors` (type: `array`):

Optional MCP connectors authorized in your Apify account. Use them to send or write this Actor result to tools such as Slack, Notion, GitHub, Sentry, Supabase, or another compatible MCP service.

## `mcpToolName` (type: `string`):

Optional exact MCP tool name. Leave blank to let the selected MCP action preset discover a compatible tool automatically.

## `mcpToolArguments` (type: `object`):

JSON object passed to the selected MCP tool. String values may use {{actor_title}}, {{result_summary}}, or {{result_json}} placeholders.

## `mcpFailOnError` (type: `boolean`):

When enabled, an MCP delivery error fails the Actor run. Disabled by default so data extraction and intelligence results remain available even if the external destination is unavailable.

## `mcpActionPreset` (type: `string`):

Choose a safe action pattern. AUTO_SAFE_WRITE discovers a compatible non-destructive write tool automatically; use a specific preset for Slack, GitHub, Notion, or database delivery.

## Actor input object example

```json
{
  "queries": [
    "人工智能"
  ],
  "maxResultsPerQuery": 10,
  "ownedDomains": [],
  "competitorDomains": [],
  "monthlyRuns": 1,
  "mcpToolName": "",
  "mcpToolArguments": {},
  "mcpFailOnError": false,
  "mcpActionPreset": "AUTO_SAFE_WRITE"
}
```

# Actor output Schema

## `results` (type: `string`):

Structured Baidu organic rankings with ownership, snapshot and competitive intelligence fields.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quanmatrix/baidu-serp-brand-intelligence").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("quanmatrix/baidu-serp-brand-intelligence").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call quanmatrix/baidu-serp-brand-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quanmatrix/baidu-serp-brand-intelligence"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nF71ddDrNIVehNuJT/builds/1z46gzFfO4hebIYR3/openapi.json