Weibo Scraper — Posts, Profiles, Comments & Hot Search

Pull public Weibo posts, profiles, comments, likers, and the realtime hot-search board into one flat dataset. No Weibo developer account and no API key. Paste a post id, a user id, or a URL.

Input	Rows
Post mid, bid, or detail URL	One post
User id or profile URL	One profile
Same post id, comments or likers	One row per comment or liker
Hot search	One row per board entry
Keyword plus your logged-in cookie	Search hits inside a date window
User id plus your logged-in cookie	Fans, or accounts that user follows

HTTP only. No browser. Search, fans, and following need a cookie from your own logged-in Weibo session. The other five operations do not.

Operation	Login	What you get
weiboDetail	No	One post
userDetail	No	One profile, including follower counts
comments	No	Comments, newest pages first
likers	No	Accounts that liked the post
hotSearch	No	Current 热搜 list
searchWeibo	Your cookie	Posts matching a keyword and date window
userFans	Your cookie	Accounts that follow the user
userFollowing	Your cookie	Accounts the user follows

Why Use This Scraper?

• Post text, counts, pictures, and the author, from a mid or a m.weibo.cn/detail URL.
• Profile stats that the post payload leaves empty: followers, following, posts, verification.
• Comments and likers on a public post, page by page.
• The realtime 热搜 board, with rank and heat.
• Keyword search, fans, and following when you paste your own SUB cookie.
• One operation per run, so the dataset stays one shape.

Overview

This actor reads public Sina Weibo pages for social listening, creator research, and China trend tracking. Each run does one job and writes flat rows to the Apify dataset. Export JSON, CSV, or Excel from that dataset.

A post row does not include follower counts. Those sit on the profile operation. Hot search is a live board, so the same word will not hold the same rank an hour later.

Schedule a guest operation from the Apify console the same way you would any other actor. Leave cookie empty on those schedules. A search or fan schedule has to store the cookie in the task input, which means anyone who can open that task can read the session. Prefer a one-off run when the cookie is yours.

The dataset is the whole result. Download it as JSON, CSV, or Excel from the run, or read it with the Apify API. Rows from different operations should not be mixed in one run, because the columns change with _operation. Filter on _operation if you merge exports later.

Supported Inputs

Guest operations accept:

• A numeric post id (mid), for example 5249718969175092
• A short bid, for example QkRpSCuRm
• https://m.weibo.cn/detail/5249718969175092
• https://weibo.com/7961606632/QkRpSCuRm
• A numeric user id, or https://weibo.com/u/7961606632
• Hot search needs no id

Login operations accept:

• searchWeibo: a keyword such as 北京 or Tesla, optional startDay and endDay (YYYY-MM-DD). Default window is the last 30 days in China time.
• userFans and userFollowing: the same user id as the profile operation.
• cookie: the Cookie header from a logged-in weibo.com tab. It must contain SUB=.

Not supported:

• A user timeline of their posts
• Reposts of a post
• Private accounts, or fan lists the account has hidden
• Search, fans, or following with only the automatic visitor session

Use Cases

Who	What they take
Brand teams	Hot-search words and posts that mention a name
Creator research	Profile stats, verification, bio
Community research	Comments and likers on a post
Agencies	A flat sheet they can hand to a client
Analysts	Date-window search, once they supply their own cookie

How It Works

1. You pick one operation and paste the id, URL, or keyword.
2. For guest operations the actor mints a visitor session and requests Weibo's public JSON.
3. For search, fans, and following it sends the cookie you pasted and does not replace it with the visitor session.
4. Rows land in the dataset. maxItems stops the run early. maxPages caps comments, likers, search, fans, and following at 50 pages.

Input Configuration

Field	Type	Required	Notes
operation	string	No	Default weiboDetail. One of weiboDetail, userDetail, comments, likers, hotSearch, searchWeibo, userFans, userFollowing.
weiboId	string	For post, comments, likers	Mid, bid, or post URL. Prefill 5249718969175092.
userId	string	For profile, fans, following	UID or profile URL. Prefill 7961606632.
keyword	string	For search	Example 北京.
startDay	string	No	YYYY-MM-DD. Default 30 days ago, China time. Search only.
endDay	string	No	YYYY-MM-DD. Default today, China time. Search only.
maxPages	integer	No	Default 5, min 1, max 50.
maxItems	integer	No	Hard cap on rows. No default.
cookie	string	For search, fans, following	Cookie header including SUB=.
proxy	object	No	Leave empty to use the built-in residential proxy.

