A sudden drop in non-follower reach cannot be confirmed by an outside checker alone. Use BanScope to verify public visibility, then compare Threads Insights to distinguish a visibility problem from recommendation/ranking changes.
A sudden drop in non-follower reach cannot be confirmed by an outside checker alone. Use BanScope to verify public visibility, then compare Threads Insights to distinguish a visibility problem from recommendation/ranking changes.
Last reviewed: 2026-09-22A profile or post can remain publicly accessible while receiving less recommendation distribution. Meta publishes Recommendation Guidelines explaining that some allowed content may still be ineligible for recommendation.
BanScope checks whether the Threads profile resolves publicly, whether public post signals are present on the profile, and whether the username appears in an accessible public search response. It does not read internal recommendation eligibility or non-follower distribution volume.
See the BanScope methodology →Recommendation eligibility is an internal platform decision. BanScope does not claim to tell you that a Threads account is definitively “not recommended”; it verifies the public surfaces an outside viewer can observe.
Use only a public username. No login or password required.
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 →
