Following one post from a raw idea all the way to a live URL touches nearly every part of the scheduling and generation system, and walking through that full path end to end makes the individual pieces — the queue, the scheduler, the generation step — click together in a way that reading about each one separately doesn’t quite achieve.
Stage One: The Idea Enters the System
A post’s lifecycle starts wherever its topic originates — a keyword from a gap report, a manually chosen title, an item from a competitor RSS feed flagged for rewriting. At this stage nothing has been scheduled or generated yet; there’s just a topic and, ideally, enough brief-level context (angle, intent) to generate something useful from it.
Stage Two: Entering the Queue
Once a topic is committed to — whether through a manual “add to queue” action or as part of an automated workflow — it enters the queue in a waiting state, either with a specific scheduled time or marked for ASAP publishing. This is the first point the post has a queue entry and a visible status, even though no content has been generated yet.
Stage Three: The Scheduler Picks It Up
When the post’s scheduled time arrives (or immediately, for ASAP items), the scheduler — whether running via `schedule:work` or cron-triggered `schedule:run` — picks it up from the waiting state and begins processing. This is the point the queue status typically shifts from waiting to a processing or in-progress state.
Stage Four: Generation Happens
The actual content generation runs during this stage — pulling in whichever mode applies (Generate, Paste-Generate, or Search-Scrape), applying tone and voice settings, generating a featured image if that pipeline is enabled. This is usually the most time-consuming stage and the one most exposed to the 300-second timeout on large batches.
Stage Five: Publishing to WordPress
Once content generation completes, the finished draft gets pushed to the connected WordPress site via the REST API — converted into the appropriate content format, categorized, and published, at which point the post genuinely exists as a live URL rather than an internal queue entry.
Stage Six: Post-Publish Steps
Depending on which add-ons are active, publishing can trigger further downstream steps — auto-interlinking scanning for internal link opportunities, rank tracking auto-enrolling the new page, instant indexing submitting the URL for faster search engine discovery. These happen after the post is technically live, extending the full lifecycle a bit further than the moment of publishing itself.
Where to Go Next
For the complete picture of every stage in this lifecycle, see the complete guide to scheduling and workflow automation.
