Does getting a Community Note hurt my post's reach?
The two systems are separate, and the Community Notes code itself doesn't set your post's ranking — it decides whether a note shows. But X has publicly stated that posts with a Currently Rated Helpful note get reduced reach and that authors become ineligible for revenue sharing on them, and a visible "readers added context" label changes how people engage regardless. So the note doesn't reach into the ranking scorer directly in the open code; the reach impact comes through stated platform policy and the engagement effects of the label. The honest split: the CN repo scores notes, not your reach — the reach consequence is policy layered on top.
"A note killed my reach" is a common claim, and the truth needs the same care as the link myth: separating what the code does from what platform policy does. Here both are real, but they're different sources of effect.
The Community Notes code scores notes, not your reach
The communitynotes scoring algorithm decides one thing: whether a note reaches
Currently Rated Helpful status and shows on the post. It computes note intercepts and statuses — it
does not contain your post's ranking score or reach. Nothing in that repo down-ranks your post; that
isn't its job.
A Community Note becomes Currently Rated Helpful (and shows publicly) when its learned note intercept clears the CRH threshold, which defaults to 0.40 in the open scoring code.
The reach impact comes from stated policy
Separately, X has publicly stated that once a post carries a Currently Rated Helpful note, its
reach is reduced and the author loses revenue-sharing eligibility on that post. This is platform
policy, communicated by X — not a line we can show you in the open ranking scorer. We label it as
what it is: an official stated effect, distinct from code we can point to.
X has publicly stated that posts with a Currently Rated Helpful note receive reduced reach and that authors lose revenue-sharing eligibility on those posts. This is stated platform policy, not a mechanism present in the open Community Notes scoring code.
And the label changes engagement on its own
Even setting policy aside, a visible "Readers added context" label changes behavior: some people disengage, some reply about the note, some don't share. Those are real shifts in the engagement signals that do feed ranking — so a noted post can lose reach through ordinary engagement effects, no special penalty required.
Signal by signal
| mechanism | source | strength |
|---|---|---|
| Note reaches Helpful status | communitynotes code (intercept ≥ 0.40) | code-current |
| Reduced reach + no revenue share on noted posts | X public policy statements | officially stated |
| Engagement shifts from the visible label | ordinary ranking signals | inferred from the formula |
What the code doesn't say
The magnitude of the reach reduction. X states that noted posts get less reach, but no published
code quantifies it, and the CN repo doesn't contain it. We can confirm the note-status mechanism and
cite X's stated policy; we can't show you a number for how much reach a note costs.
X has publicly stated that posts with a Currently Rated Helpful note receive reduced reach and that authors lose revenue-sharing eligibility on those posts. This is stated platform policy, not a mechanism present in the open Community Notes scoring code.
What to do with this
The durable lesson isn't "avoid notes by gaming them" — it's that accurate posts don't attract Helpful notes in the first place, because a note only reaches Helpful status when people across viewpoints agree it adds needed context. Write things that wouldn't need correcting. xDoctor's CN tools help you see the note landscape around accounts factually, without trying to defeat the system.