Quick answer
AI content detectors do not detect AI. They measure how statistically predictable text is, and AI writing tends to be predictable. That is a correlation, not a test, which is why clear technical writing by a human is routinely flagged and lightly edited AI writing routinely is not. OpenAI withdrew its own classifier in 2023 for low accuracy. Treat any detector score as weak circumstantial evidence, never as proof, and never make a consequential decision about a person on one.
This topic is unusually badly served, because the people writing about it are mostly selling detection, teaching people to evade detection, or reassuring readers that Google does not care. All three skip the same thing: what these tools actually measure.
Once you know that, everything else — the false positives, the evasion advice, the search-ranking question — resolves cleanly.
Two statistical properties, under various names.
A detector scores text on these and outputs a probability. That is the whole mechanism. There is no watermark, no signature, no hidden marker. It is reading style and inferring origin.
Watch out
Follow the logic to its conclusion: any human who writes clearly, consistently and without stylistic flourish scores as AI. That describes technical documentation, legal writing, non-native English speakers who learned formally, scientific abstracts, and anyone taught to write plainly. These groups are systematically disadvantaged by detectors, and the tools cannot distinguish them from generated text because there is nothing to distinguish — the measured property is genuinely the same.
The most informative data point is that OpenAI shut down its own AI Text Classifier in July 2023, citing low accuracy. The organisation with the deepest knowledge of how its models generate text concluded it could not reliably detect that text.
Commercial detectors advertise high accuracy figures. Those come from vendor testing on their own datasets, typically unedited AI output versus clearly human writing — the easy case. Real-world text is edited, mixed, and written by people with varied styles, and accuracy degrades sharply there.
| Text type | Detector reliability | Why |
|---|---|---|
| Raw AI output, unedited | Reasonably good | Low perplexity, uniform rhythm. The easy case |
| AI output, lightly edited by a human | Poor | Editing raises perplexity quickly |
| Human writing, plain and clear | Poor — false positives | Clarity looks like predictability |
| Non-native English speakers | Poor — false positives | Formal learned constructions score as predictable |
| Technical or legal writing | Poor — false positives | Precision and consistency are the point |
| Short passages under 300 words | Unreliable either way | Not enough text for the statistics to mean anything |
| Human-AI collaborative writing | Meaningless | The question has no binary answer |
My take
The false positive problem is not a rough edge, it is the defining flaw, and it falls hardest on people least able to contest it — students, non-native speakers, junior staff. A tool that accuses someone of dishonesty with a confidence score it cannot justify, against an accusation that is close to impossible to disprove, is not a tool I would put in a disciplinary process. I would not use detector output as evidence about a person, and I would push back hard on any institution that did.
The question most publishers actually care about, and the answer is clearer than the discourse suggests.
Google’s published position is that it rewards helpful, reliable, people-first content regardless of how it is produced, and that using automation to manipulate rankings violates its spam policies. Those two statements are consistent: the target is low-value content produced at scale to game search, not the use of a writing tool.
What actually gets penalised is thin, unoriginal, unhelpful content — which AI makes cheap to produce in volume, which is why the two get conflated. The causal factor is the thinness, not the tool.
Nor does Google run a detector in the way people imagine. Given that purpose-built detectors are unreliable, a search engine assessing billions of pages would be poorly served by a signal with that error rate. Quality signals are more robust and harder to game.
A practical section, because this happens frequently and the advice available is poor.
Point two is worth acting on before you need it. If you write anything that could be challenged, work somewhere with version history. A draft that evolved over six hours across forty revisions is close to unfakeable.
Detection is the wrong lever. If your concern is quality and honesty, there are better ones.
AI detectors measure predictability and infer authorship, which is a reasonable heuristic and an unreasonable basis for a decision about a person. They work on the case nobody needs help with, and fail on edited text, plain human writing, and non-native speakers — with the failures landing disproportionately on people who cannot push back.
For publishers the question is a distraction. Google does not penalise AI assistance; it penalises unhelpful content, which it has always done. Write something worth reading, verify what you claim, add what only you know, and the tool you drafted with stops being relevant.
And keep your version history. It is the only evidence that actually works.
For why AI text has these statistical properties, see what ChatGPT is and how it works. For producing content that holds up on its merits, the best AI content creation tools covers the workflow side. The same detection argument now surfaces in recruitment, where candidates write applications with AI and employers reach for screening tools in response, which is covered in best AI tools for HR.
They measure two statistical properties: perplexity, meaning how surprising the word choices are, and burstiness, meaning how much sentence length and complexity vary. AI output tends to be predictable and uniform, so detectors score text on those properties and infer authorship. There is no watermark or hidden signature involved.
Only on unedited AI output, which is the case least in need of a tool. OpenAI withdrew its own AI Text Classifier in July 2023 citing low accuracy. Commercial vendors advertise high figures from testing on their own datasets of raw output versus clearly human writing, and accuracy degrades sharply on edited or mixed real-world text.
Because they measure predictability, and clear, consistent, unflorid human writing is predictable. This systematically affects technical documentation, legal writing, scientific abstracts, non-native English speakers who learned the language formally, and anyone trained to write plainly. The detector cannot separate them from generated text because the measured property genuinely is the same.
Google’s stated position is that it rewards helpful, reliable, people-first content regardless of how it is produced, while treating automation used to manipulate rankings as spam. What gets penalised is thin, unoriginal, unhelpful content, which AI makes cheap to mass-produce. The causal factor is the thinness rather than the tool used to write it.
Version history is the strongest evidence available. Draft history in Google Docs or Word, showing a document evolving across many revisions over hours, is close to unfakeable. Also useful: research notes, outlines, browser history, and being able to discuss the choices in the piece. Work in a tool that records revisions before you need it.
Ask which tool and what score, in writing. Produce version history and research notes. Run known-human text, such as something you wrote years ago, through the same detector to demonstrate false positives. Cite OpenAI’s withdrawal of its own classifier. Ask what false positive rate the institution assumes, and offer to discuss the content in detail.
Not as evidence about a person. The false positive rate falls hardest on those least able to contest an accusation, and the accusation is close to impossible to disprove. Better approaches are a disclosure policy rather than a ban, reviewing for accuracy rather than origin, requiring first-hand material a model cannot have, and discussing the work.
Yes, readily, which is itself an argument against relying on detectors. Editing raises perplexity quickly, so lightly edited AI text frequently passes while unedited plain human writing fails. Any tool that is trivially defeated by the exact behaviour you would want to encourage — human editing and improvement — is not measuring what it claims to measure.
A practical Triumphoid guide to gemini gems vs chatgpt custom gpts: my blogging automation use…
A practical Triumphoid guide to claude projects vs custom gpts for wordpress content systems, with…
RPA is not dead, it has been correctly demoted to a last-resort integration layer. Here…
Advanced short-term vs long-term vector-backed context persistence across asynchronous execution runs.
A practitioner comparison of marketing automation platforms for 2026: HubSpot, Marketo, ActiveCampaign, Brevo, Klaviyo, Pardot,…
ChatGPT cannot watch video, it summarises transcripts. Which video types work, the four methods ranked,…