How AI Text Detection Actually Works
- →AI text detection comes in three families: perplexity-style statistics, trained classifiers and rubric-based reading. Each one fails in a different way.
- →Perplexity is the most-cited signal, but it depends on the model doing the scoring, and it punishes formal and second-language writing.
- →Trained classifiers learn the AI output they were trained on. New models and simple paraphrasing push them off balance.
- →Burstiness looked like a durable signal. In ContentTrace internal testing on October 3, 2026, it separated human and AI text no better than chance, so it now carries no weight.
- →Rubric-based reading looks for evidence of a writer thinking, like opinions, insider detail and self-correction. Those signals are the most useful ones for editing.
- →No method is certain. A signal-level breakdown helps a writer improve a draft. A single number used as a verdict on a person does harm.
In 2023, a Stanford team ran 91 essays from the TOEFL, the English exam many non-native speakers take for university admission, through seven popular GPT detectors. Every essay was written by a person. On average, the detectors labeled them AI-generated 61.22% of the time. Eighteen of the 91 were flagged by all seven tools at once.
That result says less about those students than about how detection works. The tools weren't broken in some random way. They were doing exactly what they were built to do, and the method itself had a blind spot that lines up with careful, plain, textbook English.
Most people treat detectors as a black box: paste text in, get a number out. The box only holds a few kinds of machinery, though. Once you know which kind you're looking at, the scores start to make sense. So do the failures.
Knowing which one produced a score tells you how far to trust it.
The three ways software reads text for signs of AI
The first family is statistical. It measures properties of the text itself: how predictable each word is, how much the vocabulary varies, how sentence length swings. These signals come from the way language models generate text, one likely token after another. That process leaves marks.
The second family is the trained classifier. Someone collects a large pile of human text and a large pile of AI output, then trains a model to tell them apart. It never explains itself. It just returns a probability.
The third family is rubric-based reading. Instead of counting tokens, it reads the text against a fixed list of things human writers tend to do and AI drafts tend to skip. Does an opinion shift mid-argument? Is there a detail only an insider would know? Is the writer working something out, or delivering a finished answer?
Most commercial detectors lean on the first two, because they're fast and cheap at scale. For anyone trying to improve a draft, that's the wrong choice. The statistical signals are real, but they're the easiest to game and the least useful to a writer. Knowing a paragraph is "low perplexity" tells you nothing about what to change.
What perplexity actually measures, and where it breaks down
Perplexity is the signal everyone in this space talks about. The idea is simple: given everything that came before, how surprising is the next word? A language model assigns a probability to every possible next token. Low perplexity means the text was predictable. High perplexity means it was full of unexpected choices.
Human writers usually score higher, and not because they're trying to be unpredictable. They pick the odd word that fits better. They mention something specific that bends the paragraph off its expected path. Nobody plans those choices. They're what happens when a real person turns a thought into language.
Researchers have refined the idea. DetectGPT, from a Stanford group in 2023, compares a passage with slightly altered copies of itself and checks whether the original sits near a peak of the model's probability curve. On fake news written by the 20-billion-parameter GPT-NeoX model, it raised the detection score (AUROC) from 0.81 for the best earlier zero-shot method to 0.95.
The model-dependency problem few vendors mention
Here's the catch, and it explains most strange scores: perplexity is always measured relative to a specific model. A sentence that looks predictable to one model may look surprising to another. Detector accuracy therefore depends on which model is doing the scoring, and as frontier models change, older detectors drift. The number on screen looks absolute. It isn't.
It also explains the TOEFL result. Writers working in a second language often choose common words and safe structures on purpose. To a scoring model, that careful English looks like machine output. The method can't tell "predictable because a model wrote it" from "predictable because the writer was being careful."
The obvious fix is to look at rhythm instead. Burstiness, the swing between short and long sentences, is a property of the text alone, so it shouldn't depend on any model. The original version of this post called it a more durable signal than perplexity. That claim didn't survive testing.
In ContentTrace internal testing on October 3, 2026, burstiness separated human and AI text no better than chance. The test used 162 scored samples: 75 human texts written before 2022 and 87 AI replies from Claude, ChatGPT and Gemini.
Burstiness is still shown in every ContentTrace report, under Statistical Proxies, but for reference only. It carries no weight in the score, and neither do the other statistical proxies. These are internal results on a modest sample, and short texts give weaker signals.
Why would rhythm fail as a number when readers clearly feel it? The best explanation is that a raw variance figure ignores context. Plenty of human writing is evenly paced (an email, a how-to), and current models vary sentence length more than older ones did. Readers notice rhythm in relation to meaning. A spreadsheet of sentence lengths can't.
"Burstiness separated human and AI text no better than chance, so it is now shown for reference only."Content Trace · Statistical Proxies Signal
Trained classifiers: fast, confident and tied to the past
A classifier is only as current as its training data. It learns what AI output looked like when the dataset was built, and every new model release moves the target. That's why classifier vendors retrain constantly, and why a score from one month may not match a score from the next.
The most public example is OpenAI's own classifier. By the company's published numbers, it caught 26% of AI-written text and wrongly flagged human text 9% of the time. OpenAI withdrew it on July 20, 2023, citing its low rate of accuracy. There's a dry lesson in that. The company that built the model couldn't reliably spot the model's writing.
Paraphrasing makes things worse. A 2023 University of Maryland paper tested watermark, neural, zero-shot and retrieval-based detectors against recursive paraphrasing, where another model rewords an AI draft, sometimes more than once. Detection rates dropped significantly, while text quality fell only slightly in many cases. To a classifier, a reworded draft can look like a different kind of text entirely.
Rubric-based reading: the signals that come from thinking
The third approach is the interesting one, because its signals aren't arbitrary. They describe something real about how a mind shows up on the page. This is the approach ContentTrace takes. It explains its results with 32 signals in 8 sections, and the sections that count describe the writing, not the token math.
Opinion drift and self-correction
When people work through an argument in writing, their thinking moves. They start a paragraph committed to one position and finish somewhere slightly different, because writing it down revealed something. Sometimes they catch it and correct it. Sometimes they let the drift stand, because it's honest.
AI drafts rarely do this. The model heads toward a conclusion from the first word and keeps going. The result is technically logical and strangely flat. Nothing in it surprised its own author.
Specificity that feels accidentally true
Human writers reach for concrete details: a particular number, a named place, the tool that broke on a Tuesday. Those details make writing credible and personal at once. AI drafts reach for illustrative generalities because the model has no experiences to draw from. It can invent specifics, but invented ones have a different texture. They're too clean and too perfectly on point. Real specifics are slightly awkward, and that imperfect fit is part of what makes them feel true.
This is where rubric-based reading earns its keep. A low score on Insider/Niche Knowledge doesn't accuse anyone of anything. It points at the paragraph that needs a real example. You can run a draft through Content Trace to see the breakdown section by section, free and with no account.
Why no detector is 100%, and what the score is for
A common framing says AI detectors are useless unless they're perfect. Nobody judges other diagnostic tools that way. A radiologist reading an X-ray isn't right every time, and neither is a bank's fraud filter. The real questions are whether the signal beats chance, whether its errors follow patterns you can account for, and whether the tool is honest about its limits.
Honesty is where most tools fall down. A single percentage implies a certainty no method has. The frustration that causes is specific and avoidable. Picture a student who wrote every word watching a dashboard call the essay 90% AI, and there's nothing in the report to argue with. The TOEFL study shows that this happens to real people, at scale.
The better use of any score is editorial. Treat it as a map of where a draft reads as generic, then fix those places. That works whether the draft started with a model, a person or both, and it's the use that actually helps content perform with readers, in search and in AI answers.
Frequently asked questions
For the research on beating detectors, Can AI Detectors Be Fooled? goes further into paraphrasing and its limits. The Behavioral Signals That Give AI Writing Away covers the rubric signals one by one. And Why Your AI Detector Score Keeps Changing explains the drift described above.
- Liang et al. (2023), GPT detectors are biased against non-native English writers (arXiv)
- Mitchell et al. (2023), DetectGPT: Zero-Shot Machine-Generated Text Detection using Probability Curvature (arXiv)
- Sadasivan et al. (2023), Can AI-Generated Text be Reliably Detected? (arXiv)
- OpenAI: New AI classifier for indicating AI-written text (with July 2023 withdrawal note)
Colin H builds ContentTrace at Web Thrive. He has spent 20+ years in B2B SaaS marketing, running content, SEO and AEO programs, and now builds them around AI-assisted content production. Read the ContentTrace manifesto


