JD
All projects

AI-Assisted Publishing

SEO Content Engine

Keyword in, publish-ready article out — with a human where it counts.

Builder — pipeline design and brand-voice systemInternal tool

01

Problem

Content velocity decides organic growth, but every article was a bespoke project: research, outline, draft, edit, format, publish. Talented marketers spent their time on production mechanics instead of judgment.

Raw LLM drafting wasn't the answer either — one-shot articles read like everyone else's AI content, drift off brand voice, and skip the research that makes a piece rank.

02

Solution

The engine decomposes content production into stages with a defined artifact at each step: a research brief, an approved outline, a draft, a voice-refined article, a published post. Humans review artifacts, not walls of text.

Brand voice is a maintained asset — a spec built from the company's best writing, applied as a dedicated refinement pass. Drafting optimizes for coverage and accuracy; the voice pass optimizes for sounding like us. Separating those two jobs is what made the output publishable.

Workflow

Pipeline

Every arrow is a reviewable artifact. Editors approve outlines before drafting and articles before publish — judgment stays human, production gets automated.

1

Keyword

Target keyword plus intent classification — informational, comparison, or transactional.

2

Research

SERP analysis, competitor coverage, and entity extraction compiled into a research brief.

3

Outline

Structure generated from the brief: headings, questions to answer, schema opportunities. Editor approves.

4

Article

Section-by-section drafting against the outline, with citations from the research brief.

5

Brand voice refinement

A dedicated pass rewrites the draft against the voice spec — cadence, vocabulary, stance.

6

Publish

Formatted with metadata, FAQ schema, and internal links, then pushed to the CMS.

Perspective

AI-assisted publishing, honestly

The goal was never 'AI writes our blog.' It was moving humans from typing to deciding. Editors in this system make the calls that matter — is this angle right, is this claim true, does this sound like us — and stop doing the parts a pipeline does better.

The counterintuitive lesson: more stages, better content. Every stage boundary is a place to catch drift before it compounds. One-shot generation bakes its mistakes in; staged generation exposes them while they're cheap to fix.

Challenges

What was hard, and what I did about it

Sounding like a brand, not a model

Voice guidelines like 'confident but friendly' do nothing. The voice spec that worked pairs concrete before/after examples with explicit bans — words we never use, constructions we avoid — applied as its own pass.

Research that's real

LLM 'research' from parametric memory is a liability. The research stage works from fetched SERP and competitor data, and the drafting stage may only cite the brief — claims without a source get flagged for the editor.

Keeping humans genuinely in the loop

Approval steps decay into rubber stamps. Making review artifacts small — approve an outline, not a 2,000-word draft — kept editorial judgment real without killing throughput.

Tech stack

Built with

PythonClaude APISERP APIsWordPress REST APIJSON-LD / FAQ schemaPrompt chaining

Outcomes

What changed

  • 5xcontent throughput per editor — directional, and the floor not the ceiling
  • 2 approvalsper article — outline and final — keep quality human-owned
  • Consistentbrand voice across every piece, enforced by spec instead of memory

Next project

Claude + MCP