You wrote something you were pleased with, posted it, and four hours later it has two comments. Was that good? Bad? Normal for a Tuesday?
Most owners have no idea, and it is not because the numbers are hidden. The counts are right there on the post. The problem is that a raw count is meaningless without a baseline, and almost nobody has built one.
What can I actually see on one of my posts?
Every Skool post shows you who commented, how many people did, and the likes it collected. That is genuinely most of what matters for a community post, because a community post is not trying to get impressions — it is trying to start a conversation.
Skool changes its surfaces from time to time, so check your own community rather than trusting a description of what a post page shows. Look for whatever aggregate view exists in your admin area too; if there is a top-posts or activity summary, that is a faster route than clicking through individual posts.
What is worth internalising is the hierarchy of signals:
- Comments from different people — the strongest signal. Several distinct humans chose to type something.
- Comment depth — replies to replies. A thread is worth more than five one-liners.
- Likes — cheap to give, so a weak signal on their own, but useful as a floor for how many people saw the thing.
- New commenters — someone who has never commented before commenting now is worth more than your three regulars showing up again.
That last one is underrated. If the same four people comment on everything, your comment count is measuring your four friends, not your community.
How long should I wait before judging a post?
Wait roughly 72 hours before judging a Skool post, which is the single most useful discipline in post analysis and costs you nothing.
A post's engagement does not arrive instantly. People check in across days, and different members are online at wildly different times — which is a separate problem covered in the best time to post on Skool. If you judge a post at hour two you are mostly measuring who happened to be online at hour two.
Give a post roughly 72 hours to mature before you decide anything about it. Skoolgrades computes its peer benchmark on matured, 72-hour-old posts for exactly this reason: comparing a fresh post against a settled one is comparing two different things and will make your numbers swing for no real reason.
The practical version: do not review posts the day you publish them. Review last week's posts this week.
How do I know what a good post looks like for my community?
There is no universal benchmark for what a good Skool post looks like, and you should be suspicious of anyone who gives you one — community size, niche, price point and culture all move it enormously. A 400-member paid mastermind and a 12,000-member free community are not on the same scale.
Build your own instead. It takes twenty minutes once.
- List your last ten posts that are at least 72 hours old.
- For each, write down: distinct commenters, total comments, and whether any commenter was new.
- Take the median of distinct commenters. Not the mean — one viral post will distort a mean badly.
- That median is your baseline. A post that beats it clearly did something right. A post well below it did not land.
Worked example, entirely hypothetical: if your last ten posts drew 3, 5, 2, 9, 4, 3, 6, 2, 4 and 5 distinct commenters, your median is 4. The 9 is worth studying — what was different about it? The two posts that drew 2 are worth studying too.
Then convert to a rate so it stays honest as you grow. If 4 distinct people commented and you have 500 members, that is 0.8%. As your membership doubles, holding 4 commenters means your rate halved. See how to calculate Skool engagement rate for the fuller version.
A post count you cannot compare to anything is trivia. The same count next to your own median is a decision.
What should I look at when a post does well?
When a post beats your baseline, look at four things — format, ask, timing and who replied — because the point is working out what is repeatable rather than celebrating.
- Format. Question, story, resource, poll, announcement, win-share? Formats have very different comment profiles, and polls in particular lower the cost of participating to almost nothing.
- Ask. Did the post end with a specific, easy question, or did it end with a full stop? "What's your take?" underperforms "Which of these two would you have done?" almost every time, because the second is easier to answer.
- Timing. Did it go out when your people are actually around?
- Who replied. Regulars only, or new faces? A post that pulls a first-ever comment out of a lurker is doing something a post that pleases your regulars is not. That is the mechanic behind activating lurkers.
Do this for four or five posts and you will have a short list of things that work in your specific room. That list is worth more than any general advice article, including this one.
What won't post numbers tell me?
Post-level numbers have two honest limits: they arrive too late to act on, and they measure reaction rather than value.
They are lagging. By the time you know a post worked, the moment has passed. Post analytics tell you what to do more of next month; they do not help you decide what to write this morning. For that you need to look at what your members are engaging with — which is a different question, covered in how to find posts that are working on Skool.
They measure reaction, not value. A post can generate twenty comments of pure noise and change nothing. Another can get three comments, one of which is a member saying the thing that made them stay. Engagement counts are a proxy for value, and proxies drift. Keep reading the actual comments, not just counting them.
How does Skoolgrades measure whether a post worked?
Skoolgrades collects posts and comments through a Chrome extension running on your own logged-in Skool session — no Skool API, no datacenter traffic. It is not affiliated with or endorsed by Skool.
On the reporting side, the Business Dashboard includes top posts, participation rate and timing readouts, plus a peer benchmark: your engagement rate against comparable communities, computed on matured 72-hour posts so it does not lurch every time you publish. Reports are included on every Skoolgrades plan.
The word "participation" there is doing real work, and it is worth pinning down because it is where most disagreements about engagement come from. Skoolgrades reports a participation rate: the share of members who genuinely interacted with a post — a comment, a comment reply, or a poll vote. A member counts only if they actually did something. A visit-based engagement rate, by contrast, counts a member who opened the page once in the window and did nothing at all, and as of July 2026 Skool's own dashboard reports engagement on a visit basis. Check yours, since Skool ships changes often. The visit-based number is always the bigger and more flattering one, which is why a community can look healthy on that measure while the feed is silent. Participation is smaller, harsher, and the number that actually moves when a post lands.
Two limits to be straight about. Engagement counting is comments plus polls — per-post liker capture was deliberately dropped, so there is no like-level breakdown of who liked what, and participation therefore means comments plus poll votes. And communities over roughly three thousand active members are sampled with a frame of around nine hundred members, which makes their figures estimates.
On the forward-looking side, Content Gems ranks original post ideas across a judged external network and your own back catalogue, with a tray explaining why each idea surfaced and a list of the members it should reach. That is the part that answers what to post in your community rather than what already happened.
So how do I tell if a post actually worked?
A post worked if it beat your own recent median for distinct commenters, and the numbers you need are already on the post. What is missing is context, and context is something you build rather than something a dashboard hands you.
Wait 72 hours. Count distinct commenters, not total comments. Take the median of your last ten as a baseline. Study the outliers in both directions. Convert to a rate so growth does not flatter you. That routine costs you twenty minutes a week and will teach you more about your community than any benchmark number from someone else's.