Xiaohongshu topic planner

Plan Xiaohongshu Topics

Turn user situations and business evidence into a sustainable publishing system. Do not create a calendar of interchangeable generic topics.

Inputs

Use the account promise, target reader, current account stage, offer, price or decision complexity, recent goal, available proof, material sources, production capacity, existing posts, frequent questions, objections, and desired period. State assumptions when inputs are incomplete.

Topic source map

Build topics from:

• user questions, searches, comparisons, anxieties, and decision criteria;
• work processes, tools, checklists, mistakes, and acceptance rules;
• product use, implementation, limits, service, and aftercare;
• real cases, experiments, before/after mechanisms, and failed assumptions;
• comments, consultations, sales objections, and non-buying reasons;
• policy, market, or product changes that can be verified when current information is required.

Topic jobs

Give every topic one primary job:

Job	Reader need	Useful formats
Discovery	“This is about my situation”	scene, tension, mistake, observation
Search	explicit question or decision	tutorial, comparison, checklist, FAQ
Trust	judge competence and boundaries	process, evidence, case, failure review
Proof	validate a claim	demonstration, test, documented result
Conversation	contribute an experience or question	judgment, trade-off, prompt
Conversion	understand fit and next step	suitability, objection, delivery, FAQ
Retention	return for a series	progressive lessons, templates, updates

Workflow

1. Define three to five content pillars from the account promise and proof.
2. Translate each pillar into explicit reader situations and search intents.
3. Create topics with one job, one reader state, one primary keyword, and one value contract.
4. Record the proof or material required. Remove topics that depend on invented evidence.
5. Balance the calendar across search answers, execution methods, cases or experiments, and decision checklists.
6. Sequence topics so each post creates a useful follow-up rather than repeating the same claim.
7. Add a reuse path: comment follow-up, FAQ, carousel, short video, case update, or pinned post.
8. Assign one observable learning goal to each post. Do not promise a target result.

Output

Return:

1. account promise and content pillars;
2. current reader questions and decision stages;
3. prioritized topic pool grouped by job;
4. calendar with topic, intent, keyword, angle, proof, format, desired action, and learning goal;
5. series plan and reuse map;
6. material gaps and next production actions.

If the user specifies a publishing period, build that calendar. Otherwise provide a prioritized seven-post sample. When the user requests four posts per week, avoid four versions of one topic: use search answer, execution method, case/experiment, and decision/checklist as the default operating mix unless the evidence suggests a better mix.

Guardrails

Do not invent search volume, trends, cases, user data, platform rules, or performance. Do not treat a fixed posting frequency or content ratio as an algorithm requirement. Do not copy benchmark wording or use unrelated trending terms.