From xiaohongshu-complete-skills
Analyzes Xiaohongshu traffic sources (discovery, search, followers, external) to understand views/engagement origins, optimize strategies, and diagnose changes.
npx claudepluginhub vivy-yi/xiaohongshu-skills --plugin xiaohongshu-complete-skillsThis skill uses the workspace's default tool permissions.
Traffic analysis is the systematic examination of where Xiaohongshu content views come from, helping creators understand which traffic sources perform best and how to optimize content strategy for maximum reach and engagement.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Traffic analysis is the systematic examination of where Xiaohongshu content views come from, helping creators understand which traffic sources perform best and how to optimize content strategy for maximum reach and engagement.
Use when:
Do NOT use when:
Before (ignoring traffic sources):
❌ "My post got 1000 views, good job!"
❌ "Why did views drop? Must be the algorithm"
❌ "All traffic is the same, 100 views = 100 views"
After (traffic-source driven):
✅ "Post got 1000 views: 70% from search (high intent), 20% from discovery (broad), 10% from followers (loyal)"
✅ "Views dropped because discovery traffic fell 60%, but search traffic stayed strong - optimize cover for discovery"
✅ "Search traffic converts 3x better than discovery - double down on SEO-optimized titles"
4 Traffic Sources Framework:
| Traffic Source | Characteristics | Conversion Rate | Optimization Strategy |
|---|---|---|---|
| Discovery | Algorithm-recommended, viral potential | 2-4% | Eye-catching covers, trending topics |
| Search | User-initiated, specific intent | 6-10% | SEO-rich titles, keyword optimization |
| Followers | Loyal audience, consistent | 10-15% | Consistent posting, community engagement |
| External | Shares, profile visits | Varies | Cross-platform promotion |
Xiaohongshu Creator Center (free, native):
Qiangua Data (recommended for deeper analysis):
For each post, document:
Calculate percentages:
Discovery % = (Discovery views ÷ Total views) × 100
Search % = (Search views ÷ Total views) × 100
Follower % = (Follower views ÷ Total views) × 100
Key metrics per traffic source:
Traffic quality assessment:
Analyze last 10-20 posts to find patterns:
Discovery-dominant posts (60%+ from discovery):
Search-dominant posts (50%+ from search):
Follower-dominant posts (70%+ from followers):
For Discovery Traffic:
For Search Traffic:
For Follower Traffic:
Build weekly traffic source log:
Week | Total Views | Discovery % | Search % | Follower % | Best Source
-----|-------------|-------------|-----------|------------|------------
W1 | 5,000 | 60% | 25% | 15% | Discovery
W2 | 8,000 | 70% | 20% | 10% | Discovery
W3 | 4,000 | 40% | 40% | 20% | Mixed
Trend analysis:
Sudden traffic drop?
Sudden traffic spike?
| Mistake | Why Happens | Fix |
|---|---|---|
| Ignoring traffic sources, only looking at total views | Easier to track one number | Always analyze traffic breakdown - 1000 discovery views ≠ 1000 search views |
| Assuming all traffic is equally valuable | Not all views convert the same | Track engagement/conversion by source - search converts 3x better |
| Optimizing for wrong traffic source | Chasing views instead of growth | Focus on search traffic for sustainable growth, discovery for viral spikes |
| Neglecting follower traffic | Obsessed with new views | Loyal followers provide consistent engagement - don't ignore them |
| Not tracking traffic source trends over time | Reactive instead of proactive | Build weekly traffic log to spot patterns before problems occur |
| Blaming "algorithm" for all changes | Easy scapegoat | Check specific traffic source - algorithm only affects discovery traffic |
| Over-optimizing for discovery only | High visibility, low conversion | Balance discovery (volume) with search (quality) for sustainable growth |
Case Study: Niche Beauty Account
Data-Backed Insights:
REQUIRED: Use data-analytics (overall data analysis framework) REQUIRED: Use data-metrics-understanding (understand what metrics mean)
Recommended for deeper analysis:
Use traffic-analysis BEFORE:
Related traffic optimization skills: