How to Check an X (Twitter) Shadowban or Visibility Restriction

Bottom line: Don't judge based on a single search result

There is no single condition generally called a shadowban. Distinguish reach restrictions officially described by X, search and reply ranking, sensitive-content settings, private settings, blocks and mutes, and account restrictions accompanied by official notices, and record only verifiable public states.

Items to check first

• Check whether X has issued a restriction, lock, or identity verification notice
• Check whether the account is public and the target post has not been deleted
• Whether you checked not only "Top" but also "Latest" and from: searches
• Whether profiles, replies, and direct post links were checked outside the account owner's environment

Isolate the reason why it is not displayed

The phenomenon of "not appearing in search" and "reply not found" is caused by a mix of public settings, viewer settings, search/reply ranking, handling of individual posts, official restrictions on accounts, and temporary problems on the X side. Check the following table from above.

Organize conditions commonly called shadowbans

Terms such as "Search Ban" and "Reply Deboosting" are informal names used by third-party services or users and may not match X's current official, fixed diagnostic categories. This article rephrases them as observable behavior, such as not appearing in search results, replies being collapsed, or not being eligible for recommendations.

Check possible display restrictions

X explains that it may limit the reach of content within search, recommendations, and conversations due to rule violations or quality/safety decisions. On the other hand, since the appearance changes depending on the search ranking and settings for each viewer, it is not possible to determine the internal state just because the page is not displayed once.

• Can the direct link to the profile be opened even in an environment other than the user?
• Can I check account candidates through user search?
• from: Can you check public posts by searching for "latest" username?
• Is it possible to check the target content by searching for replies or linking directly to the post?
• Do the results repeatedly vary depending on the person, another account, and the logged-out state?

It is not possible to directly obtain X internal account evaluations, ranking scores, and restriction reasons from third parties. Please record the disclosure status (seen/not visible/unable to confirm), including the date and time and confirmation environment.

What you can and cannot check with the X display restriction check tool

If a search error or usage limit is displayed on the X side, it will be recorded as "unable to confirm" instead of "not visible." Compare whether the same difference remains even after rechecking after a while.

If a problem is found/not found

If it continues to be hidden in multiple environments

• Check X notifications and email, then complete any officially requested identity verification or appeal
• Review search, publishing, and sensitive settings, and record changes and times
• Stop mass posting identical content or large numbers of unrelated replies, and return to normal use in accordance with the X Rules.

If no difference is found in publication status

• Evaluate changes in impressions and recommendation visibility separately from restrictions on public status
• Allow for temporary search failures and recheck later without changing conditions
• For only the individual problematic posts, check the content, visibility, and reply target.

We do not use unfounded methods that require a fixed number of operations or a fixed number of days of waiting to be released. If there is a restriction notification from X, the notification and official help instructions will take precedence.

X official information used for confirmation

Search and display specifications are subject to change. This article uses the X Help Center and X Rules as of the time of writing to explain the official terminology and the condition commonly referred to as "Shadow Ban."

Example: compare the display state of @devtools_test

Consider a fictional public account, @devtools_test, whose profile opens but whose latest posts do not appear in search results. Prepare a unique phrase and the post URL, then separate search results from direct display.

Open the same link as the account owner, another account, and while logged out. In environments that show an X error or search-usage limit, record “could not verify” rather than treating it as not displayed.

1. Enter a username or profile URL
2. Enter a unique phrase and post URL as needed
3. Open the generated verification link in the same order across three environments
4. Choose visible, not visible, or could not verify
5. Record the check date, time, and conditions, and compare them with later results

This procedure does not retrieve X's internal evaluations. It is intended to check whether the same difference persists across multiple public states.

Frequently asked questions

Can this tool alone confirm a shadow ban?

No. It does not access X's internal evaluations; it organizes how profiles, searches, replies, and posts appear as checked by the user on X.

Are reduced impressions a display restriction?

You cannot determine that from lower impressions alone. Post content, time of day, engagement, and personalization of recommendations can also affect them, so separately investigate verifiable visibility status.

Do I need to enter a password or Cookie?

No. Do not enter your X password, Cookie, access token, or API key into DevelopTools.