On July 30, 2026, LinkedIn added an option to the menu on every post: Seems like AI slop. Not “appears AI generated”, not “low quality”. Slop, a piece of internet slang, now part of the interface of a platform owned by Microsoft.
The same day, LinkedIn removed its own enhance your post button, which had used a language model to rewrite whatever members typed. It was replaced with a proofreader. Chief product officer Hari Srinivasan described the replacement as something that corrects your words without changing your voice.
Both moves landed in a week when the numbers about AI content were everywhere. Which raises a question worth asking before accepting any of them: who is holding the thermometer, and do they also sell air conditioning?
What the button really does
Less than the name suggests. Clicking it hides the post from your own feed and returns a message thanking you for the feedback. Beyond that, a LinkedIn spokesperson said flagged posts get reduced algorithmic reach, comparable to marking something as not interested.
The flags also train LinkedIn’s classifiers. There is no removal, no public label, and no stated penalty on the account. One outlet noted plainly that what happens to a flagged post beyond reduced reach remains unresolved, which suggests the policy is still being worked out.
So it is a personal mute button with a downrank attached and a training signal underneath. That is not nothing. It is also a long way from the enforcement mechanism the wording implies, and worth knowing before anyone panics about being reported.
The numbers do not agree with each other
Here is what has been published about how much of LinkedIn is machine written.
Pangram, an AI detection company, scanned roughly a million posts through an opt-in Chrome extension and found more than 40 per cent of long-form LinkedIn posts fully AI generated, with X around 25 per cent. Originality.ai, a competing detection firm, reported 53.7 per cent of long-form posts as likely AI in January, based on 3,368 posts from 99 influential profiles. In July, the same company scanned 5,000 posts and reported 81 per cent. Pangram’s browser extension users, meanwhile, see roughly two thirds of what they scroll flagged.
Four figures for one phenomenon, ranging from four in ten to eight in ten. Every one of them has been reported as a fact.
They are not directly comparable, and the firms say so. Different models, different sampling, and a real distinction between “fully AI generated” and “likely AI”. But the gap is the story. When two thermometers disagree by forty degrees, the useful question stops being what the temperature is.
Who benefits from a large number?
The studies come from companies whose business is detection.
Pangram raised nine million dollars in July, led by Menlo Ventures, in the same week its LinkedIn figures were circulating. GPTZero has raised 13.5 million. Copyleaks around seven million. Originality.ai runs profitably selling to publishers and SEO teams. Substack launched a detector through a partnership with Pangram, and its chief executive said outright that he did not want Substack turning into LinkedIn.
This is not a conspiracy and there is no reason to think it is coordinated. It is something more ordinary and harder to correct for. The organisations producing the measurements are the ones that profit when the measurement is alarming, and the press cycle those measurements generate is what funds the next round.
The detection firms are also more careful in their own materials than the coverage of them is. Pangram’s chief executive calls his figures a lower bound, on the reasonable grounds that people who install an AI detection extension are not a random sample of internet users. That caveat rarely survives into the headline.
Do the detectors work?
Reasonably well, and the honest answer has a large asterisk on it.
Pangram claims a false positive rate of 0.01 per cent, and a critic writing against the detection industry still concedes its performance has held up across independent studies. This is not snake oil, and the first generation of detectors it improved on genuinely was.
The asterisk is where the rate was established. Controlled benchmarks are not the informal, multilingual, stylistically mixed environment of a real social feed, and nobody has independently tested that model on non-native English at scale. Which matters, because the people most likely to be wrongly flagged are exactly the people writing in a second language, or writing in a formal register, or writing with the kind of consistency that good editing produces.
The fine print is more revealing still. Originality.ai’s terms of service instruct users not to apply its output to any purpose carrying a legal or material impact on a person, employment decisions included. The company selling detection disclaims the use most buyers have in mind. It also states openly that it is built for publishers and marketers, not students, and will not defend its accuracy for academic use. The same probability score, sold as a business tool to one buyer and an accusation to another.
So why did LinkedIn move?
It would be tidy to conclude that a nine million dollar startup pushed Microsoft into action. It is not what happened.
LinkedIn has better data than any external detector. It built the writing button, so it knows at the point of generation how much content came out of it. It does not need a browser extension sampling a million posts to describe its own platform.
The timeline runs the other way, too. Disclosure labels for AI content date to 2024. The downranking initiative launched in May 2026, announced by editorial vice president Laura Lorenzetti, who wrote that overusing AI at scale dilutes what real conversation produces. The July studies arrived after the platform was already acting.
The driver is more prosaic. A feed people distrust is a feed people scroll less, and less scrolling is less inventory to sell. That is a revenue problem visible in LinkedIn’s own dashboards, and it does not require anyone else’s research to notice.
Microsoft also has a specific position to protect. It is selling AI assistance into every product it owns, so “AI is bad” is not a message it can afford. “Slop is bad, and AI used well is fine” is exactly the line Srinivasan drew when he wrote that AI and slop are not the same thing.
Why not stop it at the compose box?
The announcement never addresses the obvious point. LinkedIn does not need members to identify AI writing, because it is better placed to identify it than anybody outside the company.
It built the writing button. Every post that came out of enhance your post was generated inside LinkedIn’s own product, which means the platform knew at the moment of generation. It does not need a browser extension sampling a million posts to describe its own feed.
And if a startup running a Chrome extension can flag content at scale, a company owned by Microsoft can do it in the compose box. If the goal were fewer generated posts, the intervention writes itself: a message before publication saying this reads as machine written, try again in your own words.
They are not doing that. The flag arrives after publication, from another member, and removes nothing.
The arithmetic behind that choice
Two reasons, and neither is about authenticity.
The first is inventory. Blocking a post at the compose box means one fewer post in the feed. Posts are what the advertising sits between, and a platform does not reduce its own supply to solve a quality complaint. A hide button removes nothing. The post still exists, still reaches the poster’s network, and still carries ads for everyone who did not flag it.
The second is liability. Intervening before publication makes LinkedIn the accuser. Every false positive becomes an angry member with a legitimate grievance and no meaningful appeal, and the platform owns every one of those conversations. Handing members a button moves the accusation off the company and onto the membership. Same signal, no exposure.
The private analytics nudge confirms both readings. LinkedIn is willing to tell a poster their writing came across as inauthentic, quietly, after the fact, with nothing attached to it. That is the exact limit of what the company will do: enough to demonstrate concern, not enough to cost anything.
Which makes the feature easier to describe than the branding suggests. It is a hide button with a training signal attached. Members do the labelling for free, the classifiers improve, and the feed stays exactly as full as it was.
The part nobody has solved
A button that lets one member reduce another’s reach, anonymously, with no adjudication and nothing to appeal, is open to obvious misuse. A ghostwriter quoted in coverage of the launch put it plainly, warning the feature looks ripe for abuse against legitimate posts.
The competitive version is the sharpest. In any field where practitioners compete for the same clients on the same platform, a free anonymous way to suppress a rival’s visibility will not sit unused.
And human intuition about machine writing is worse than people believe. What gets flagged is short sentences, clean structure, plain vocabulary and a consistent register. Those are the surface features of generated text. They are also what careful editing produces, and what anyone writing in a second language tends to produce. The same problem shows up wherever machines are asked to judge writing: the signal being measured is style, and style is not authorship.
LinkedIn is at least aware of the distinction. It is testing a private note in a poster’s analytics when members have flagged their writing, framed as feedback about coming across as inauthentic, not as an accusation. That is a more sensible design than a public label, and it is the first time writers have had any signal at all about how their work reads to strangers.
What to make of all this
Three things seem solid.
The problem is real. Anyone who has scrolled LinkedIn recently does not need a study. The default output of a language model asked for a post is the same shape every time, and that shape is now the texture of the platform.
The size of it is unknown. Four in ten and eight in ten are different worlds, and the people producing both figures sell the remedy. Treat any specific percentage as a claim, not a finding.
The remedy is aimed at the visible symptom. A button addresses what members complain about in public. It does not address ad density, feed ranking, or the fact that the platform shipped the generator and is now shipping the alarm.
For anyone writing professionally, the practical consequence is smaller than the noise around it. Material that only one person could have written cannot be generated, cannot be mistaken for generation, and does not depend on a detector to prove it. The difference between a machine and a person was never really about the sentences. It was always about who had been somewhere and could say what it was like.
The thermometer question stays useful, though. When the next number arrives, and it will, the first thing worth checking is who is holding it.
The Guides That Get Your Book Written, Published, and Sold
Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.
We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.