A post can be relevant to a reader and still be excluded from a feed. That is not necessarily a contradiction: ranking and visibility checks answer different questions.
Ranking estimates how candidates compare for a particular reader. A filter decides whether a candidate should remain in the pool under a specified condition. The distinction matters when reading claims that a high score must translate into an impression.
Before a score can matter
In the reviewed For You post pipeline, a list of filters appears before the scorers. It includes duplicate removal, previously seen posts and the viewer’s muted keywords. These are examples from the published route, not a complete account of every surface on X.
The same file then lists scoring components and a top-scoring selector. In other words, a candidate can leave the pool before the code reaches the scoring stage. A prediction cannot rank a post that is no longer a candidate in that path.
A check after selection
The pipeline also lists a visibility hydrator after selection and a visibility filter among the subsequent filters. The filter keeps Allow, Interstitial, Avoid and Downrank actions, while removing Drop, Tombstone and NotEvaluated actions. Interstitial is a treatment, so “kept by this filter” should not be read as “displayed without any notice or restriction.”
The visibility request distinguishes in-network candidates from out-of-network candidates and uses different safety levels for them. The published rule lists differ. That is a code-level distinction; it does not establish the verdict a particular post received or every rule active on the live service.
How to use the distinction
When a post reaches fewer people than expected, a like count alone cannot identify the cause. The post may not have entered a candidate pool for some readers, may have ranked differently, or may have faced another check. These are possibilities, not a diagnosis of any individual account.
For an author, the useful habit is to separate three questions: could the post enter this route, how did it compare with other candidates, and did later checks change what remained? Each question needs its own evidence. The public code describes mechanisms; it does not provide a post-by-post explanation of the live feed.
Scope: the public code snapshot reviewed November 3, 2026; the For You post route. Production settings and other surfaces may differ.
Primary sources: pipeline and stage order · visibility filter actions · safety-level selection · rule lists.
