Reach dropped
What to check and what not to do in the week everything went quiet.
The prompt
You analyse social. Diagnose a drop in reach. Before and after: {numbers over two or three weeks} What you posted those days: {topics and formats} What you did differently: {if anything} Followers: {number} Check in order: 1. How many days the drop has lasted. Two days is not a drop, it is two days. Reacting before a week means fixing something that is not there. 2. What changed on your side: posted less often, stopped replying, changed subject, started adding links. 3. Outbound links: almost everywhere they suppress reach. Check whether the start coincides with their appearance. 4. Format: whether you drifted into one type of post. Feeds tire of sameness faster than of bad. 5. The calendar: holidays, summer, major events. They move numbers more than your work does. 6. What to do this week: one change, not five. With five you will not know which worked. 7. What not to do: delete posts, double your posting rate, buy anything, change subject. A two or three week dip is normal, not a fault. The problem starts when it lasts a month with your work unchanged.
Anything in curly braces is yours to replace.
Example output
Nine days — worth looking at. Coincidence: from the 3rd every post carries a link to the site. There were no links before. Format: 8 list posts in a row. The feed is tired. One change this week: links move to the first comment. Watch for 7 days. Not doing: posting more often, deleting anything.
Related prompts
The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.
Write 20 opening lines for Threads posts on the topic "{topic}". Audience: {who} My role: {who you are to them — practitioner, seller, observer} Hard limits: — No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land. — No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past. — No caps lock, no emoji chains. Give 4 groups of 5: 1. Personal experience with a specific number or timeframe. 2. Disagreement with received wisdom in the niche. 3. An observation the reader recognises in themselves. 4. An open question they have something to answer from their own experience. After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Show sample resultHide sample
Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
Write a Threads post on the topic "{topic}" designed to pull replies. What I know about it: {your experience, facts, numbers} Audience: {who} What I want to hear in the replies: {e.g. how other people solve this} Rules: — No longer than 500 characters, that is the platform limit. 300 is better. — The first 90 characters must work as a standalone hook; the rest is what people unfold themselves. — End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice. — Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say. Don't do this: — "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to. — Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow. Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Show sample resultHide sample
Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
This prompt is part of the PRO collection
Unlock accessA link in the body sends people off-platform, and the feed accounts for that. The scheme: the post stands alone, the link comes as the first reply.
This prompt is part of the PRO collection
Unlock access