ATRIUMsearch → argument graph
Article · 2026-08-10 · 6 moments

How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies

What does it take for a social media platform to stop rewarding clickbait content? ✦ AI generated

01
Claim

Engagement bait is not a moderation problem but a structural one: ranking and retrieval systems optimized on engagement as a proxy for relevance will surface whatever maximizes interaction counts, and such bait can only be durably fixed by changing what retrieval measures—moving from behavior to meaning.

Clickbait isn't a moderation problem that classification can solve; it lives in the retrieval stage that decides what enters a feed. Because retrieval must score hundreds of millions of candidates in milliseconds, platforms rely on engagement as a cheap proxy that is easy to manufacture and optimize directly—so bait gets promoted—and demotions after ranking treat the symptom without fixing the underlying disease.

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): At first glance, this question might sound like a moderation problem that you can simply solve by enforcing better content policies and classifying posts that are engagement bait. However, the problem is much deeper. It often sits inside the component that decides which posts become part of a user's feed in the first place... However, the problem is that this type of engagement is also easy to manufacture. For example, a post that opens with "comment DONE if you're a real engineer" collects clicks and replies while delivering little value. But a ranking function tuned to reward interaction will promote it even though it is clearly an engagement bait. For years, the countermeasures against this were heuristics and demotions applied after ranking, but such an approach hasn't eliminated the problem. Accounts producing bait always find ways around such measures... A more durable fix changes what retrieval measures in the first place, and this happens by moving from behavior to meaning.

02
Example

LinkedIn consolidated five separate retrieval systems into a single fine-tuned LLaMA-3 language-model dual encoder that serves the entire feed through nearest-neighbor search at sub-50-millisecond latency, and its key insight is that feature representation—not the model—is where the real effort lies.

LinkedIn replaced five independently optimized retrieval systems with a single dual encoder built on a fine-tuned LLaMA-3, converting members and posts into one shared embedding space via a prompt library that turns structured features into text. The general lesson: feeding raw popularity counts as integers had almost no correlation with relevance scores, while converting counts into ranked percentages raised correlation sharply and improved retrieval accuracy by roughly fifteen percent.

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): In March 2026, LinkedIn replaced those systems with a single retrieval model built on a fine-tuned version of Meta's LLaMA-3. The model acts as a dual encoder, converting both members and posts into one shared embedding space. It serves the entire feed through nearest-neighbor search at sub-50-millisecond latency... A language model processes text, while a recommendation system runs on structured features such as view counts, engagement rates, work history, and post metadata. LinkedIn bridged this with a prompt library that converts structured fields into templated text sequences the model can process... When the team fed raw popularity counts directly into the prompts, the numbers had almost no correlation with the model's relevance scores, because large integers entered the model as arbitrary tokens. Converting each count into a ranked bucket, expressed as a percentage that the model could process in context, raised the correlation sharply and improved retrieval accuracy by roughly fifteen percent. The takeaway from this is that the model is often the part that works, and the surrounding representation of the data is where the real effort goes.

extends · 1gives example · 1

03
Example

Meta went in the opposite direction to LinkedIn: it keeps an ecosystem of more than a thousand specialized models arranged as a multi-stage retrieval funnel, ending in a multi-objective value model that extends the objective past raw engagement to avoid-content signals.

Meta arranges Instagram's recommendation system as a funnel of over a thousand specialized models across four stages (retrieval, early-stage two-tower ranking, heavy late-stage ranking, and a final diversity/integrity pass). Its value model extends beyond raw engagement to weight saves positively and subtract signals like 'See Fewer Posts Like This,' because many competing objectives are easier to tune and audit as separate stages.

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): Meta arranges Instagram's recommendation system as a multi-stage funnel, consisting of an ecosystem of more than a thousand models supporting it. Candidates pass through a sequence of stages, and each stage applies a more expensive model to a smaller set of surviving candidates... In Meta's approach, the late-stage model predicts many possible user actions at once, and a value model combines those predictions into a single score. That combination adds weight for positive actions, such as a likely save, and subtracts weight for predicted negative actions, such as a "See Fewer Posts Like This" tap. The basic objective of this extends past raw engagement to include signals about content a user would prefer to avoid... Many competing objectives, including engagement, diversity, integrity, and creator fairness, are easier to tune and audit as separate stages than as one model. Of course, the cost to this is operational complexity, which is the exact complexity LinkedIn set out to reduce.

extends · 1gives example · 1

04
Mechanism

Semantic retrieval using embeddings solves the proxy problem: dual-encoder models embed users and posts into a shared space so that related meanings—not surface keywords—position items nearby, and retrieval becomes a fast nearest-neighbor search over a precomputed index.