Example: one post

{
  "operation": "weiboDetail",
  "weiboId": "5249718969175092"
}

Example: comments, capped

{
  "operation": "comments",
  "weiboId": "https://m.weibo.cn/detail/5249718969175092",
  "maxPages": 2,
  "maxItems": 50
}

Example: search with your cookie

{
  "operation": "searchWeibo",
  "keyword": "北京",
  "startDay": "2026-08-22",
  "endDay": "2026-09-21",
  "maxPages": 1,
  "maxItems": 20,
  "cookie": "SUB=...; SUBP=..."
}

Output Overview

Every row has _operation so you can tell which mode produced it. Post rows and search rows share the post fields. Profile, fan, and following rows share the user fields. Comment and liker rows point back at weiboId. Hot-search rows are a word, a rank, and a heat number.

Follower counts on a post row are often null. Run userDetail for that author's counts.

Output Samples

Live rows from 21 Sep 2026. Long text and signed image URLs are shortened.

Post (weiboDetail)

{
  "_operation": "weiboDetail",
  "weiboId": "5249718969175092",
  "bid": "QkRpSCuRm",
  "weiboPageUrl": "https://m.weibo.cn/detail/5249718969175092",
  "text": "#檀all[超话]#\n2025.12.31 24小时文手挑战：1:00\n\n白晓宇《北京爱情故事》…",
  "textLength": 3071,
  "isLongText": true,
  "postedAt": "Wed Dec 31 01:00:00 +0800 2025",
  "repostCount": 19,
  "commentCount": 36,
  "attitudeCount": 169,
  "regionName": "发布于 辽宁",
  "source": "JCT全肯定Android",
  "topics": ["檀all[超话]"],
  "picCount": 1,
  "screenName": "白兔猫-休养补水版",
  "userId": "7961606632",
  "verified": true,
  "followersCount": null,
  "userPageUrl": "https://weibo.com/u/7961606632"
}

Profile (userDetail)

{
  "_operation": "userDetail",
  "userId": "7961606632",
  "screenName": "白兔猫-休养补水版",
  "verified": true,
  "verifiedReason": "娱乐博主",
  "description": "做点自己爱吃的🍚",
  "location": "其他",
  "gender": "f",
  "followersCount": 4163,
  "friendsCount": 295,
  "statusesCount": 6800,
  "userPageUrl": "https://weibo.com/u/7961606632",
  "birthday": "巨蟹座",
  "createdAt": "2024-11-13 18:46:30"
}

Comment

{
  "_operation": "comments",
  "weiboId": "5249718969175092",
  "commentId": "5251110719197355",
  "text": "晓宇我要在你能看见的日子里让你死死记住我的样子",
  "postedAt": "01-03",
  "source": "来自 辽宁",
  "likeCount": 1,
  "userId": "5874145289",
  "screenName": "Hoo味优酸乳_家有影帝版",
  "followersCount": 121,
  "userPageUrl": "https://weibo.com/u/5874145289"
}

Liker

{
  "_operation": "likers",
  "weiboId": "5249718969175092",
  "attitudeId": "5331439927165740",
  "postedAt": "08-13",
  "source": "OPPO智能手机",
  "userId": "8257425031",
  "screenName": "vivi甜兔-忙碌营业版",
  "followersCount": 2,
  "userPageUrl": "https://weibo.com/u/8257425031"
}

Hot search

{
  "_operation": "hotSearch",
  "rank": 1,
  "word": "钟南山团队发现肺结节发病新趋势",
  "hotValue": 1119668,
  "label": "热",
  "searchUrl": "https://s.weibo.com/weibo?q=%E9%92%9F%E5%8D%97%E5%B1%B1%E5%9B%A2%E9%98%9F%E5%8F%91%E7%8E%B0%E8%82%BA%E7%BB%93%E8%8A%82%E5%8F%91%E7%97%85%E6%96%B0%E8%B6%8B%E5%8A%BF"
}

Key Output Fields

Post and search: weiboId, bid, text, postedAt, repostCount, commentCount, attitudeCount, topics, picUrls, screenName, userId, keyword (search only).

Profile, fans, following: userId, screenName, verified, verifiedReason, followersCount, friendsCount, statusesCount, description, sourceUserId (fans and following).

Comments and likers: weiboId, commentId or attitudeId, text, likeCount, screenName, userId.

