Vote fuzzing vs shadowban vs automod filter: a diagnostic decision tree
Your new Reddit post shows 1 upvote and 50% upvote rate. Three different systems can produce that screen. Here is the operator decision tree.
Your post is 12 minutes old, shows 1 upvote, sits at 50% upvote rate, and the comment count is zero. That single screen can mean four completely different things, and the move to make next is different for each. This is the diagnostic decision tree (vote fuzzing, automod filter, crowd control, or shadowban) with the detection step for each branch.
What does "1 upvote and 50%" actually mean on a brand-new Reddit post?
Reddit displays 1 upvote on every new submission because the OP's auto-upvote is the only confirmed vote and the score hides under fuzzing for the first window. Per the Reddit Help score-hiding reference, votes are intentionally not shown for the first hour or so to prevent bandwagoning. The 50% upvote rate is the fuzzed default, not a 50/50 split.
The practical implication: do not diagnose anything from the score for the first 30–60 minutes. Diagnose visibility. If the post is visible to logged-out users in the subreddit's /new feed during that window, the score will sort itself out as upvotes accumulate. If the post is not visible to logged-out users at minute 12, the score will never move because no one outside the author sees it.
How does vote fuzzing work and what does it look like?
Vote fuzzing is the cosmetic noise Reddit injects into displayed up and down counts. Per the REDAccs ranking writeup, the displayed score wobbles by a small amount on refresh, but the actual ranking math (log10(max(|s|, 1)) + seconds / 45000, documented in Amir Salihefendic's algorithm breakdown) still runs against the true score.
What it looks like: refresh the post three times in 10 seconds and watch the upvote count tick between, for example, 7, 6, 8. Both sides are fuzzed in parallel, which is why the upvote rate sticks near 50% on low-engagement posts. The fuzzing is not what is killing the post. It is the default behavior for every submission ever made. Reading vote fuzzing as a problem is the most common false positive in our Reddit algorithm decode, and it is why operators panic at minute three and resubmit a post that was on track.
How do you tell if automod or crowd control filtered your post?
Open https://reddit.com/r/\<sub>/new in a logged-out browser tab. If your post is not in that feed, a subreddit-level filter caught it. Automod and crowd control are the two candidates. Per Reddit's AutoModerator reference, automod runs YAML rules against post content and either removes (gone, usually with a public comment) or filters (sent to modqueue, silent). Per the crowd control help article, crowd control filters based on the author's relationship to the sub (non-subscriber, low in-sub karma, low Contributor Quality Score).
The fast confirmation step is the .json endpoint. Append .json to the post URL while logged out and read the removed_by_category field on the post object. Common values: automod_filtered (held in modqueue), automod_removed (gone), moderator (a human pulled it), null (visible). Reveddit and its open-source code automate that same lookup and flag the removal type for you. If the .json shows null but the post still does not appear in logged-out /new, crowd control is the most likely answer; the operator-side decode lives in our crowd control detect-and-pass guide.
How do you confirm or rule out a site-wide shadowban?
Shadowbans are sitewide and rare. The fastest confirmation is the logged-out profile test. Open https://www.reddit.com/user/\<your-username>/ in a private window. If you get "page not found" or "this account has been suspended," you are either shadowbanned or sitewide-suspended, and every post you make is invisible to every other user across every sub. Per the Reddifier 2026 shadowban guide and Multilogin's 2026 detection writeup, this is the cleanest single test; the r/ShadowBan bot is the second-best confirmation.
The pattern that distinguishes a shadowban from a subreddit-level filter: shadowbans break every post, not just one. If your last five posts across three different subs all show 1 upvote and zero replies, run the shadowban test. If only the most recent post in r/SaaS is dead, the issue is the sub's filter stack, not the account. The full recovery protocol once a shadowban is confirmed lives in our shadowban detection guide and the day-by-day recovery playbook.
The decision tree, end to end
If you see the post normally, visibility is fine and the score will settle. If you get a 404 or "removed," skip to Step 3.
Post present: visibility intact, fuzzing is cosmetic, wait or work the comments. Post missing: subreddit filter caught it (automod or crowd control).
Read removed_by_category. automod_* means automod; null with the post missing from logged-out feeds means crowd control; moderator means a human.
404 or suspended page = sitewide shadowban or suspension. Account works normally = the issue is per-subreddit, not your account.
Run the four steps in order; do not skip ahead. The most common operator mistake is assuming a shadowban when the post is actually fine and the score is fuzzing through its first 30 minutes. The second most common is assuming automod when the real filter is crowd control, which produces no modmail and no removal reason. The third is missing the difference between automod_filtered (will surface to the modqueue and may be approved within hours) and automod_removed (gone, modmail required to revive). Two of the four outcomes need patience; one needs a rule fix; one needs an account-level appeal. Same screen, four different next moves.
When the diagnosis says "the post is fine, the score is just fuzzing"
This is the most useful and least satisfying outcome. Visibility is intact, the algorithm is running, and the post is competing on velocity against everything else hitting /new in that window. Per the ITGeared writeup on score hiding, the fuzz and the hidden score together exist precisely so early voters cannot read momentum off the screen and pile on or bail. The way to move the score is to feed the velocity layer of the hot algorithm: a strong first comment in the first 5 minutes, a 60–80 character title hook, and a posting time when the sub's active count is rising rather than falling.
If the velocity does not show up (verified visible, verified not shadowbanned, verified not filtered, and still flat at 30 minutes), the post lost to the queue. That is a craft problem, not a systems problem. Audit the title, the first comment, the hook, and the sub-fit. The drip vs blast upvote-timing decision applies once velocity is the bottleneck; the ROI measurement playbook covers how to read whether a paid push paid back.
Frequently asked questions
Why does my new Reddit post show 1 upvote and 50%?
That is Reddit's default new-post display. Per the Reddit Help score-hiding article, votes are intentionally hidden and fuzzed for the first 30–60 minutes to prevent bandwagoning. It is not a sign of a shadowban or a filter; it is the floor every post starts at.
Does vote fuzzing affect my ranking?
No. Fuzzing scrambles the displayed upvote and downvote counts, but the true score still drives the hot algorithm. A post with a true score of 150 outranks one with a true score of 100 regardless of what the fuzzed numbers show on screen.
How do I tell automod removal from crowd control?
Append .json to the post URL while logged out and read removed_by_category. automod_filtered or automod_removed means automod. If the field is null but the post is missing from the logged-out /new feed, crowd control is the most likely filter. Crowd control rarely surfaces in removed_by_category; it manifests as silent absence.
How do I know if I am shadowbanned, not just filtered?
Open your profile in a logged-out private browser at https://www.reddit.com/user/\<your-username>/. A 404 or suspension page means sitewide shadowban. If the profile loads normally and only one post is invisible, you are not shadowbanned; the issue is at the subreddit level.
Can I appeal a vote-fuzzed score?
There is nothing to appeal. The fuzz is cosmetic. The actual score and ranking are unchanged. Resubmitting a post because the fuzzed display looked bad usually trips automod's repost rules and burns the account's standing in the sub for no gain.
How long should I wait before assuming the post is dead?
Run the diagnostic at minute 15 and again at minute 45. If visibility is intact and the post has zero net upvotes from non-author voters after 45 minutes in a sub that is currently active, the post lost the velocity race. The first-hour upvote velocity playbook is the next read.
:::