The alternative to behavioral retrieval is semantic retrieval powered by embeddings, which place related items near one another in a high-dimensional space even without shared keywords. A dual-encoder design converts users and posts into points in the same space, letting platforms precompute post embeddings and run fast nearest-neighbor searches at request time.

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): An embedding is a list of numbers that positions an item as a point in a high-dimensional space, arranged so that related items land near one another. For example, a post about fixing a leaking tap and a post about reducing water waste sit close together even when they share no keywords, because their meanings are related... One encoder converts a user, along with their profile and recent activity, into a point in the space. A second encoder converts each post into a point in the same space. Since the two encoders operate independently, a platform can compute every post embedding in advance and store it in an index. At request time, it computes the user embedding and runs a nearest-neighbor search to find the closest posts, which keeps retrieval fast across an enormous corpus.

explains mechanism · 1

05
Claim

The real reason the three companies converged on semantic retrieval but diverged in implementation is data structure: a text-rich professional network, a multi-objective media platform, and a video service with an enormous item corpus each favor a different retrieval design.

All three designs converge on the same payoff—semantic retrieval reduces engagement bait as a property of the architecture—but each incurs distinct tradeoffs (consolidation vs. specialization, compute cost, and generative failure modes). The differences come down to data: a text-rich network, a multi-objective media platform, and a huge video corpus each favor a different design, and none of the approaches is a pure type or fully removes bait.

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): Semantic retrieval reduces the leverage of bait rather than removing it, since a system can still be gamed by content engineered to match high-value topics. Also, these three designs are points of emphasis on shared scaffolding more than pure types... The reason these choices differ comes down to data. A text-rich professional network, a multi-objective media platform, and a video service with an enormous item corpus each favor a different design, and each team optimized for the structure of their specific data.

explains mechanism · 2

06
Example

YouTube removed the search index entirely with PLUM, which assigns videos semantic IDs and treats retrieval as a generation task: an adapted Gemini-family language model produces the codes of the next videos a user is likely to watch, gaining much wider long-tail coverage while risking generated identifiers that map to no video.

YouTube's PLUM removes the retrieval index: it gives every video a Semantic ID derived from its content, adapts a Gemini-family language model by adding these IDs to its vocabulary, and performs retrieval as a generation task producing the Semantic IDs of likely next videos via beam search. The payoff is far wider long-tail coverage and a 4.96 percent click-through lift on Shorts, at the cost of generating identifiers that map to no video (kept under five percent).

transcript

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies): The system, called PLUM, assigns every video a Semantic ID, a short sequence of discrete codes derived from the video's own content. Videos with similar content receive similar codes, so the identifier carries information about the item rather than acting as a random label. PLUM then adapts a pretrained language model (from the Gemini family) by adding these Semantic IDs to its vocabulary and continuing to train it on video metadata and user activity. After this adaptation, the model performs retrieval as a generation task. Given a user's recent history, it produces the Semantic IDs of the videos that the user is likely to watch next... This approach, however, introduces a failure mode that the index-based designs avoid, which is generating an identifier that maps to no video, and PLUM reports keeping that rate below five percent after fine-tuning. Measured against the previous production system, PLUM surfaced a far wider range of long-tail videos, and on YouTube Shorts, it raised panel click-through by 4.96 percent.

extends · 1gives example · 1

Highlight slides
Clickbait is a retrieval problem, not a moderation problem✦ from: Engagement bait is not a moderation problem but a structural one: ranking and retrieval systems optimized on engagement as a proxy for relevance will surface whatever maximizes interaction counts, and such bait can only be durably fixed by changing what retrieval measures—moving from behavior to meaning.Semantic retrieval embeds users & posts into shared space✦ from: Semantic retrieval using embeddings solves the proxy problem: dual-encoder models embed users and posts into a shared space so that related meanings—not surface keywords—position items nearby, and retrieval becomes a fast nearest-neighbor search over a precomputed index.Data structure drives retrieval divergence✦ from: The real reason the three companies converged on semantic retrieval but diverged in implementation is data structure: a text-rich professional network, a multi-objective media platform, and a video service with an enormous item corpus each favor a different retrieval design.Durable fix: measure meaning, not behavior✦ from: Engagement bait is not a moderation problem but a structural one: ranking and retrieval systems optimized on engagement as a proxy for relevance will surface whatever maximizes interaction counts, and such bait can only be durably fixed by changing what retrieval measures—moving from behavior to meaning.Converged payoff, divergent tradeoffs✦ from: The real reason the three companies converged on semantic retrieval but diverged in implementation is data structure: a text-rich professional network, a multi-objective media platform, and a video service with an enormous item corpus each favor a different retrieval design.
Related episodes