“AI content” is not the problem. Unedited AI content is. Here are the exact patterns that signal low quality, and how to remove them in a 10-minute edit pass.
Background
In 2026, “is this AI?” is the wrong question — most published web writing has AI somewhere in the pipeline. The right question is “does this article help a real reader?” Low-quality AI content fails on specific, identifiable axes: no point of view, no specifics, no friction, no story. Once you can name the failure modes, you can fix them.
How to tell
- The opening paragraph could apply to any topic in the niche.
- Every section is roughly the same length — a sign of templated generation.
- The article uses words like “comprehensive,” “leverage,” “robust,” or “today.”
- Lists have exactly 5, 7, or 10 items with parallel grammatical structure.
- There are no concrete numbers, screenshots, names, dates, or product references.
- The conclusion restates the introduction.
Step by step
Each step is a copy-paste prompt or shell command. Run the whole pass on your draft before publishing.
-
Rewrite the opening to “only-this-topic” specificity. Prompt:
Below is the opening of an article: <paste sentences 1-3> Rewrite sentence 1: - Must be a specific claim (number / case / counter-conventional) - Drop "This article will" / "In today's" / "With the rise of" openings - After rewriting, the line CANNOT work if pasted into an article on any other topic (must be topic-specific) Give me 5 candidates. For each, explain why it fails the "pastable into another topic" test. -
AI cliché sweep. In your article directory:
# Surface all high-risk words first grep -E -ni "comprehensive|robust|powerful|essential|seamless|empower|ecosystem|disrupt|crucial|indispensable|game-changer|delve into|tapestry|navigating|in today's fast-paced|harness the power" your-article.mdEach match: delete, or replace with something specific (“comprehensive features” → “supports 12 file formats”).
-
One real piece of evidence per ~400 words.
Allowed evidence: - Specific tool name + version ("Astro 5.2", not "a modern static site framework") - Specific price / time / number ("$20/month" / "Q1 2026" / "1500 users") - A screenshot or code snippet (not a placeholder) - First-person experience ("Last week I hit" / "On my last submit" / "I tested it myself") - A citation with a link + dateSanity check:
# Rough count of "evidence anchors" — should be ≥3 per 1000 words grep -cE "[0-9]+|\.(com|io|org)|v[0-9]" your-article.md awk 'BEGIN\{RS=""\} \{print NR, NF\}' your-article.md # paragraph length distribution -
Break the 5-parallel-bullet pattern. AI almost always emits 3-5 parallel bullets. After spotting:
Before (5 parallel): - Improves efficiency - Enhances experience - Streamlines workflow - Reduces errors - Saves cost After (mixed forms): - Efficiency: 30 min → 5 min (measured on 50 runs) - Experience: review score 4.2 → 4.7 (company avg 3.9) - Workflow got one step longer — by design, because X - Error rate didn't move materially. Don't believe the sales deck - Cost depends on team size; small teams may not save muchRule: at least 2 of 5 in a different sentence form, at least 1 with counter / nuance (“didn’t save” / “no change”).
-
Insert one counter-intuition paragraph. Prompt:
Below is an article on <topic>: <paste article> Identify the 3 most common reader priors (things readers default to believing before opening this piece). Then write a ≤120-word counter-conventional paragraph challenging ONE of them: - Must include a concrete reason (number / case) - No clickbait reversal-for-its-own-sake - Open the paragraph with "Counter to what most expect..." - End with an actionable alternative -
Cut the conclusion paragraph. AI will reliably write “In conclusion” / “To wrap up” / “Hope this helps”. Surface and delete:
tail -30 your-article.md grep -E -ni "in conclusion|to summarize|hope this helps|to sum up|in summary|wrapping up" your-article.mdDelete the entire paragraph. End on your last concrete point — no summary required.
-
Read aloud. For every paragraph, ask:
- Could this paragraph appear unchanged in a competitor's article? - If I swap the topic word ("Vercel" → "Netlify"), does it still read fine? - Is it just "adjective + adjective + adjective"? Any "yes" → rewrite or delete. -
Add real expertise metadata. In frontmatter or the footer:
--- author: "Your real name" authorBio: "5 years indie dev / shipped 3 apps / runs a 1500-article content site" publishedAt: 2026-05-21 lastUpdated: 2026-05-21 reviewedBy: "<colleague / editor name, optional>" ---Add a “why I wrote this” line at the end:
I wrote this because: I ran this exact process last year, got stuck on <specific blocker> for X days, and couldn't find a single piece of writing that explained <critical step> clearly. Every step here is something I've actually done.
Common pitfalls
- Trying to fix bad AI output with another AI pass. The second pass usually just makes it more generic. Edit by hand.
- Adding “expert quotes” that the AI invented. If you cannot verify the quote, delete it — fake attributions are the fastest way to lose trust.
- Removing all AI-ness by adding more words. Short and specific beats long and hedging.
- Believing “I rewrote 30%” is enough. The 70% you kept might still be the problem if it is structural.
Who this is for
Indie publishers using AI-assisted workflows who want their output to read like a person actually wrote it.
When to skip this
Pure aggregation sites that explicitly do not want a voice — though those struggle to rank anyway in 2026.
FAQ
- Can I detect AI content with a tool?: Detection tools are unreliable in 2026 — both false positives and false negatives are common. Trust the structural signals above more than any classifier score.
- Should I avoid AI entirely for quality?: No. The best 2026 workflows blend AI drafting with human editing. The all-or-nothing framing is the wrong one.
- How long should the edit pass take?: Plan 20-30 minutes per 1500-word article. If you are spending 60+ minutes, the original draft was too thin — restart with a better prompt.
- What about translated AI content?: Same rules, harder execution. Translations need a native speaker pass — machine translation plus AI generation compounds the problem.