Weibo Hot Search Scraper

The Actor saves Weibo's hot-search board as it stands right now, one row per entry.

{
  "maxItems": 100
}

Accepted input

Nothing is required. The board is the board — there is no query to give it and no account to point it at. maxItems is there only as a bound on how many entries are saved, defaults to 100, and 0 disables it; the board is normally well inside that.

Result fields

Every row carries the board entry exactly as Weibo returns it — its rank, its keyword, its heat and whatever tag the platform has put on it — passed through whole rather than narrowed down to a list somebody chose once. count is how many entries the board held at that moment.

Why this one wants a schedule

The board is a snapshot and nothing else republishes it. An entry that was at the top an hour ago may be gone, and once it is gone there is no way to ask what it was.

Because the Actor needs no input, it can sit on a schedule unattended. Run it hourly and the dataset becomes a history of what China was searching for, which is a thing you can only build going forward — you cannot backfill it later.

Empty is an answer, and a failure is a failure

If the board itself comes back with nothing, that is the board's answer and the run reports it as one: no rows, nothing charged, run succeeds.

A run that could not reach the backend fails loudly instead, and so does a response in a shape this Actor does not recognise. An empty dataset always means "the board was empty" — it never stands in for a request that went wrong. That distinction is what makes a scheduled history trustworthy: a gap in it is a real gap, not a quiet failure.

Related Actors

To search accounts by keyword, use the Weibo User Search Scraper. To read a post one of these trends points at, use the Weibo Post Scraper. For all of these behind one mode selector — including topic search — use the All-in-One Weibo Scraper.