Twitter Shadowban Test: Check X Visibility in 5 Steps
·9 min read
A Twitter shadowban test can flag a possible visibility problem, but it cannot prove why X ranked, filtered, or limited a post. Run the free third-party check first, then use the 5 manual steps below to verify the result.
Yuzurisa checks public visibility signals. Donivo does not operate the checker, and the result is not official X enforcement data.
What the checker tests
The checker uses its own labels for several kinds of public visibility. These are useful diagnostic categories, not official names for X enforcement actions.
Checks whether the username appears when someone begins typing it in search.
Checks whether public posts can be found through a direct X search.
Looks for replies that may be missing when another person opens the conversation.
Looks for replies that appear behind an additional notice or lower in a conversation.
How to interpret the result
A failed check means the tool could not find an expected public signal. It does not automatically mean that X applied a hidden account penalty. A protected account, deleted post, narrow query, search delay, conversation setting, block, or technical failure can produce a similar result.
X explains that different search surfaces use different signals. Its search recommendation overview distinguishes ranked results from chronological results, so appearing on a profile does not guarantee placement in every search view.
Verify X visibility manually in 5 steps
Repeat the same narrow checks instead of trying many unrelated searches. Consistent observations are more useful than a large collection of one-off results.
- 1
Confirm the account is public
Protected accounts and audience-limited posts will not behave like fully public content. Check the visibility setting before testing search.
- 2
Search while logged out
Use a private window to search the exact username and a distinctive phrase from a recent public post.
- 3
Open the reply as a second viewer
Ask another person to open the original conversation and look for the reply without using your account.
- 4
Check account notices
A verification prompt or temporary limitation gives you more useful information than a generic shadowban label.
- 5
Wait and retest once
Search indexes and conversation views can change. Record what you checked, pause risky activity, and repeat the same test later.
If your account is protected, follow the steps for making an X account public before running a search-based test.
Check account notices before guessing
If X shows a verification request, account warning, or temporary limit, follow that notice first. The official locked and limited account guidance explains that some limits can affect search results and notifications while X asks the account owner to complete a step.
Scheduling is different from bot-style automation
Scheduling a post you intentionally prepared through a supported account connection is different from scripting the X website, sending unsolicited replies, manipulating engagement, or publishing duplicative content at scale. X’s automation rules make the account owner responsible for actions taken by connected applications.
- Avoid identical or near-identical posts across several accounts.
- Do not automate aggressive follows, likes, reposts, mentions, or replies.
- Review links, media, claims, and timing before scheduling a batch.
- Remove or pause scheduled posts when the source information changes.
- Review the current X Rules when you are unsure whether a behavior is allowed.
Build a safer X publishing routine
Keep the content deliberate with the social media scheduling guide, check the layout with the social post preview, and follow the platform-specific steps for scheduling posts on X.
When to contact X support
Contact support when you have a specific account notice, access problem, or restriction you believe is an error. Keep the checker result, logged-out observations, dates, and exact error messages as context. A third-party result cannot appeal an enforcement decision for you.