Weibo Hot Search & Brand Trend Tracker avatar

Weibo Hot Search & Brand Trend Tracker

Pricing

from $1.75 / 1,000 results

Go to Apify Store
Weibo Hot Search & Brand Trend Tracker

Weibo Hot Search & Brand Trend Tracker

Track public Weibo hot-search topics and selected brand keywords, returning structured ranks, trend changes and alert-ready signals for social listening and market monitoring.

Pricing

from $1.75 / 1,000 results

Rating

0.0

(0)

Developer

Rafael Barreto Haddad

Rafael Barreto Haddad

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Track public Weibo hot-search topics and selected brand keywords, returning structured ranks, trend changes and alert-ready signals for social listening and market monitoring.

Why use this Actor

Brand and research teams need fast, structured Weibo trend alerts with change context rather than a static hot-search list.

Key features

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

{
"trackedKeywords": [
"AI"
],
"maxResults": 10,
"onlyMatched": false,
"previousSnapshot": []
}

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

  • trackedKeywords — Tracked keywords: Optional brand, competitor, product or topic strings to flag inside the current Weibo hot list.
  • maxResults — Maximum trends: Maximum hot-search rows returned.
  • onlyMatched — Only matched tracked keywords: Return only rows containing a tracked keyword.

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

Detailed documentation

Detailed documentation

Detailed documentation

Detailed documentation

Detailed documentation

Detailed documentation

Track public Weibo hot-search topics and matched brand keywords, returning structured trend ranks, deltas and alert-ready results.

A static hot-search list is useful for browsing; a monitored, scored list is more useful for operations. This Actor turns Weibo public hot search into repeatable brand and trend intelligence.

Why use this Actor

This Actor is built for users who need structured evidence and a decision layer rather than a pile of raw HTML. It extracts public-source data, normalizes the records, assigns deterministic scores that can be inspected, and emits compact actions suitable for people, APIs, MCP clients, and autonomous agents. The design favors lightweight HTTP execution where the source permits it and fails explicitly when a source blocks access instead of silently inventing rows. Snapshot input can be reused across scheduled runs to turn one-time extraction into monitoring.

Key features

  • Public Weibo hot-search JSON extraction.
  • Rank, heat, labels and tracked-keyword matching.
  • Exact rank and heat deltas from a previous snapshot.
  • Deterministic trendScore.
  • ALERT_TRACKED_BRAND, ALERT_HIGH_PRIORITY, WATCH and MONITOR actions.

Input

Optionally provide tracked brand/topic keywords, output size, matched-only filtering and a previous snapshot.

Output

Each row is one hot-search trend with normalized rank/heat evidence, change intelligence and agentAction.

Example

{
"trackedKeywords": [
"AI"
],
"maxResults": 10,
"onlyMatched": false,
"previousSnapshot": []
}

The default dataset contains one billable decision-ready row per extracted entity. Aggregate summaries and reusable snapshots are stored in the default key-value store when applicable. Scores are deterministic heuristics, not claims of certainty.

Use cases

  • China brand reputation monitoring.
  • Newsroom and trend research.
  • Campaign/event monitoring.
  • Agent-triggered alerts.

Pricing

Initial benchmark price: US$0.0025 per trend row before tier discounts.

The Actor uses pay-per-event pricing. The primary event is one qualified row written to the default dataset. The product is designed to keep platform cost materially below the event price at normal workloads; the factory rechecks margin from live validation runs before publication.

Limitations

v1 targets Weibo hot search rather than arbitrary post search. Heat values are platform-provided signals and can change meaning over time.

Public web sources change. A successful extraction today is not a contractual guarantee that a source will preserve the same markup tomorrow. Anti-bot systems, regional network behavior, deleted content, private accounts, and login-only data can reduce coverage. This Actor does not bypass account access controls and does not claim access to private data. Use the output as operational evidence and revalidate high-stakes decisions against the original source.