- Article
- 4 minutes read
- Reviewed August 3, 2026
A WordPress content item moves through states from its initial creation to publication, revision, archiving or deletion. The post status tells WordPress how that item should be handled and who can normally access it.
A status is not merely a label shown in the editor. It affects queries, permissions, scheduling, public visibility and editorial workflows.
The Main Built-In Post Statuses
Auto-Draft
WordPress may create an auto-draft when a new editor screen opens. It is a temporary record used before the author explicitly saves meaningful content.
Draft
A draft is saved but not published. Users with suitable capabilities can continue editing it in the administration area.
Pending Review
Pending content is complete enough to be reviewed but cannot or should not be published by its current author. It supports workflows where contributors submit work to editors.
Future or Scheduled
Scheduled content has a future publication date. WordPress uses its scheduling system to change the status to published when the time arrives.
Published
Published content is available according to its visibility and the public behaviour of its post type. A published entry is not necessarily discoverable if the type is not publicly queryable.
Private
Private content is published for authorized users rather than the general public. Visibility depends on capabilities and may differ from a custom internal content system.
Trash
Trashed content is removed from normal views but retained temporarily so it can be restored until the trash is emptied.
Inherit
Revisions and attachments can use an inherited status that follows the status or context of a parent object.
Status and Visibility Are Related but Different
The editor may offer Public, Private and Password protected visibility choices. These options interact with status and content settings, but they are not a universal access-control model.
Password protection hides rendered content behind one shared password. It does not identify individual users or provide granular capabilities.
Editorial Workflows
A simple workflow might move from draft to pending review to published. Larger teams may need legal review, translation, approval or scheduled campaign stages.
WordPress supports custom statuses at a technical level, but integrating them fully into the editor, list tables, counts, permissions, REST API and publishing controls requires careful development and testing.
Status Transitions and Automation
WordPress fires actions when a post changes status. Plugins can use these transitions to send notifications, clear caches, update external systems or create audit records.
Automation should be idempotent where possible. A retry or repeated save must not create duplicate external records or send the same notification indefinitely.
Scheduling Reliability
Scheduled publishing depends on WP-Cron or an alternative server-side scheduler. Low-traffic sites or disabled cron systems can miss the expected time until another request triggers the queue.
Mission-critical publishing should be monitored and may benefit from a real system cron job that calls WordPress on a predictable schedule.
Deleting and Retaining Content
Moving an item to the trash is not the same as permanently deleting it. Retention requirements should define how long drafts, revisions, trash and personal data remain available.
Plugins that connect related records must decide what happens when a parent item is trashed or deleted. Silent cascading deletion can cause irreversible data loss.
A Practical Lifecycle Policy
- Define who can create, review, publish, edit and delete each content type.
- Document which statuses the editorial team should use.
- Clarify whether private content is truly restricted for the intended audience.
- Monitor scheduled publication when timing matters.
- Decide how revisions, trash and archived records are retained.
- Test integrations on every relevant status transition.
Frequently Asked Questions
Is private a post status or a visibility setting?
WordPress represents privately published content with the private status, while the editor presents privacy through its visibility controls.
Can WordPress have custom post statuses?
Yes, developers can register custom statuses, but providing a complete editorial interface and predictable integration requires more than registering a label.
Why did a scheduled post publish late?
WordPress scheduling commonly depends on WP-Cron, which is triggered by requests. Configuration, traffic or disabled cron execution can delay the transition.