Claude Code Pipeline: 7 Commands for SEO Content at $0.45/Post

A developer operating a content SEO pipeline through Claude Code for a year has open-sourced the system. The repo (MIT license) contains 7 slash commands in .claude/commands/ — each a markdown file with a strict role and output contract. Commands read pipeline.yaml for state, run one step, pause at a human gate, and update state for stateless re‑entry.

Pipeline flow

/seo-research — uses Perplexity Deep Research API (~$0.45/post)
/seo-brief — human gate
/seo-write
/seo-optimize — 10-check scorecard
/seo-publish — Sanity HTTP API → IndexNow ping

Four human gates exist so the operator retains control over angle, brief, copy, and publish decision. The flow can be resumed mid‑post the next day with /seo-daily.

Real results

For one brand running this pipeline: 131 → 964 avg impressions/day in 12 months (7.3×). Monthly impressions 2,142 → 39,240 (18×). Blog content from the pipeline drove 51.8% of all Google Search Console impressions across 119 posts. Clicks did not grow proportionally — the operator notes titles/meta were not tuned for CTR yet and is building a /seo-refresh command for next iteration.

Technical notes from the developer

Sanity MCP issue: create_documents_from_json overwrites custom _id with a UUID, breaking deterministic frontends. The publisher uses Sanity’s direct HTTP mutation endpoint instead — documented in the repo.
Brand voice in one YAML: config/seo-settings.yaml — no hardcoded brand anywhere. Fork → swap one file → you’re running your brand.
Pluggable CMS: Sanity is the reference implementation, but swapping to WordPress, Contentful, or Webflow is a single file edit.

Use case

This is for developers who run content/marketing ops using Claude Code and want to see a concrete, reproducible pattern for chaining slash commands into a production pipeline.

📖 Read the full source: r/ClaudeAI