How to Spot AI-Written Content
You can read the signals (style tells, structural patterns, factual softness, missing lived experience) far more reliably than any detector tool. Here's what to look for and why it matters for editorial standards.
You can spot AI-written content far more reliably by reading for a cluster of signals (style tells, structural patterns, factual softness, and missing first-hand experience) than by trusting any detector tool. No single signal is conclusive; a careful human writer might hedge, and a heavily edited AI draft might not. But several signals together are a strong indication that a piece came off the line unedited. And that, not the origin itself, is usually what you actually care about: unedited content is content that skipped the human judgment that makes it trustworthy.
This is the recognition skill that sits beside quality and editing, read from the outside. Where common AI writing tells catalogs the patterns so you can remove them from your own drafts, this piece is about evaluating work you didn't write: a freelancer's submission, a contributor's article, a competitor's page, a draft you've been handed to publish. The aim throughout is pro-quality, not anti-AI: the tool is fine; unedited output is the problem.
The four signal groups
Read for these together. The strength of the read comes from convergence: one tell is noise, four is a pattern.
Style tells
The surface fingerprint of unedited prose. Watch for compulsive hedging (can, may, might, in some cases), filler phrases (it's important to note, when it comes to, in today's fast-paced world), inflated vocabulary (utilize, leverage, delve, robust, seamless), and empty transitions (Moreover, Furthermore, As such). Each is a default the model reverts to, and in combination they produce a flat, even, voiceless register that reads as nobody-in-particular.
A single filler phrase proves nothing; humans use them too. A draft that strings together five of them in two paragraphs is telling you something.
Structural patterns
Step back from the sentences and look at the shape. Unedited drafts tend toward suspicious symmetry: every section the same length, the same intro-bullets-wrapup template repeated down the page. They tend to over-list, rendering connected arguments as disconnected bullets. And they tend toward false balance, presenting two sides of everything and concluding "it depends" without ever landing on a position.
Human writing is lumpy and opinionated. It spends a paragraph where something matters and a sentence where it doesn't, and it eventually says what it thinks. Mechanical evenness and a refusal to commit are structural tells.
Factual softness
This is the most consequential group. Unedited AI content is often plausibly informative but specifically thin:
- Vague, unsourced claims. "Studies show," "experts agree," "many companies find": assertions with no actual study, expert, or company named.
- Round, convenient numbers. Statistics that are suspiciously clean and attached to no traceable source.
- Citations that don't resolve. References that look legitimate but can't be found, because the format is easy to fabricate and the substance was invented.
- Confident generality. A fluent explanation that never quite commits to a checkable specific.
When a claim sounds authoritative but evaporates the moment you try to verify it, that softness is a strong signal, and it's also the part that does real damage, which is why verification is its own discipline in fact-checking AI-assisted content.
Lack of specificity and experience
The deepest tell, and the hardest to fake. Unedited drafts rarely contain the texture of someone who has actually done the thing: a specific number from a real project, an unexpected detail, a hard-won caveat, an anecdote with particulars, an opinion formed by having been burned once. They describe the topic from the outside, in the generic terms anyone could assemble from reading about it.
Ask of any passage: could this have been written by someone who only read other articles on the subject? If yes, it probably was. First-hand specificity, the thing models can't retrieve because it was never written down, is the clearest signature of genuine authorship.
A spotting checklist
Run through these when evaluating a piece. The more that land, the stronger the signal.
- Do filler phrases and inflated words cluster unusually thickly?
- Is the structure mechanically symmetrical, every section the same shape and length?
- Is everything in lists, including ideas that should be argued in prose?
- Does the piece present every trade-off but never take a position?
- Are claims vague, sources unnamed, numbers suspiciously round?
- Can the citations actually be located and confirmed to say what's claimed?
- Is there any first-hand specificity: a real example, an unexpected detail, a hard-won caveat?
- Could this have been written by someone who only read about the topic, never did it?
No single yes is a verdict. A cluster of them means the piece almost certainly hasn't been through a serious human edit, which is the finding that matters.
Why AI-detector tools fall short
It's tempting to outsource all of this to a detector. Don't rely on one. Detector tools estimate the statistical likelihood that text was machine-generated, and they are wrong often enough, in both directions, that their scores can't be treated as evidence.
| Limitation | What happens |
|---|---|
| False positives | Careful, plain human writing, non-native English, and formulaic genres get flagged as AI |
| False negatives | Lightly edited or reworded AI output slips through as "human" |
| No ground truth | Detectors measure statistical patterns, not authorship; there's no fact they can actually verify |
| Easily defeated | Minor paraphrasing or a second editing pass changes the score |
| Unfair to act on | A probability score isn't proof, so using it to accuse, grade, or reject punishes the wrong people |
The practical conclusion: a detector is at most one weak signal to fold into your own reading, never a basis for a decision on its own. Accusing a writer, rejecting a submission, or grading work on a detector's score is both unreliable and unfair. Your own read of the four signal groups is more trustworthy, and crucially, it points at quality rather than origin.
Why spotting it matters, and what it's really about
The reason to develop this skill isn't to catch people using a tool. It's to protect editorial standards. Content that shows the tells is, far more often than not, content that skipped the human pass: facts unverified, voice absent, specifics missing, position dodged. Spotting the signals is really a way of detecting unedited work, and unedited work is the actual risk, whoever or whatever produced the first draft.
That reframing keeps you fair and keeps the focus right. A draft that started in a model but went through real verification, real specificity, and a real point of view is good content, full stop. A draft a human typed from scratch but never checked or shaped can be just as generic and just as wrong. Origin is a proxy; quality is the target. The signals matter because they correlate with the proxy, but you should always judge the work itself.
What to do when you spot it
Evaluate on quality, not origin, every time:
- Check the load-bearing facts. Take the most important claims and verify them against primary sources. Factual softness is where the real damage hides; this is the non-negotiable step.
- Demand specifics. Send it back for real examples, real numbers, and first-hand detail where the piece runs generic. Specificity is the fastest fix and the hardest tell to fake.
- Require a point of view. If it balances everything and lands nowhere, ask it to take the position the evidence supports.
- Hold the same standard you'd hold anything. Apply your normal editorial bar: accuracy, voice, structure, specificity. If the piece clears it, the origin is irrelevant. If it doesn't, return it regardless of source.
That's the whole stance: don't accuse, don't rely on a tool, don't treat "AI-written" as an automatic disqualifier. Read for the signals, use them to find work that skipped the human pass, and then judge, and fix, the work on its merits.
Where to go next
Spotting is the outward-facing half of a quality discipline:
- Common AI writing tells (and how to remove them): the same patterns from the inside, with a find-and-fix table for your own drafts.
- How to fact-check AI-assisted content: the verification workflow for the factual-softness signal, where the real risk lives.
- Quality & editing: the human-in-the-loop: why the human pass is what these signals are really detecting the absence of.
Spotting AI content well isn't about gotchas or detector scores. It's about reading for the absence of judgment, and then supplying it.
Less work, more on-brand content
Austen runs this whole workflow for you: from research to on-brand drafts that get found by Google and AI.
Start freeMore in Quality & Editing
-
Readability: How to Write Clearly Without Dumbing Down
Readable doesn't mean simplistic. It means a reader gets your meaning on the first pass without effort. Here's how to write for clarity, and why the same moves help AI cite you.
-
Self-Editing: How to Edit Your Own and AI's Drafts
Editing your own draft is hard because you already know what you meant. Here's how to create distance, switch from writer to editor, and run the passes that actually fix a draft.
-
Quality & Editing: The Human-in-the-Loop That Separates Good From Generic
Drafting is cheap now; judgment isn't. Editing has become the highest-leverage skill in content. Here's what drafts get wrong and the pass that fixes it.