Visible content and recommended content are different
Meta applies Recommendation Guidelines to content shown to people who do not already follow an account. Content can remain on the platform while receiving less recommendation distribution.
Threads Not Recommended: What Can You Actually Check?
Third-party websites cannot directly read Meta’s recommendation-eligibility decision. The useful diagnostic is to separate public visibility from recommendation performance using BanScope, Insights and Meta’s recommendation rules.
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.
THREADS NOT RECOMMENDED
Threads Not Recommended: What Can You Actually Check?
Third-party websites cannot directly read Meta’s recommendation-eligibility decision. The useful diagnostic is to separate public visibility from recommendation performance using BanScope, Insights and Meta’s recommendation rules.
Last reviewed: 2026-09-22What BanScope checks first
BanScope verifies that the public profile resolves, that public post signals are visible, and that the username can be found in an accessible public search response. If these pass, it helps narrow the problem away from basic public availability and toward recommendation/ranking performance.
See the BanScope methodology →Diagnostic order
- Check public profile/post/search visibility in BanScope.
- Compare non-follower discovery and reach in Threads Insights.
- Review the Recommendation Guidelines against recent content.
- Check any account-status or policy notice available in the app.
- Compare multiple posts to separate a single-post issue from an account-wide pattern.
Why recommendations may fall
- Content that is not eligible under recommendation rules.
- Normal ranking and interest changes.
- Low relevance/response for a specific post.
- A separate public visibility problem.
What to review
- Follow official policy notices if shown.
- Return to original, context-relevant posting rather than repetitive recommendation-bait.
- Compare Insights over several days.
- If search visibility is also down, diagnose that separately.
Manual check
- Review account status/policy notices in the Meta apps.
- Compare discovery sources and non-follower reach in Insights.
- View the target post from another account.
Why BanScope does not claim a direct verdict
Recommendation eligibility is not contained in the public profile HTML or search response used by BanScope. An outside tool should not turn a reach drop into a fake internal “Not Recommended” flag.
Diagnostic path: symptom → cause → verify → re-check
1. SymptomSeparate public visibility from reach loss2. CauseSeparate recommendation eligibility from ranking variation3. VerifySee what can and cannot be observed4. Re-checkRe-check profile, search and posts later
Check your account
Use only a public username. No login or password required.
Official references
BanScope does not turn a third-party guess into a verdict. These platform documents describe search, recommendation and public-visibility behavior relevant to the diagnostic.
See validation and update history for this methodology →