I posted the same comment in four different threads over a month. The views were 221, 15, 12, and 9.
byโข
Same effort every time, same comment, just a different thread each time. The spread came entirely from which thread I picked, not from anything I changed about what I wrote.
That has changed how I think about distribution. It stopped being a channel decision and became a research step before I write anything: how fresh the thread is, how many replies it already has, whether the person asking is actually going to read what comes back.
Curious how other people here think about this. Do you have a way of predicting which thread is worth the time before you write the comment, or is it mostly trial and error for you too?
221 views
Replies
I ran the same experiment without meaning to and got the same shape. Scraped every post I had made in a stretch and the distribution was brutal: the top 10% carried 67% of all the reach, and the median post got 14 views. Not a gentle curve, a power law. What I take from yours is that the 221 is not the interesting number, the 9 is. If identical writing lands at 9, then writing quality had nothing to do with the 221 either, and the thing you actually chose that day was the room. Placement is doing the work and craft is a rounding error next to it. The uncomfortable follow-on is that most of us are optimising the part we control and enjoy, rather than the part that decides the outcome. Did the 221 thread differ on views, or on how recently someone had commented in it? Those two look identical from outside and behave completely differently.
@rabnoor_sย It was thread size, not freshness. I commented same day as everyone else, no head start. The thread climbed to 781 points and 135 comments over the next week and my view count rode that whole climb, not a burst right after I posted.
Worth separating two numbers here. Views on a comment are mostly a property of the thread, not of the comment. You inherited 221 in one place and 9 in another because the thread already had that traffic either way. So optimising thread pick is really optimising a number that was never yours to move.
The number that is yours is the one only your comment can cause. Replies addressed to you, profile clicks, follows. You said yourself you only tracked views.
I do a lot of commenting in community groups off PH and the rule that has held up is post age at the moment you write, not thread size. Under roughly 24 hours old, people are still actively reading and you get replies. Past a week you get views and silence.
Cheap test on the data you already have: go back to the 221 thread and count how many replies were addressed to you rather than to the OP. If it is zero, that was the worst of the four, not the best.
@oshylabsย Checked. Zero replies addressed to me in the 221 thread, the whole time I tracked it. Your test called it before I ran it.
@abdullah_javaid3ย That is the useful result even though it reads like a negative one. 221 views with zero replies to you means that thread gave you reach and nothing else. The 9 view thread was not worse, it was the same outcome with an honest number attached.
For the next four I would track replies addressed to you, profile clicks and follows in the 48 hours after each comment. Views go in a separate column and get ignored when you decide where to post next.
If none of the four produce a reply, the problem has moved from thread pick to what the comment asks for. A comment ending on a specific question aimed at one named person gets answered. One ending on a general observation gets read and scrolled past. Worth auditing your own four on that alone.
@oshylabsย Checked that too. Two of the four ended on a direct question to the OP, two ended on an observation. All four still got zero replies regardless. So the ending wasn't it, at least not for these four.
Views might be the wrong counter entirely. We tracked what four comments actually produced in late July, and the number that moved was not the one I expected.
All four went into launch-day threads for products in that day's top 30. Busy pages. Every founder wrote back or upvoted the comment. Direct product votes out of it: zero.
One of the four turned into something better. The biggest thread of the set, a launch that finished #2 that day. By the end of that exchange the makers had put the gap we flagged on their roadmap. More value than the other three combined. And it came out of the most crowded thread of the four.
Then there is the part nobody told me. Two of those pages now show up when you search our brand name. A comment is a page in Google's index long after the views stop moving. Your 9-view thread and your 221-view thread may age very differently on that axis.
For context, I run sourcing checks from Yiwu, so PH threads are not where my buyers sit anyway. Which forces exactly the discipline you describe, researching the thread before writing a word.
@supplymoย The indexing point is the one I hadn't considered at all, I've only ever thought about PH as a live traffic channel, never as a page that keeps working in search months later. Is it the comment text itself showing up when you search your brand name, or the whole thread ranking with your comment just being on the page? That changes whether the comment needs the brand name in it to get that benefit, or whether just being present on a well indexed thread is enough.
@abdullah_javaid3ย The whole page ranks, not the comment text. I went back and checked before answering: neither of the two indexed comments contains the brand name anywhere in the body. They were plain product questions.
The likely reason it still matches is embarrassing in its simplicity. My username is literally the brand name, so every page my comment sits on carries it in the markup, profile link included, without me typing it once.
Which is convenient, because typing your own brand into a comment is exactly the thing that reads as spam.
One caveat, this is a site: search observation, so I can see which pages are in the index but not how Google weighs what's on them.
@supplymoย That's a much simpler explanation than I expected, so it's about the account being visible on the page and not the comment content at all. Curious if that means a thread you commented on once keeps working for you in search a year later, or if the ranking fades the older the page gets.
my main rule is one signal: is the person who asked replying to people, and not only to the good comments.
an op who answers the boring replies too is reading everything, which means yours gets read. an op who only answers the flattering ones is collecting, and the thread is a wall.
second check is whether the existing replies talk to each other or all point at the op. when every comment is aimed at the op and nobody answers anybody, it is being farmed, and a real answer sinks under the one liners however good it is. i skip those now.
age matters less than i expected. a six hour thread with three real replies beats an hour old one with twenty.
one thing worth separating, because it took me a while: this predicts whether you get read, not whether you get upvoted. the comment that started my longest exchange with a maker sits on zero, and a throwaway line elsewhere picked up points. worth knowing which of the two you are optimising for before you pick the thread.
@jernej_jan_kocicaย The read versus upvoted split is the one I hadn't separated out. I've been treating engagement as one signal, and a maker replying versus a crowd upvoting are clearly optimizing for different things. Which one are you writing for by default, and does that change depending on whether you're trying to reach the OP specifically versus just get read by whoever's in the thread?
@abdullah_javaid3ย the op, by default, and it is not close.
an upvote is anonymous and then it is over. a reply is a person who is still there and can be answered again. in a few weeks of doing this the only thing that came out of it that i can actually point at is one email from a maker, and that came from a thread where the op was answering people within minutes. the comments that collected more points and no reply produced nothing i can name.
and it does change what i write, more than i expected. the tell is whether the comment still makes sense to somebody who did not read your post. if it does, i wrote it for the room. if it is half unreadable without your post sitting above it, i wrote it for you. i do not think one comment can be both, you just end up general enough to be safe and then it lands nowhere in particular.
the room version is the one that collects upvotes, because agreeing with a clean general statement costs nothing. the op version gets answered because it is aimed at one specific thing you said, and it is also the one that reads badly to everyone else scrolling past.
so which would you rather have on your own thread, ten upvotes or one person who keeps replying?
@jernej_jan_kocicaย One person who keeps replying, easily, and I'm watching it happen in real time. The new thread I posted today got an upvote from a stranger within minutes and nothing since. This one is sitting at 40 comments because people keep coming back with something new to say. The upvote told me the idea landed somewhere. This thread is the only one that's actually taught me anything.
@abdullah_javaid3ย the upvote within minutes and then nothing is the cleanest version of the split we were just talking about. somebody read it, agreed, and had nothing to add. that is what agreement looks like from the outside, and it is not a bad signal, it just means the idea arrived finished.
which is awkward for anyone trying to write a good opening post. the tighter you make the argument, the less there is left to answer. this thread started as a number and a shrug, you did not know why the spread happened, and that is probably why people keep walking in with a theory. the new one already has the theory in it, so the only thing left to do with it is agree.
did the 221 one start scrappier than the new one, or am i pattern matching after the fact?