LinkedIn’s AI Slop Crackdown Is Finally Hitting Reach

LinkedIn’s AI Slop Crackdown Is Finally Hitting Reach
LinkedIn’s fight against synthetic corporate chatter is moving from irritation to enforcement. More than a million users have now tapped its “Seems like AI slop” control, while the platform says suspected AI-generated posts are losing reach.

The company introduced the reporting option on July 30, amid mounting concern that generative tools were flooding the professional network with polished but hollow “thought leadership.” One analysis by AI detector Pangram found that 41% of LinkedIn long-form posts were flagged as fully AI-generated.

LinkedIn’s response combines automated classification with human judgment. Hari Srinivasan, its chief product officer, said the company deliberately favored member feedback over a system that might misidentify legitimate writing: “We want members to get feedback from real humans on what sounds authentic — not just have an AI detector review it and get it wrong.”

That feedback is now producing visible consequences. Srinivasan said members are “now experiencing 40% less views on what we classify as AI slop” than only weeks earlier. When a post receives sufficient reports, LinkedIn will show its author a Post Analytics message saying that some members believed it “seems like AI,” framing the measure as a warning rather than an outright takedown.

The platform says it has built safeguards against coordinated or unfair targeting and is approaching reports “assuming good intent.” But the shift also signals a broader recalibration: LinkedIn has upgraded its AI classifiers, removed an AI feature that could “enhance your post,” and previously pledged action against mass-produced comments with little or no human involvement.

The debate over LinkedIn’s identity has spilled into wider culture-war shorthand. Elon Musk amplified a post claiming that users were editing work histories to add “AI” and remove “DEI,” a separate observation that underscores how quickly AI has become a résumé signal as well as a content problem.

Continue reading https://foxvector.com/stories/01a0361b-e25e-2039-72cd-25b356e9a94e