
LinkedIn is taking urgent action to stop “AI slop” filling its platform.
The business social network has received sustained criticism in recent weeks over the increasing amount of low-quality, automatically generated posts that are shown to users. It appears to be the result of professionals who wish to promote themselves and increase their visibility by sharing posts on the site – but then hand the actual writing of them to chatbots such as ChatGPT or Claude.
The company is now seeing hundreds of thousands of attempts to make automated comments each day, and has blocked billions of other automation attempts in the last couple of months.
It comes amid increasing concern about AI slop across a range of publishing platforms on the web. Substack, for instance, announced this week that it would be working with AI detector company Pangram to let users automatically assess whether a post was likely to have been written using artificial intelligence, and adding a new feature to let writers explain whether they have used the technology in their writing.
Now, LinkedIn says that it is taking a range of steps to fight the problem, and to make the site a place that lets users “connect with real people and share their real perspectives, ideas and expertise”.
“AI slop is a top priority for all of us,” said Hari Srinivasan, LinkedIn’s chief product officer, in an update posted to the site. “We really care about this.”
That will include a new button to allow users to report when a post or comment “seems like AI slop”. “Slop is hard to define and the definition changes; this lets us tune our models and make better feeds,” said Mr Srinivasan.
As well as improving LinkedIn’s tools for detecting slop, any users who are posting content that has been reported by users will see feedback in a dashboard. That will help those making such posts know that real humans see their updates as being inauthentic, Mr Srinivasan said.
LinkedIn will also look to improve the tools that are able to automatically spot such AI slop. That will help the app suggest it less in feeds, he suggested.

-annual-meeting.jpeg?width=1200&auto=webp&trim=0%2C0%2C0%2C0)