Content Queue
The Content Queue lets you line up specific blog post topics in advance. Each run automatically picks the next topic from the queue, giving you precise control over what gets published.
How it works
Topics in the queue are consumed in order (first in, first out). When a run starts—whether triggered by cron, manually, or via the API—it checks the queue:
- If the queue has a pending topic, that topic becomes the run's content focus and is marked as consumed.
- If the queue is empty, the run falls back to your Brand Context (primary topics and domain messaging) as usual.
- An explicit topic override (e.g. from the "Run Now" modal) always takes priority over the queue.
Managing your queue
Adding topics
Type a topic into the input field and press Add. You can optionally include notes that provide extra context for the AI writer (e.g. "Focus on the European market" or "Include a comparison table").
Reordering
Drag topics using the grip handle to change their order. The topic at position 1 will be used by the next run.
Editing and removing
Hover over a topic to reveal edit and delete buttons. You can update the topic text or notes at any time before it's consumed.
Clearing the queue
Use the Clear Queue button to remove all pending topics at once. This requires confirmation and does not affect your history.
AI topic suggestions
Available on Pro and Expert plans. Click Suggest to generate five topic ideas based on your Brand Context and recent post history. Each suggestion includes a brief reasoning. Click the + button next to a suggestion to add it to your queue.
History
Switch to the History tab to see all consumed and skipped topics. Each entry shows when it was used and links to the generated post, making it easy to trace which topic produced which article.
Plan limits
| Plan | Max queued topics |
|---|---|
| Free | 5 |
| Pro | 25 |
| Expert | 100 |
Why was my topic rejected as a duplicate?
When you add a topic, Wonderblogs compares it against your recent posts and any pending queue items. If the new topic is too close to something you've already covered, the add is blocked and the nearest match is named in the error message.
The same check runs again right before a post is written. If the workflow can't find a sufficiently fresh angle after three tries, the run is skipped and the queue topic is marked Skipped (duplicate) in your queue history.
You can adjust how aggressive this check is from Site Settings → Content Uniqueness. Pick Relaxed if your niche has a lot of legitimate topical recurrence (e.g. monthly market updates), or Strict if you want to push for fresh angles every time.