# JD.com Keyword Rank Tracker (`ikmal_suzali_atr/jd-rank`) Actor

Full JD.com search results per keyword (China (jd.com)) with position and sponsored flag — see where a brand ranks and who holds the paid slots. Dual-mode: the same code runs as an ATR BullMQ worker.

- **URL**: https://apify.com/ikmal\_suzali\_atr/jd-rank.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 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.

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

## JD.com Keyword Rank Tracker

Answers one question for a keyword on JD.com: who pays to appear on it, in what order, at what price. The actor reads JD's ad-fed keyword search, so every row is a paid placement with its slot position, the shop behind it and the store quality score JD publishes.

### What you get

- Slot order per keyword: `keyword`, `page` and a `position` that keeps counting across pages.
- `is_sponsored` is `true` on every row by design. This feed is JD's advertising surface, so the dataset is a clean list of who buys the keyword.
- `ad_type` for the placement type, next to `total_results`, JD's own count for the keyword.
- Shop identity: `seller` is the store name, `shop_id` its numeric id, `self_operated` marks JD's first party stores.
- Trust signals shoppers act on: `good_rate_pct` is the positive review percentage and `comments_bucket` the review volume band JD prints, such as `200万+`.
- Category placement as `cid1`, `cid2` and `cid3`, showing whether an advertiser bids inside or outside its own category.
- `price` in CNY as a number, plus `product_url` and `image_url` for every placement.

### Input

Pass keywords and how many pages of the ad feed to capture.

```json
{
  "keywords": ["洗发水"],
  "locale": "cn",
  "pages": 2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "CN"
  },
  "delayMs": 1200,
  "callsPerSession": 60
}
```

- `keywords` (required): the search terms to capture. Chinese terms are expected. Duplicates are ignored.
- `locale`: `cn`. JD.com has one storefront.
- `pages`: pages of the feed per keyword, 1 to 10. Pages after the first come from JD's paging feed at about 24 placements each.
- `proxyConfiguration`: residential inside mainland China, the input default.

### Output

One dataset row per placement.

```json
{
  "platform": "jd",
  "locale": "cn",
  "keyword": "洗发水",
  "page": 1,
  "position": 1,
  "id": "100178868918",
  "name": "维特丝洗发水男女士专用去屑止痒控油持久蓬松留香洗头膏",
  "price": 38.8,
  "currency": "CNY",
  "in_stock": true,
  "is_sponsored": true,
  "seller": "维特丝京东自营旗舰店",
  "shop_id": 1000116943,
  "self_operated": 1,
  "good_rate_pct": 99,
  "comments_bucket": "200万+",
  "cid1": 16750,
  "cid2": 16751,
  "cid3": 16756,
  "ad_type": 3,
  "total_results": 7599,
  "product_url": "https://item.jd.com/100178868918.html",
  "captured_at": "2026-09-12T03:02:04.988Z"
}
```

`brand`, `original_price` and `rating_count` are null on this feed. `rating` mirrors `good_rate_pct`, so it is a positive review percentage out of 100, not a five star average. Read `good_rate_pct` and ignore `rating`.

### Use cases

- Ad monitoring: group `seller` and `shop_id` by `position` to see who dominates the paid shelf.
- Category poaching: compare `cid1` to `cid3` against your own category to catch advertisers bidding outside their shelf.
- First party versus marketplace advertising split, from `self_operated`.
- Price positioning of advertisers, from `price` at each `position`.
- Advertiser trust benchmarking from `good_rate_pct` and `comments_bucket`, to see if higher rated shops hold better slots.

### Notes and limits

- Every row is a paid placement. This actor does not report organic rank. For that, use the JD.com Catalogue by Category actor.
- A keyword with no ad inventory legitimately returns zero rows and is counted as empty in the run stats. That is a real answer about the keyword, not a failure.
- `pages` is capped at 10 per keyword. A verified capture of `洗发水` at `pages: 2` returned 46 placements, all sponsored.
- A residential proxy inside mainland China is the recommended default. In a parallel verified run from a non-China exit, two of three keywords returned placements and the third was refused, so an in-country exit makes captures reliable.
- Results are deduplicated by SKU within a keyword, so a placement repeated across pages keeps its first position.

### FAQ

**Do I need a proxy?** Residential inside mainland China (country CN) is recommended and is the input default. Other exits are refused unpredictably.

**How many results can I get?** Up to 10 pages per keyword at roughly 24 placements per page. A verified two page capture returned 46 rows.

**Does it need a login or an API key?** No. No JD account and no API key.

**Why is every row marked sponsored?** Because the feed behind this actor is JD's advertising search surface. Reporting the rows as organic would be wrong, so they are flagged honestly.

# Actor input Schema

## `keywords` (type: `array`):

Search keywords to rank. Duplicates are ignored.

## `locale` (type: `string`):

Which storefront / locale.

## `pages` (type: `integer`):

Result pages to capture per keyword. Leave at 0 to capture every result page; the run stops as soon as the results end.

## `delayMs` (type: `integer`):

Pause between page fetches.

## `callsPerSession` (type: `integer`):

Re-mint the session after this many page fetches.

## `proxyConfiguration` (type: `object`):

On the Apify platform this decides egress. A residential proxy in the storefront's country is recommended (CN for the default). On our own servers it is ignored and our residential proxy is used.

## Actor input object example

```json
{
  "keywords": [
    "洗发水"
  ],
  "locale": "cn",
  "pages": 0,
  "delayMs": 1200,
  "callsPerSession": 60,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CN"
  }
}
```

# Actor output Schema

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

One row per search result position.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# 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 = {
    "keywords": [
        "洗发水"
    ],
    "pages": 0
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/jd-rank").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 = {
    "keywords": ["洗发水"],
    "pages": 0,
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/jd-rank").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 '{
  "keywords": [
    "洗发水"
  ],
  "pages": 0
}' |
apify call ikmal_suzali_atr/jd-rank --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/jd-rank"
        }
    }
}
```

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/Qy1etlJNT4HghzFvq/builds/obFIvEeVnLo0cbhM5/openapi.json