Public build · Technical case study

BuildZn SEO content agent

A business-aware editorial system that ranks problem topics, gathers primary sources and prepares drafts with a review report.

Node.jsGemini RESTEditorial checks

01
Rank a bounded backlog by business fit, evidence and observed demand
Input and entry point
02
Check published articles and draft history for overlapping intent
Implementation stage
03
Build a source pack, content brief and outline
Implementation stage
04
Prepare an unpublished draft with claim, link and editorial checks
Output and operational boundary

IMPLEMENTATION EXCERPT / agent/lib/pipeline.js

const sources = [];
for (const source of topic.sources) sources.push(await researcher(source));

// … brief, generation, checks and independent review
report.status = 'ready-for-human-review';
// draft.md stays unpublished; no publish operation exists.

Selected implementation lines with explanatory comments. Omitted work is marked with “…”. Inspect the complete source below.

Evidence boundary

Observed issues are evidence of a problem, not keyword search volume. Generated work stays unpublished until a person checks facts, examples and usefulness.

THE PROBLEM

Where the work gets stuck.

A headline generator cannot know which problems fit a business, what evidence supports the answer or whether another article already covers the intent.

Follow the implementation

Rank a bounded backlog by business fit, evidence and observed demand
Check published articles and draft history for overlapping intent
Build a source pack, content brief and outline
Prepare an unpublished draft with claim, link and editorial checks

Technical scope

Manual Node.js workflow with a business profile, project evidence, a topic backlog, optional Search Console signals, fresh source retrieval, structured generation and deterministic quality gates.

The decision that matters

Observed issues are evidence of a problem, not keyword search volume. Generated work stays unpublished until a person checks facts, examples and usefulness.

Inspect the evidence

Public source reviewed October 1, 2026. Pinned implementation links preserve the version reviewed. This walkthrough does not reproduce private client details.