Aimogen gives you full, explicit control over how AI-generated content is saved and published. Nothing is auto-published unless you tell it to be. Post status is a first-class setting, respected consistently across all generators and execution paths.
This document explains how post status works, where it is configured, and how Aimogen behaves in edge cases.
Where Post Status Is Defined #
Every Aimogen content generator includes a Post Status selector.
You’ll find it in:
- Single AI Post Creator
- Bulk AI Post Creator
- CSV-Based AI Post Generator
- Amazon Product Review Writer
- Amazon Product Roundup Creator
- Listicle & Structured Content Generator
- Dialog & Conversation Generator
There is no global hidden override. The status you select in the generator is the status that is applied.
Supported Post Statuses #
Aimogen supports all standard WordPress post statuses.
Draft #
The post is created but not visible publicly.
This is the recommended default for:
- Bulk generation
- CSV imports
- RSS or YouTube-based content
- Affiliate and review content
Draft gives you a review step without losing generated data.
Published #
The post is published immediately after generation.
Use this only when:
- You fully trust your prompt and model
- You have tested output quality
- You understand the risks of auto-publishing
Aimogen does not delay or queue published posts. Once generation finishes, the post goes live.
Pending Review #
The post is saved as pending.
This is useful for:
- Editorial workflows
- Multi-author sites
- Approval-based publishing
WordPress’ normal review and approval mechanisms apply.
Private #
The post is created but visible only to logged-in users with permission.
Useful for:
- Internal documentation
- Staging content
- Client previews
- Internal knowledge bases
How Status Is Applied Internally #
For each generated post:
- Aimogen finishes AI execution
- Content is post-processed
- The WordPress post is created
- The selected post status is applied immediately
There is no intermediate state and no background status changes.
Bulk Generation Behavior #
In bulk generators:
- Every post in the batch uses the same status
- Status is applied per post, not per batch
- A failure in one item does not affect others
If a bulk run is interrupted:
- Posts already created keep their assigned status
- No partial or half-saved posts are left behind
CSV and Structured Imports #
CSV-based generation follows the same rules:
- One row = one post
- Each post receives the selected status
- CSV data cannot override post status unless explicitly supported by custom logic
If you need per-row publishing control, that must be handled manually after generation or via workflows.
RSS and YouTube Inputs #
Because RSS feeds and YouTube videos are processed via the Bulk AI Post Creator, they inherit the same publishing rules:
- You choose the post status once
- Every generated post uses that status
- There are no RSS-specific or YouTube-specific overrides
Draft is strongly recommended for these inputs.
Editing Generated Posts Later #
Once a post is created:
- It behaves like any normal WordPress post
- You can change its status manually
- You can edit it with the AI Content Editor
- Revisions, autosave, and editorial tools work normally
Aimogen does not lock or protect generated posts.
What Aimogen Does Not Do #
Aimogen will never:
- Auto-publish without being told to
- Change post status after creation
- Promote drafts to published automatically
- Schedule posts unless explicitly configured elsewhere
- Override WordPress publishing permissions
If a user cannot publish posts normally, Aimogen cannot publish for them either.
Common Mistakes #
- Running bulk jobs with “Published” enabled by accident
- Assuming RSS or YouTube content defaults to draft automatically
- Expecting per-item publishing rules in bulk mode
- Forgetting that status is applied immediately after generation
Always double-check post status before starting a run.
Best Practices #
- Use Draft for all bulk and automated generation
- Publish manually after review
- Use Pending for editorial teams
- Reserve Published for controlled, tested workflows
- Treat AI generation as content creation, not content approval
Summary #
- Post status is explicitly selected per generator run
- Draft, Published, Pending, and Private are supported
- Status is applied immediately and consistently
- Bulk and CSV generation use a single shared status
- Aimogen never auto-publishes without instruction
Aimogen respects WordPress publishing rules strictly. You decide when content goes live — the plugin never makes that decision for you.
