What it does
Takes one seed keyword and turns it into a complete, reviewed, published article: keyword research → SERP analysis → competitor research → topic clustering → content brief → outline → drafting → five parallel quality reviews → internal linking → schema markup → automatic quality gate → mandatory human approval → publish.Why you should use it
This is the workflow that actually produces content — everything else in MAEL either researches or maintains what this one creates.Where to find it
Trigger it by its ID,full-content-pipeline, from the
Trigger workflow dialog (Overview,
Workflows, or ⌘K).
What information you must enter
Step-by-step
1
Open the trigger dialog and enter the JSON above
2
Click Trigger run
You’re taken to the Workflows list; the run appears shortly after.
3
Watch it progress
Open the run to see each step happen live — see
Monitor Your Workflow.
4
Wait for the approval checkpoint
The run pauses at
waiting_approval once the draft passes the
automatic quality gate. Go to
Take Action to review and decide.5
Approve (or reject)
Approving lets the run continue to publishing. Rejecting stops it —
nothing else happens automatically.
What happens after you click Trigger run
The engine works through the step chain above. For non-medical content, themedical-fact-checker step is automatically skipped — only YMYL
(medical) content needs it. Four other review steps
(seo-reviewer, readability-reviewer, eeat-reviewer, internal-linking) run
in parallel once a draft exists.
How long-running work is shown
Watch it live on the run’s execution timeline. This workflow has more steps than any other in MAEL, so it typically takes longer than a research-only workflow — expect it to pause and wait once it reaches the approval step, potentially for as long as it takes a human to review it.How to understand the output
Once published, the run’s output includes the article’s ID, its CMS post ID, and its live URL. The article itself appears in Content Studio with its SEO and readability scores — see Understand Your Results. If the draft fails the automatic quality gate, it becomesreview_required instead of reaching your approval queue — see
Understand Your Results → The content evaluation gate.
What action to take based on the output
- Passed the gate, awaiting your approval → read it, then Approve or Reject in Take Action.
review_required→ open the article and look at which of the nine evaluated dimensions failed before deciding what to do.- Published → check it live via the link in the article’s detail panel; monitor its performance later in Analytics.
Common mistakes
- Assuming
publish_mode: publish_nowmeans it publishes without review — it doesn’t; the approval gate is separate and always mandatory. - Using the dialog’s stale
target_keywordplaceholder instead of the realseed_keywordfield. - Not checking Take Action after
triggering — the run will sit at
waiting_approvalindefinitely until someone decides.