< Back to situation

[REVISION HISTORY]

LinkedIn rolls out AI‑slop reporting button

Updated 20 times since CLSTR started tracking revisions of this situation.

What changed

2026-08-11 03:42 UTC → 2026-08-26 01:57 UTC · added removed

LinkedIn’s effort to curb low‑quality AI‑generated content accelerated after a July 2026 Pangram analysis of more than one million posts across LinkedIn, X, Reddit, Substack and Medium found that 41% of long‑form LinkedIn posts were fully AI‑written, with short‑form posts at roughly 30%. Subsequent Pangram studies in mid‑July confirmed LinkedIn’s lead, showing it accounted for about two‑thirds of all AI‑generated long‑form material despite representing only a third of the total content examined. In response, LinkedIn introduced a “Seems like AI slop” reporting button in the three‑dot menu of every post and comment on July 30, first in Brazil and Portugal and then across Europe, India and other markets, with a global rollout confirmed later that month. The button hides flagged items for the reporter, forwards a private report to LinkedIn’s feed‑ranking classifiers, and notifies the creator, feeding user‑generated signals into detection models. Chief Product Officer Hari Srinivasan stated that “AI slop is a top priority,” noting that the platform blocks hundreds of thousands of automated comment attempts daily and billions of AI‑generated attempts overall. The company also retired its “enhance with AI” writing assistant, replacing it with a lightweight proofreading aid to preserve the user’s voice. This shift aligns with broader industry trends seen on platforms like Snapchat, Substack, and YouTube. Additionally, the rollout coincides with upcoming regulatory requirements, such as Article 50 of the EU AI Act, which mandates the clear labeling of AI‑generated content. By late August 2026, LinkedIn reported that over 1 million users had utilized the new reporting feature within its first three weeks of availability. This high volume of user signals has contributed to a 40% weekly drop in the reach of posts categorized as low-quality AI content.

Versions

  1. 2026-08-26 01:57 UTC LinkedIn rolls out AI‑slop reporting button
  2. 2026-08-11 03:42 UTC LinkedIn rolls out AI‑slop reporting button
  3. 2026-08-07 17:42 UTC LinkedIn rolls out AI‑slop reporting button
  4. 2026-08-02 17:15 UTC LinkedIn rolls out AI‑slop reporting button
  5. 2026-08-01 16:41 UTC LinkedIn expands AI‑slop reporting button
  6. 2026-08-01 13:54 UTC LinkedIn AI content surge, reporting button expands
  7. 2026-08-01 08:38 UTC LinkedIn AI content surge, reporting button expands
  8. 2026-08-01 03:33 UTC LinkedIn AI content surge, reporting button expands
  9. 2026-08-01 00:11 UTC LinkedIn AI content surge, reporting button expands (2026)
  10. 2026-07-31 22:51 UTC LinkedIn AI content surge, reporting button expands (2026)
  11. 2026-07-31 19:34 UTC LinkedIn AI content surge, reporting button expands (2026)
  12. 2026-07-31 16:42 UTC LinkedIn AI content surge, reporting button rollout (2026)
  13. 2026-07-31 15:48 UTC LinkedIn AI content surge, reporting button added (2026)
  14. 2026-07-31 13:45 UTC LinkedIn AI content surge, reporting button added (2026)
  15. 2026-07-31 10:54 UTC LinkedIn AI content surge, reporting button added (2026)
  16. 2026-07-31 08:52 UTC LinkedIn AI content surge, reporting button added (2026)
  17. 2026-07-31 04:31 UTC LinkedIn AI content surge, reporting button added (2026)
  18. 2026-07-31 00:15 UTC LinkedIn AI content surge, reporting button added (2026)
  19. 2026-07-30 23:31 UTC LinkedIn AI content surge, reporting button added (2026)
  20. 2026-07-30 23:26 UTC LinkedIn AI content surge, reporting button added (2026)
  21. 2026-07-26 19:32 UTC LinkedIn AI-generated content prevalence (2026)

Only revisions since CLSTR began indexing content versions appear here. Select a version to see what changed compared to the one before it.