Our AI content pipeline wrote a correct post nobody wanted to read

Correct is the floor, not the bar

Our first AI-written post had every fact traced, scored 17 of 17 on our SEO checklist, earned a second AI agent's sign-off and cleared a pre-deploy check. The founder read it and sent back a three-word verdict: "correct but boring."

A post can pass every gate you own and still fail the only gate that matters: a stranger's ten seconds.

The paragraph he picked to make the point covered a bug where unknown URLs on our site served the home page with HTTP 200. True, verified, and interesting to exactly one team. His reaction: who cares.

AI already delivers correct. If your checks only measure correctness, your content is unfinished in a way your checks can't see.

The AI didn't make the post boring. The brief did.

Our brief asked for the honest inside story of our pipeline, costs and what broke, and the writer delivered exactly that, correctly, starting with a section titled "What is an AI content pipeline?"

An AI draft answers the brief you wrote, not the one you meant.

Nobody in the chain asked who the reader was or what they could do afterwards. The first post had no reader promise at all. Its facts were internal trivia: dates, token prices, how many work sessions we ran. None of them changed a decision for a stranger.

So the rewrite starts with one sentence, written before any research: "After reading, the reader can ___." If we can't fill the blank, the topic dies. Put that sentence at the top of your next brief.

Six questions catch correct-but-forgettable content

A fact checker asks "is it true?" These six ask "would anyone care?", and you can answer each one in about 30 seconds.

1. Competitor swap: could a competitor's AI have written this sentence? Highlight every sentence where the answer is yes. If that's most of the page, it's generic.
2. First-hand detail: is there at least one detail only someone who actually did the thing would know? Add a number, a failure or a decision from your own work.
3. A claim to argue with: is there one statement a reader could disagree with? If everything is safe, nothing is memorable.
4. Opening: would a stranger read sentence three? The first two should state a sharper problem than the reader would, give a surprising result, or show a short scene.
5. Skim test: read only the title, headings and bold lines. Do they tell the whole story?
6. Next ten minutes: can the reader do or check something right after reading? If not, you wrote a report, not a post.

Run these on the draft, not on the topic. A topic can be fine and the draft still boring.

Headings that state a claim let a skimmer read your whole argument

A skimmer sees the title, the TL;DR, the headings, the bold lines and the callouts. Together those should carry the entire argument.

If the headings alone don't tell the story, the prose won't save it.

Our first post opened with the heading "What is an AI content pipeline?" That's a glossary entry. A skimmer learns nothing from it. The rewrite opens with "Correct is the floor, not the bar", a claim you can agree with, doubt or want proved. Definitions moved to the FAQ, where the people who want them can find them.

Rewrite every H2 in your own post as a claim. The sections that resist are the weak ones, and they identify themselves before anyone else sees them.

Our cost number was wrong in a way that looked fine

The first edition of this post said the draft call cost $0.04. It was $0.29, and the whole post cost about $0.61, not the $0.25 we printed. Our cost tracking had missed the writer's separate work session, and nobody re-derived the figure from the raw log before we published it. Generation is still cents; the error was in how we counted.

A plausible wrong number survives every check that only looks at the number.

Audit the measurement, not just the output, and when you publish a cost, say what you counted and what you left out. The itemized figures are in the FAQ below.

Add a reader gate that is not the writer

The fix for boring is a reader who isn't the author. Ours is a separate AI critic that reads the draft like a skeptical stranger and scores hook, value, skimmability and "who cares". It never rewrites. Fixes go back to the writer.

Fact gates check the words. A reader gate checks whether anyone would still be reading.

We're not alone in seeing why this matters. In one r/AiForSmallBusiness thread, small teams describe review quietly dying because AI output looks finished. And Google's guidance on generative AI content tells you to fact-check it, which is necessary and says nothing about whether anyone will read it.

You don't need agents for this. Paste your draft and the six questions into a fresh chat and ask: "Score this as a skeptical reader who found it in search. Verdict PASS or REVISE, one line per question. List fixes as notes. Don't rewrite." The scorer must not be the writer.

We staged this rewrite and diffed it against the live page before shipping, which is what our Text Diff Checker is for.

Frequently Asked Questions

What is an AI content pipeline?

A fixed sequence of steps that turns a topic into a published post with AI doing most of the work. Ours runs: reader promise, research, skim-first outline, writer draft, facts-only edit, reader gate, publish approval.

How much does AI-generated content cost per post?

About $0.61 for the first edition, counting everything. The Sonnet draft was $0.29. Two supporting work sessions (drafting overhead and the edit, SEO check and staging) cost $0.06 and $0.14. Keyword and search-results data cost $0.12. The first edition said $0.04 for the draft and about $0.25 total, which was wrong. The rewrite you are reading has cost $0.64 so far: one work session that ran the brief, the research, the outline, both writer drafts and both reader-gate reviews. The log now counts those writing and reviewing sessions. Vendor figures of $25-85 per article (for example on trysight.ai) include human editing time, which ours does not.

Can Google rank AI-written content?

Yes. Google says it judges quality and E-E-A-T, not how the content was produced. What it treats as spam is scaled content produced to manipulate rankings, and it asks you to fact-check AI output.

Do you disclose that AI wrote this?

Yes, in the byline above. Google suggests disclosing how content was made where readers would reasonably expect it.