AI Content Pipeline for Solo Affiliate Sites: The Stack We're Actually Using

This site is built and run by a solo operator using AI agents (Claude Code) for research, drafting, and publishing. This guide is the map of that pipeline — what each stage does, and which tools sit in it. We’ll link out to individual tool reviews and comparisons as we actually test each one; until a review carries the “tested firsthand” badge, treat any tool mention here as a research note, not a recommendation.

The five stages

1. Research — finding underserved, high-intent keyword clusters instead of chasing head terms we can’t win.
2. Brief / outline — turning a keyword into a content brief with a clear angle.
3. Draft — AI-assisted first draft, written to the brief.
4. Firsthand verification — the stage that can’t be skipped: actually using the tool being reviewed, with screenshots and specifics, before anything gets marked as tested.
5. Publish & monitor — shipping via Git-based deploys, then watching Search Console data to decide what to expand or rewrite.

Why this order matters

Google’s 2026 core updates have specifically targeted “scaled content abuse” — pages generated in bulk without editorial oversight. Stage 4 above exists specifically to avoid that outcome. Nothing here is published purely from spec sheets or secondhand summaries.

Tools tested so far

• Frase — content briefs and competitor SERP structure. Useful for research, but every stat and “fact” it generates needs independent verification before it goes near a draft.
• Make — no-code automation. The free tier genuinely works, but watch the default trigger schedule and OAuth scope settings, or things fail in ways that don’t show up in the run log.
• n8n — no-code automation with an AI assistant that can build a workflow from one sentence. Watch its default trigger interval even more closely than Make’s — see our Make vs n8n comparison for the head-to-head on the same real task.

We’ll keep expanding this list with links to individual reviews and head-to-head comparisons as we test more of the stack.

Tools mentioned in this guide