Am I Shadowbanned on Twitter? Run This Visibility Check

Use one original post and one reply to separate a real visibility symptom from an ordinary drop in reach.

By CarryFeed8 min readPublished

Your own profile is the least useful place to check. It can prove that X stored a post; it cannot prove that another person can find that post in search or inside a conversation.

X now pilots an official Under the Hood report for a disclosed set of visibility labels. That report is useful first-party evidence, but it covers a completed prior month and focuses on For You labels. For a post missing from Search or a reply that is hard to find today, you still need a public surface-by-surface check.

The practical answer is not a red or green badge. It is a record of which sample you checked, where you checked it, who could see it, and whether the same result repeated.

Contents
  1. The 47-view post
  2. The ten-minute check
  3. How to read the result
  4. False positives
  5. The official tool update
  6. What to do next
  7. FAQ

A low-view post is a reason to investigate, not a diagnosis

Suppose an account that normally reaches a few thousand people publishes a post and sees 47 views. The author opens their profile. The post is there. They search while signed into the same account and find it again. The natural conclusion is either “nothing is wrong” or “I am definitely shadowbanned.” Neither conclusion follows.

X says content can remain available on an author's profile even when it is not eligible for recommendation. It also documents that Top and Latest search do different jobs. The diagnosis therefore has to separate storage, public access, search visibility, reply placement, and recommendation.

Run the same two samples through four observations

Choose one recent original post and one recent reply. Keep both direct URLs open. Do not switch samples midway through the check, because a missing post and a missing reply can point to different systems.

The four-observation protocol
  1. Establish the public baseline

    Open the account and the original post's direct URL in a logged-out window. If either is unavailable, resolve privacy, deletion, suspension, or an incorrect URL before testing discoverability.

  2. Use Latest, not Top

    Search from:yourhandle, switch to Latest, and look for the same original post. If needed, add a distinctive phrase from the post. Top measures ranking; Latest is the more useful discoverability surface.

  3. Check the reply where it lives

    Open the parent post from a logged-out window or another account. Look for the sampled reply in the conversation, then confirm that the reply's direct URL still opens.

  4. Repeat only the failed observation

    Record the query, viewer state, safe-search setting, URL, and time. Repeat the same failed check later instead of changing every variable at once.

X documents that Latest remains subject to global visibility filtering, while other search surfaces apply additional ranking. See Search Recommendations and How to use X search for the surface definitions behind this protocol.

Four result patterns lead to four different conclusions

A useful result names the surface that failed. It does not generalize one missing observation into an account-wide enforcement claim.

Profile opens · direct URL opens · Latest finds the post · reply is findable
No public visibility issue was detected in the samples. Stop retesting and investigate distribution, topic, audience fit, or the post itself.
Direct URL opens · the same post is missing from Latest twice
Possible search-visibility issue for that post. Preserve the URL and exact query; do not claim every post or surface is affected.
Latest finds the original post · reply opens only by direct URL
Possible reply-placement issue in that conversation. This is different from an account-wide search restriction.
Profile is protected or unavailable · direct URL does not open
Inconclusive. Privacy, deletion, suspension, a bad handle, or source availability must be resolved before visibility can be tested.

Remove the common false positives before escalating

X's search rules and restrictions describe several reasons an account or post may not appear in search. One empty result is not enough to distinguish enforcement from settings, ranking, or an unavailable source.

“My post is not in Top.”
Top is ranked for relevance and engagement. Use Latest for this discoverability check; otherwise you are measuring rank.
“My own account can see it.”
The author's signed-in view is not an independent observation. Use a logged-out window or a different account.
“Impressions fell, so I am banned.”
Impressions mix audience interest, timing, competition, follower activity, and recommendation. A fall can trigger this check, but it is not the result.
“One checker showed green.”
A third-party checker may observe only account access or one search endpoint. Even a clean Under the Hood report covers a defined label set and report period, not current Search ranking or reply placement.

X's Under the Hood report changes one part of the answer

On August 14, 2026, X announced an official pilot that reports a disclosed set of post and account labels that may limit For You visibility. This is stronger evidence than a third-party public checker can provide.

The published report-serving code shows a monthly, best-effort report gated by account age, posting activity, data readiness, and the pilot feature switch. A clean report rules out its supported labels for that period; it does not certify normal Search visibility, reply placement, or same-day reach.

Use the two approaches for different jobs: Under the Hood for first-party label evidence, and this field diagnosis for the public surface where the current symptom appears.

A label appears in Under the Hood
Record the report period, label name, and stated effect. Describe the exact restriction rather than calling every label an account-wide shadowban.
No supported label appears
Continue only if a concrete public symptom remains. Test that sample in Search or its conversation instead of repeatedly refreshing the report.
The report is unavailable
That may reflect pilot access or eligibility. It does not count as evidence for or against a visibility restriction.

Preserve the failed case or stop testing

X says content that is not eligible for recommendation may still remain available on the author's profile and to followers. Read its recommendation eligibility explanation when a direct URL works but distribution looks different.

All sampled surfaces are clear
The visibility check is done. Compare the topic, opening line, media, timing, and audience fit instead of looking for another checker.
One observation fails twice
Keep the post URL, query, time, viewer state, and a plain description of what was missing. Check X for an explicit notice and use the official appeal path if one is shown.
The result is inconclusive
Confirm the handle, public-account status, direct URL, safe-search setting, and whether the post still exists. An unavailable source cannot support a visibility conclusion.
Collect the public observations
Run CarryFeed's visibility checkCarryFeed checks the public profile, a recent-post sample, and Latest search separately, and reports unavailable observations as unknown.
Interpret an official label
Read the Under the Hood code guideUse this when X exposes a label or you need to understand the difference between ranking and visibility filtering.

“Shadowban” is a broad label for several different failures. Use the word as the start of a check; it is too broad to be the result.

A defensible answer names the sample, the surface, the observer, and the result. That is less dramatic than a red badge, but it tells you what to do next.

Frequently asked questions

Can a shadowban checker know for certain that my Twitter account is shadowbanned?

There is no single verdict that covers every form of reduced reach. X's Under the Hood pilot can report supported internal visibility labels for an eligible account and prior month; public checks can test direct access, Search discoverability, and reply placement.

Why can I see my post on my profile but not in search?

Profile availability and Search visibility are different surfaces. X documents global visibility filtering in Latest search and separate ranking for Top search.

Does low engagement mean I am shadowbanned?

No. Low engagement can justify checking visibility, but it does not prove a Search or reply restriction. Test the same recent post across public surfaces.

Should I use Top or Latest to check a post?

Use Latest. Top is ranked by relevance and engagement, so absence from Top is not evidence that the post is missing from public search.