BanScope

What Causes an X Shadowban?

If your posts disappear from search, replies become hard to find, or reach drops suddenly, there may not be one single “shadowban” behind it. Use official X guidance and BanScope’s public visibility checks to separate likely causes.

No loginNo passwordPublic data onlyMulti-source / beta
No login · No password · Results in seconds
No password or login required. Usernames are not stored in server analytics. Recent check history can be kept only in this browser on this device.
What you get
100 Visibility score✓ Profile✓ Search✓ Posts✓ Replies
X and Threads do not publish an official shadowban flag. BanScope cross-checks profile, suggestions, search, posts and replies across multiple public sources.
X SHADOWBAN CAUSES

What Causes an X Shadowban?

If your posts disappear from search, replies become hard to find, or reach drops suddenly, there may not be one single “shadowban” behind it. Use official X guidance and BanScope’s public visibility checks to separate likely causes.

Last reviewed: 2026-09-22

Separate the symptom from the cause

“Shadowban” is not a public enforcement status that X exposes to third-party tools. People use the term for several different symptoms: missing search results, missing suggestions, replies that are difficult to find, or lower discovery. Similar symptoms can come from privacy settings, search-quality filters, indexing delays, spam controls, sensitive-content filters or restrictions on a specific conversation.

What BanScope can separate

BanScope checks public profile resolution, search suggestions, recent post IDs against search results, public post resolution, and reply IDs against reply/conversation search. A missing signal is not automatically labeled a ban; unavailable evidence is returned as a re-check condition.

See the BanScope methodology →

A practical diagnostic order

  1. Confirm that the profile and posts are public.
  2. Run the five BanScope visibility checks separately.
  3. Open X Latest search for from:username and compare recent normal posts.
  4. Review whether recent activity is dominated by repeated text, repeated links, aggressive automation or hashtag abuse.
  5. Re-check later to separate indexing delay from a persistent visibility change.

Common cause candidates

  • Protected posts or incomplete profile/search prerequisites.
  • Sensitive-content filtering, relevance, safety and search quality systems.
  • Repeated or near-duplicate posts and links.
  • Automated posting or reply patterns that may degrade search quality.
  • Indexing delays and limits affecting older content.
  • Conversation-specific settings, deleted parent posts or restrictions outside the account itself.

What to do next

  • Compare your setup with X Search Help and Search Rules.
  • Stop repetitive or mechanical posting patterns and return to normal use.
  • Use a simple normal post without link-heavy formatting for a search test.
  • For reply issues, test a real public reply URL rather than relying on a large thread list.
  • Do not assume a fixed recovery duration; compare dated visibility checks.

Manual check

  1. Open X while logged out or from another account.
  2. Use Latest search for from:username.
  3. Open the target post or reply URL directly and compare what an outside viewer can see.

What cannot be proven externally

BanScope and other external tools cannot read X’s internal moderation labels, search-quality score or a private reason code. Missing public signals are useful evidence, but they do not identify the internal cause by themselves.

See validation and update history for this methodology →