Content Workflow

End-to-end article creation - from identifying audit gaps to publishing optimized content.

Overview

The content workflow in Studio follows a structured process. Each step uses specific MCP tools that handle data fetching, content generation, and publishing. The workflow is designed so that each article directly targets weak areas in the domain's audit scorecard.

You don't need to run these steps manually. The Write Article skill orchestrates the entire flow. This page explains what happens under the hood so you can customize or intervene at any step.

If you use the Discovery Brief, rerun discovery after saving it. The content planner reads the latest stored discovery context, so the rerun is what makes the updated buyer and proof signals available downstream.

How the Discovery Brief Helps

The Discovery Brief is not just a note-taking form. It supplies strategic inputs that the site crawler usually cannot infer cleanly: who the real buyer is, which services matter most, what objections need to be handled, what proof is available, which terms should be preferred, and which queries or claims should be excluded.

Visibility query selectionImproves which prompts and queries are monitored by adding ICP fit, business priority, proof fit, geo fit, and brand-safety signals.

Brief generationHelps content plans include the right audience, angle, objection, differentiator, proof points, and CTA instead of relying on generic topic matching.

GuardrailsPrevents off-brand terminology, weak comparisons, unsupported claims, and low-value topics from leaking into planning or writing.

Monitoring and Debugging Runs

Studio now exposes the article-writing trail directly in the product. Use this when a run looks stuck, when you need to confirm what Claude actually did, or when the short status UI is not enough.

Quick Rewrite and the regular Write Article flow both end up in the same article queue and use the same transcript and telemetry surfaces. If you can debug one, you can debug the other.

Task Step DrawerThe quick skim view. Use it to scan recent steps across active tasks. Step opens the exact row in the full viewer. Tools opens grouped tool calls for the same run.

Terminal ViewerThe full debugging page. The left side is the run list. The right side shows one selected run in detail with summary cards, filters, and saved transcript rows.

Timeline viewThe full play-by-play. Use this when you need exact prompts, exact output text, or the real order of events.

Tools viewThe short version. Use this when you want one row per tool call so slow, noisy, or failing steps stand out fast.

Terminal vs Backend rowsTerminal rows came from the Claude or terminal side. Backend rows came from linked server task logs. Looking at both helps when one source feels incomplete.

Fastest debugging workflow

Start in the Task Step Drawer if you only need a quick status check.
Open the latest article run in Terminal Viewer when you need more detail.
Use Tools view first for slow steps, failed steps, or large outputs.
Switch to Timeline when you need the exact saved text or event order.
Use the built-in help popup in both surfaces if the labels are unclear.

The summary cards show tool count, tool time, result time, input size, output size, and the slowest tool. They are meant to help you find bottlenecks quickly, not just confirm that a run exists.

Workflow Steps

Load client profile

aeo_get_client_profile

Fetches the composite profile for a domain - latest audit scores, voice profile, client dossier, CMS connection, and recent articles. This is the starting context for every content session.

Refresh discovery context

Discovery + Discovery Brief

Before planning articles, run discovery and save the Discovery Brief so audience, pain points, proof points, differentiators, preferred terms, and exclusions are available to the system.

Gap analysis

Audit scorecard

Review the audit scorecard to identify weak criteria. Low scores in Q&A Format, FAQ, or Content Freshness are the most common gaps that content can directly address.

Topic selection

aeo_create_topic

Choose a topic that addresses the identified gaps. Claude suggests 3-5 topics based on the audit data and latest discovery context. The selected topic is tracked in the pipeline for status management.

Research and outline

Block pipeline

Claude creates a block-based outline using one of 11 article type recipes. The brief can influence audience framing, angle, objections to answer, proof requirements, and CTA direction.

Write blocks

aeo_write_block

Blocks are written in generation order (not display order) using the domain voice profile. Each block generates HTML content respecting its word count target.

Review and enhance

aeo_rewrite_block

Review the assembled article. Rewrite individual blocks, add new sections, or remove blocks that feel redundant. Each edit preserves the rest of the article.

Save and publish

aeo_publish_to_cms

Save the article to the database, then publish to the connected CMS. For Webflow, FAQ sections are extracted into a separate field and categories are auto-mapped.

Block-Based Pipeline

Articles are composed of blocks - independent content units with defined types, word count targets, and generation order. The pipeline uses 50+ block types organized into two categories.

Content blocks

Generate article content. Each has a word count target and generation order.

herointroductionbody-sectionconclusionfaqkey-takeawayscomparison-table

Processing blocks

Add metadata and structural elements. Run after content blocks are complete.

seo-metainternal-linksschema-markupreading-time

Blocks are written in generation order, not display order. The introduction might be generated after the body sections so it can reference what the article actually covers.

CMS Publishing

The final step publishes the article to the domain's connected CMS. Currently supported: Webflow. The publishing step handles several CMS-specific transformations automatically.

H1 extractionStrips the H1 from article body and uses it as the CMS name/title field

FAQ separationExtracts FAQ section into a dedicated CMS field for structured display

Category mappingResolves category names to CMS option IDs via the connection config

Default imageSets a default featured image from the connection config for required image fields

Rate limiting500ms delay between API calls to respect CMS rate limits

Adding New Clients

No code changes are needed to add a new client. When you start working on a domain for the first time, Studio auto-onboards it with a few interactive questions. You can also upload a client research dossier (.md file) via the Dossier button in the content panel for deeper brand context. The full setup is:

Run /write-article newdomain.com - auto-onboarding creates an initial voice profile
Optionally provide writing samples for a richer voice profile
Set up CMS connection in the admin dashboard (one-time per domain)