Teams searching for how to scrape Xiaohongshu posts usually need a research dataset, not a generic crawler. The Xiaohongshu Post Details Scraper turns selected RedNote post URLs into CSV rows with post metadata, images, authors, engagement counts, comments, timestamps, locations, and replies.
Problem
Why Xiaohongshu post research breaks in browser tabs
Xiaohongshu research often starts with a product review, creator collaboration, trend post, travel recommendation, or brand mention. Trouble starts when the team must compare dozens of posts and comments. Screenshots are hard to search, copy-paste separates comments from metadata, and engagement counts lose their source URL.
That is the pain behind queries like xiaohongshu post details scraper, rednote comments scraper, and xiaohongshu sentiment analysis. The practical job is precise: convert visible post detail URLs into auditable rows.
A Xiaohongshu comment row is useful only when the team can trace it back to the post URL, post title, visible author context, collection date, and the exact preprocessing choices used for translation or sentiment labels.
Xiaohongshu can require login, verification, or a current post URL token before a detail page renders. The template produces a diagnostic row when the detail page is not loaded.
Personas
Who uses a RedNote comments scraper?
| Persona | Manual pain | CSV outcome |
|---|---|---|
| Consumer researchers | Browser notes cannot be coded consistently. | Export post URLs, comments, authors, locations, timestamps, likes, replies, and post metadata. |
| Newsrooms | Trend stories need verifiable examples, not loose screenshots. | Preserve source URLs and visible comment rows for editor review. |
| SEO and content teams | RedNote posts reveal how users describe categories, brands, routines, and alternatives. | Build briefs from repeated phrases, questions, comparisons, and sentiment patterns. |
| Brand monitoring teams | Negative comments and creator reactions can move faster than monthly reports. | Re-run a known post list and compare comment themes, replies, and engagement. |
| Agencies and influencer analysts | Creator shortlists need evidence from post reactions, not only follower counts. | Pair profile links with comment quality, likes, favorites, and reply context. |
Template
How this Xiaohongshu post details scraper creates the export
The current workflow lives on the Xiaohongshu Post Details Scraper template page. Import the JSON template rather than rebuilding the automation from memory.
The template uses a multi-URL loop: add current post detail URLs to the Navigate block, let UScraper open each URL, wait for the rendered page, expand visible comment or reply controls where possible, normalize rows in the page, and append them to one CSV.
Set Window Size -> Navigate -> Wait for Page Load -> Sleep
-> Wait for body -> Inject JavaScript extraction -> Sleep
-> Wait for .uscraper-xhs-row -> Structured Export -> Loop Continue
The JSON export defines the row selector as .uscraper-xhs-row and writes to rednote-post-details-scraper.csv in append mode. The authoritative workflow description is the template JSON; the article explains where it fits in a research process.
rednote-post-details-scraper.csvColumn
page_url
The Xiaohongshu or RedNote post URL processed in the current loop.
Column
image
Pipe-separated image URLs detected from the post detail page.
Column
title
Post title, or a diagnostic status when the detail page is unavailable.
Column
user_name
Visible post author name.
Column
personal_file_link
Author profile URL when present in the rendered page.
Column
likes_amount
Visible post like count.
Column
favorite_amounts
Visible favorite or collect count.
Column
comment_amount
Displayed comment count or detected visible comments.
Column
comments_replies
Combined visible comment and reply text for post-level review.
Column
comment_author
Author label for the exported comment row.
Column
comment_author_location
Location text parsed from comment metadata when visible.
Column
datetime
Relative or absolute comment timestamp text.
Column
comment
Comment body for the current row.
Column
comment_like_count
Visible like count for the comment.
Column
comment_reply_count
Visible reply count or detected reply total.
Column
replies
Visible replies joined into one cell.
Sample rows
1 of many
| page_url | image | title | user_name | personal_file_link | likes_amount | favorite_amounts | comment_amount | comments_replies | comment_author | comment_author_location | datetime | comment | comment_like_count | comment_reply_count | replies |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| New skincare routine review | beauty.notes | 1268 | 342 | 48 | Does it work for sensitive skin? | Mia | Shanghai | 06-02 | Does it work for sensitive skin? | 15 | 2 | I tried it for a week | Same question |
Workflows
Concrete Xiaohongshu sentiment analysis workflows
Brand perception review
Export comments from campaign, creator, or search URLs. Classify repeated praise and complaints while keeping the source URL beside every label.
Newsroom evidence table
Build a spreadsheet of posts and visible comments around a trend. Use the CSV as an index for sources, screenshots, translations, and editor checks.
SEO language mining
Extract comments from posts in a category, then cluster repeated phrases, questions, alternatives, ingredients, places, and use cases for content briefs.
Influencer shortlist validation
Compare comment quality under sponsored, organic, and competitor posts. Look for real discussion, location relevance, objections, and reply depth.
Monitoring known issues
Re-run the same post list after a launch, recall, press cycle, or creator controversy. Track which comments and reply themes need escalation.
For discovery-first work, use a Xiaohongshu search workflow before this post-detail step. For other exports, browse the UScraper template library or the UScraper blog.
Decision
When UScraper fits as an Octoparse Xiaohongshu alternative
There are several ways to collect RedNote or Xiaohongshu data: Octoparse has a post details template, Apify has API actors, GetOdata offers an all-in-one scraper, and Thunderbit publishes a no-code Xiaohongshu scraper.
UScraper is the better fit when the deliverable is a local CSV, the analyst wants to watch the browser state, and the team wants editable workflow blocks rather than a black-box API run.
| Route | Best fit | Trade-off |
|---|---|---|
| UScraper local desktop template | Supervised post URL batches, visible QA, editable steps, and CSV files on disk. | Best for reviewed batches, not unattended large-scale ingestion. |
| Hosted no-code scraper | Managed browser infrastructure, dashboards, or cloud scheduling. | Data custody, billing model, and extraction logic live with the provider. |
| API or actor platform | Programmatic jobs, JSON delivery, integrations, or scheduled pipelines. | Requires credentials, usage monitoring, and production compliance review. |
| Custom Python scraper | Full engineering control. | Request signing, tokens, selectors, and access checks can create ongoing maintenance work. |
QA
Validation checklist before you scrape Xiaohongshu posts at scale
- Save the exact post URL list, collection date, browser account state, and project purpose.
- Run five to ten posts first, then compare the CSV beside the browser.
- Keep raw text, translations, sentiment labels, and analyst notes in separate columns.
- Treat blank likes, favorites, comments, locations, or replies as QA signals, not zeros.
- Keep diagnostic rows in the file until review is complete; they explain redirects, expired tokens, login prompts, or unavailable posts.
- Avoid collecting sensitive personal data, private content, deleted material, or content behind access controls.
FAQ
Xiaohongshu post details scraper FAQ
Research teams, newsrooms, SEO teams, brand monitoring teams, agencies, and influencer analysts use it when they need post URLs, titles, authors, engagement counts, comments, timestamps, locations, and replies in a reviewable CSV.
Next step
Download the Xiaohongshu Post Details Scraper
Use the Xiaohongshu Post Details Scraper template when your team has a defined RedNote post list and needs a local CSV for research, monitoring, SEO, or sentiment review. Run a small batch first, inspect the diagnostic rows, then expand only after the export matches what you see in the browser.