← Back to library

Run a six-stage publishing pipeline for a technical blog

Andrew's site runs an OpenClaw pipeline that finds topics on popular repositories, tech forums and feeds, researches, drafts with Claude, validates structure, deploys an Astro build to a VPS, submits through IndexNow and reads Umami analytics. By March 2026 it had published 38 posts and 136 answer pages, which he says saved about 130 hours.

  • OutcomeGo from spotting a trending developer tool to a validated, deployed and indexed post within minutes, with analytics feeding back into topic choice.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditAndrew
View original
Works with
OpenClawClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Your developer blog covers fast-moving topics
  • You can host a static site yourself
  • You want posts cited by AI assistants

Not for: Publications with editorial standards that require human writing; Topics where errors cause harm

What do you need, and what do you get?

You need

  • Topic sources such as trending repos and forums
  • A static site generator and server
  • Analytics and search submission

You get

  • Live articles plus short Q&A pages
  • Search engine submissions
  • Analytics-driven topic adjustments

How does it work, step by step?

  1. Mine topicsScan trending repositories, forums and feeds for subjects with little coverage yet.
  2. Research and draftGather facts and write with a fixed structure: summary first, self-contained sections, specific figures.
  3. ValidateCheck heading order and required elements before building.
  4. Deploy and checkBuild, sync to the server and confirm the new URL returns success.
  5. Submit and learnNotify search engines, then use analytics to shape the next topics.

The prompt

Our own prompt, inspired by Andrew and written to work in OpenClaw and Claude. Values in lime are placeholders.

Prompt0 variables
Topic: [trending tool]. Research it from its repository, docs and two independent sources. Draft a post with a short summary first, sections that each answer one question, specific figures with sources, and a last-verified date. Run the structure checks in [checklist]. Save as a draft for my review; do not deploy or submit to search engines.

Inspired by Andrew: How We Publish 37 Blog Posts Without Touching a Keyboard: The OpenClaw Content Pipeline — andrew.ooo. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Fully automated publishing can spread mistakes quickly; spot-check facts.
  • Freshness labels only help if the content is actually re-verified.

Our take

Andrew's OpenClaw pipeline is instructive as architecture, not as a recommendation to publish unattended. Mining topics from popular repositories, forums and feeds, researching, drafting with Claude, validating structure, deploying an Astro build, submitting through IndexNow and reading Umami analytics is a complete loop, and by March 2026 he reports 38 posts and 136 answer pages. Put a human review step between draft and deploy, at least for claims and numbers, because a fast wrong post damages trust. The validate and health-check stages are worth copying into any content workflow. Structuring pages so they can be cited is useful whatever writes the words. Keep analytics and deploy credentials narrowly scoped. Measure whether automated posts actually rank or convert before scaling volume. Disclose AI assistance where platforms or readers expect it. Pause the pipeline when quality metrics drop rather than letting it run on autopilot for months. Review search console data monthly against what the pipeline claimed it published.

Where the time goes back: Each post that took hours of research, writing and distribution is produced in minutes.

FAQ

Is there a human editor?
The site describes the posts as published autonomously.
What structure does he recommend?
A dense summary near the top, sections that each answer a question, concrete numbers and a last-verified date.

Source and credit

Inspired by Andrew. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How We Publish 37 Blog Posts Without Touching a Keyboard: The OpenClaw Content Pipeline — andrew.ooo
Creator
Andrew
Published on
andrew.ooo
Original date
Mar 16, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
OpenClaw
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.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingPrompt✓ AI dry run

Build a product messaging framework

Turn what you know about a product into three message pillars, each with the buyer outcome, its evidence and the feeling it should create.

Credit: OpenAI Academy

Minutes
MarketingWorkflow✓ AI dry run

Build a weekly LinkedIn Ads pacing report with Claude

Have Claude turn each week's LinkedIn Ads results into one written report: progress against pipeline targets, the main platform metrics, the audiences, campaigns and ads that are falling behind, ads whose click-through to the landing page is slipping, and a short list of last week's finished work and what is planned next.

Credit: Patrick Cumming

An afternoon+
MarketingSkill✓ AI dry run

Mine your post history for ideas without false claims

Get post ideas grounded in what you actually published, with the agent asking before it treats anything in your history as a promise or fact.

Credit: Eugeniya Ivanova

Under an hour
MarketingRoutine✓ AI dry run

Send your creative team a daily ad and audience digest

Get a daily report in Slack that compares what your customers are saying with what competitors are running in their ads, so your creative team knows where the gaps are.

Credit: Camm (@cjfeth)

Under an hour