When should you use it?
- You publish search content regularly
- AI drafts need hours of cleanup
- Made-up stats have slipped into posts
Not for: Topics where you cannot verify claims; Pages meant to rank without genuine expertise
What do you need, and what do you get?
You need
- Target keyword
- Top search results and community threads
- Brand voice notes
You get
- Outline
- Draft with sources
- Fact-check report
How does it work, step by step?
- ResearchCollect the top results and community discussions; save URLs.
- OutlineStructure headings around the questions searchers ask.
- DraftWrite in your voice using only the research notes.
- Fact-checkA separate stage lists every claim and marks it sourced, unsupported or wrong; remove the last two.
- PolishAdd title, meta description and internal links; an editor approves.
The prompt
Our own prompt, inspired by u/GonkDroidEnergy on r/Agentic_SEO and written to work in Claude, ChatGPT and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
List every factual claim in this draft. Draft: {draft} Sources: {sources} For each claim return: quote, matching source URL or NONE, verdict (SUPPORTED / UNSUPPORTED / CONTRADICTED). Then return the draft with UNSUPPORTED and CONTRADICTED claims removed or marked.
Inspired by u/GonkDroidEnergy on r/Agentic_SEO: Gave away my 10-agent SEO pipeline on Gumroad. People kept asking for a hosted version. So I built it.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- One giant prompt mixes jobs and hides errors.
- A fact-checker using the same notes cannot catch gaps in the notes.
Our take
The author's lesson that separate stages beat one mega-prompt matches our experience. The fact-check stage is the one to copy first. Tighten it so the output is a claims list with a verdict per claim, which makes the editor's job a checklist instead of a reread. Research before outlining. Draft only from the outline. Reject any claim without a source link. Polish for search after facts are solid, not before. Keep human voice edits as a distinct pass. Measure how many claims the fact-check kills each week. Do not auto-publish from the pipeline. Disclose AI assistance where required. Prefer primary sources over secondary roundups. When a claim is soft, rewrite or cut it rather than hedging vaguely. Archive the claims list next to the published URL for later disputes. Kill the whole draft if more than a few major claims fail the fact-check rather than patching endlessly. Keep the research notes beside the draft so editors can see where each claim began.
Where the time goes back: Cleanup time drops because unsupported claims are removed before an editor sees the draft.
FAQ
How many stages do I need?
Is the fact-check reliable?
Source and credit
Inspired by u/GonkDroidEnergy on r/Agentic_SEO. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Gave away my 10-agent SEO pipeline on Gumroad. People kept asking for a hosted version. So I built it.
- Creator
- u/GonkDroidEnergy on r/Agentic_SEO
- Published on
- Original date
- Jan 26, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.