Hot search: rank, word, hotValue, label, searchUrl.

Pricing

Charges are per result row, once prices are set on the actor. Until then a run bills Apify platform usage only.

Event	When
weibo-detail-result	One post row
user-profile-result	One profile row
comment-result	One comment
liker-result	One liker
hot-search-result	One hot-search row
search-weibo-result	One search hit
user-fans-result	One fan
user-following-result	One followed account

An empty or failed run does not emit those events. Set maxItems when you want a ceiling.

What makes this richer than the competition

Capability	Typical Weibo actors	This actor
Comments and likers	Often missing	Guest, no login
Hot-search board	Often missing	Guest, no login
Post and profile	Common	Guest, no login
Keyword search with a date window	Often bundled behind the developer's own accounts	Your cookie, your session
Fan and following lists	Same	Your cookie, your session

Notes & limitations

• Search, fans, and following return nothing useful on a visitor session. The run fails with a login message instead of writing a fake empty list.
• Many accounts hide fans or following. A logged-in cookie can still get an empty list.
• There is no user-timeline mode and no repost mode.
• Post detail leaves followersCount null. Use the profile operation.
• Hot search is live. Ranks move.
• Image URLs from Weibo can expire.
• The cookie is used as a request header and is not written into the dataset. Do not put it in a schedule that other people can open.
• Search dates are sent as timescope=custom:YYYY-MM-DD:YYYY-MM-DD on the public search page. A window wider than maxPages still returns only those pages, about 10 to 20 posts each.
• Default memory is 256 MB. That is enough for these HTTP calls. Raising memory does not unlock search without a cookie.

FAQ

Do I need a Weibo account? Not for a post, a profile, comments, likers, or hot search. You need your own logged-in cookie for search, fans, and following.

Why is search behind a cookie? Weibo serves keyword search and the friend graph only to a logged-in session. This actor does not keep a shared Weibo account.

Can I scrape someone's full post history? No. There is no timeline operation.

What if the fan list is empty? Either the account hid it, or the cookie is not logged in. A logged-out cookie fails the run. A logged-in cookie with an empty list writes one note row.

Which id do I paste? The long number in m.weibo.cn/detail/{id} is the post. The number in weibo.com/u/{id} is the user.

Support

Open an issue on the actor page: memo23/weibo-scraper issues. Include the operation, the id you used, and whether a cookie was set. Do not paste the cookie into the issue.

Additional Services

Need a timeline, a fixed export, or a schedule around a keyword list? Say what the sheet has to look like via the actor issues, or see the rest of the memo23 actors.

Explore More Scrapers

• Douyin Scraper
• RedNote Search Scraper
• RedNote Comments Scraper
• RedNote User Profile Scraper
• All memo23 actors

🤖 For AI Agents & LLM Apps

Compact reference for agents calling this actor via the Apify MCP server or the Apify API (memo23/weibo-scraper).

Purpose: public Weibo posts, profiles, comments, likers, and hot search without a login. Search, fans, and following need the caller's own cookie.

Minimal input:

{ "operation": "weiboDetail", "weiboId": "5249718969175092", "maxItems": 1 }

Output: one flat row per result. Post fields include weiboId, bid, text, postedAt, repostCount, commentCount, attitudeCount, screenName, userId. Profile fields include followersCount, friendsCount, verifiedReason. Hot search fields are rank, word, hotValue.

Behaviors an agent should know:

• Set maxItems. Hot search and comments can be long. maxPages defaults to 5 and caps at 50.
• One operation per run. weiboDetail does not fill followersCount. Call userDetail for that.
• searchWeibo, userFans, and userFollowing fail without a cookie that contains SUB=.
• Do not send a visitor cookie and expect search to work.
• Per-row charge events exist. Until Store prices are set, budget for platform compute only.

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Weibo Corporation or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

Guest operations read publicly available Weibo pages. Search, fans, and following send only the cookie you provide and return what that session can already see. This actor does not bypass login, access private accounts, or collect passwords. You are responsible for complying with Weibo's Terms of Service, applicable data-protection law (GDPR, CCPA, and others), and your own obligations.

SEO Keywords

weibo scraper, scrape sina posts, weibo.com comments export, Apify China social, hot search board, creator profile export, fan list export, keyword date search, KOL research, brand monitoring China, liker list, post detail JSON, profile followers, public weibo dataset, China trend tracking