Reply deboosting describes a reply that still exists but is ranked low or hidden behind additional-reply controls. Existence and ranking are different signals, so BanScope verifies reply visibility automatically and leaves ranking itself to a manual check.
Reply deboosting describes a reply that still exists but is ranked low or hidden behind additional-reply controls. Existence and ranking are different signals, so BanScope verifies reply visibility automatically and leaves ranking itself to a manual check.
Last reviewed: 2026-09-22A “ghost” visibility problem concerns whether the reply can be found at all. Deboosting concerns where an existing reply is ranked in a conversation. A reply can be public and searchable but still be shown far below other replies.
BanScope verifies direct reply access and ID matching in reply/conversation search. It does not currently measure the exact ordinal position of a reply in X’s default thread ranking, so it does not automatically label a low-ranked reply as “deboosted.”
See the BanScope methodology →X does not expose the internal reason why one reply ranks below another. BanScope currently measures reply availability and searchability, not the ranking model itself.
Use only a public username. No login or password required.
BanScope does not turn a third-party guess into a verdict. These platform documents describe search, recommendation and public-visibility behavior relevant to the diagnostic.
See validation and update history for this methodology →
