How LinkedIn is Continuing to Tackle AI Slop



  • Less Generic Content Seen on LinkedIn: Recent efforts have already helped reduce views of content classified as AI slop by 40%,
  • People Are Using the “Seems Like AI Slop” Button: More than 1 million members have used the new “Seems Like AI Slop” button since we rolled it out in August.
  • We continue to improve and invest in our automation defenses: On comments alone, everyday we are now catching hundreds of thousands of automated comment attempts, and have blocked billions of automated activity (posting at scale, slop) in the last couple months alone.

 

LinkedIn is continuing its efforts to reduce AI slop and promote authentic platform conversations. Within the first two weeks after launching the "Seems like AI slop" feedback option in August, more than one million members have used it to help improve content quality.

 

We're now beginning to share this feedback signal directly with members through post analytics, offering private insights into how content is being received by the community, while maintaining safeguards to prevent misuse. Recent efforts have already helped reduce views of content classified as AI slop by 40%.

 

The “Seems like AI slop” feedback option on LinkedIn

 

These initiatives are reinforcing our commitment to keeping LinkedIn a place for real people, real expertise, and real perspectives.

 

How Does LinkedIn Define AI Slop?

 

“AI slop” includes low-effort, likely AI-generated content that may sound polished on the surface but lacks a clear point of view, unique perspective, or substance. It goes beyond style to include content that feels generic, repetitive, recycled, or designed primarily to game attention rather than add to a meaningful conversation.

 

What Is Changing?

 

  • Introduction of “Seems Like AI Slop”: The ability for members to provide feedback on posts and comments they believe are AI slop, namely low-quality, generic, inauthentic content, by clicking on the three dots on the top right side of a post and reporting content as “seems like AI slop.” These reports help inform our classifiers. If a post receives enough community feedback, the author may see a message in their post analytics to help them understand how their content is being received.
  • Updating writing tools to focus on proofreading: We are replacing "enhance your post" feature with tools that proofread and improve clarity without changing a member's voice, reinforcing the distinction between AI assistance and AI slop.
  • Expanding our AI Slop classifiers: We’ve built backend content classifiers to spot and limit distribution of AI slop.
  • Stronger Defenses: LinkedIn is blocking hundreds of thousands of automated comment attempts every day and has prevented billions of automation attempts in recent months, helping keep conversations authentic and human.

 

What does this mean for the conversations on LinkedIn?

 

It’s more important than ever that people can learn from real voices, authentic perspectives, and lived expertise. Everyday more people come to LinkedIn to have real conversations. They’re connecting, sharing what they know and learning from each other in real-time. The knowledge shared on LinkedIn is shaping how professionals access information and their careers.

 

FAQs

 

Q: How can someone mark something as “Seems like AI slop?”

A: If you see a post or comment that you believe is AI slop, you can share feedback with us. To identify content as AI slop, Click the … More icon in the top right corner of the post or comment. Click Seems like AI slop. Your feedback helps LinkedIn better understand what members consider low-value, generic content. This feedback informs our content quality work and helps us improve the feed experience for everyone.

 

Q: As an author, will I know if my content is marked as AI slop?

A: If a specific piece of content reaches a threshold of feedback from other members, you will see a tip in your Post analytics. This is intended to help creators understand how their content is being received by the wider community.

 

Join the conversation: