LinkedIn's New Algorithm Actively Detects Engagement Pods

THE SHORT VERSION: LinkedIn’s 360Brew ranking system now actively detects engagement pods and neutralizes their reach, according to a July 23 Forbes breakdown of what the platform punishes in 2026. Founders trading likes and comments inside private growth groups, alongside anyone posting generic AI-written content or “comment YES if you agree” bait, are getting suppressed instead of boosted.

What happened

Forbes contributor Jodie Cook detailed the shift in a July 23, 2026 analysis, reporting that LinkedIn’s 360Brew ranking system is now built to detect engagement pods and render them “entirely ineffective,” cutting reach for every post caught in one. The same update flags generic AI-drafted posts, which readers now scroll past in under three seconds, and actively suppresses comment-bait phrasing such as “comment YES if you agree” or “repost this if it helped.” Outbound links still cost reach too, whether they sit inside the post or the first comment. Cook, who grew her own LinkedIn following to 57,000 by tracking each platform change, frames the shift as LinkedIn converting last year’s growth shortcuts into this year’s penalties. For B2B founders who built visibility on pods and templated AI posts, the tactics that used to work are now actively working against them.

Why LinkedIn actively detects engagement pods now

Engagement pods and AI-templated posting became common shortcuts for founders trying to build a LinkedIn presence fast, especially inside paid cohorts and mastermind groups built specifically to trade early comments. Those groups now work against the founders using them, since 360Brew appears trained to recognize coordinated engagement patterns and discount them instead of rewarding them. That matters for any founder-visibility strategy built on borrowed momentum instead of original material. The posts that still travel are the ones with specific, unrepeatable detail: a client who got fired, a number from a deal that fell apart, a price that got raised and why.

1. Leave your engagement pod or growth group this weekAny WhatsApp, Slack, or Discord group where members coordinate early likes and comments on each other’s LinkedIn posts is now a liability, not a growth hack. 360Brew is built to detect the coordinated pattern and suppress the post’s reach rather than boost it, so time spent inside the group is actively working against the visibility it was supposed to buy.
2. Cut comment-bait lines out of your next ten postsPhrases like “comment YES if you agree” or “repost this if it helped” now get actively suppressed instead of rewarded. Replace the ask with a real question or a stated opinion a reader has a specific reason to push back on. Earning the comment instead of prompting it reads to the algorithm as genuine engagement, not manipulation.
3. Move outbound links into a DM instead of the postPosts with links, even links sitting in the first comment, now reach roughly 60% fewer people under the current ranking system. Write the post to stand on its own, then send the link directly to anyone who comments asking for it. The post keeps its reach and the readers who wanted the link still get it.

By the numbers: Posts with outbound links reach about 60% fewer people, generic AI-drafted text gets scrolled past in under three seconds, and saves now generate roughly five times the reach of a single like — the signals 360Brew weighs most heavily against last year’s growth tactics.

“LinkedIn spent 2026 turning the shortcuts you were taught into penalties.”
— Jodie Cook, Forbes, July 23, 2026

What to do this week

Pull your last ten LinkedIn posts and check three things: engagement-pod or group-chat coordination behind the early comments, any “comment X if you agree” language, and any link sitting inside the post or the first comment. Fix all three in your next post — write one detail only you could know, ask a real question instead of prompting a canned reply, and move any link to a follow-up DM. Track reach on that post against your last five before deciding the fix worked.