Safe WordPress Maintenance groups standard residual-data cleanup into separate, explicit actions.
Each category runs separately, with confirmation and bounded batches.
The tool is designed not to affect published posts, pages, properties, images or approved comments when you are using the intended category actions.
Maintenance categories
The interface can include:
Expired transients
Temporary caches whose expiration date has passed.
Orphaned transient timeouts
Expiration records whose associated transient value no longer exists.
These are safe to delete under the plugin’s orphan rule.
Old revisions
Historical versions of posts and pages.
The currently published content is not the revision being removed.
Revisions can be useful for recovery, so Astricode Ops treats them as a separate manual cleanup choice.
Autosaves
Temporary automatic copies created by the WordPress editor.
Trashed content
Posts, pages or other content already in the Trash.
Spam comments
Comments already classified as spam by WordPress.
Trashed comments
Comments already moved to the Trash.
Orphaned comment metadata
Comment metadata whose associated comment no longer exists.
Batch size
Each supported category provides a per-batch selector.
On a large production database, bounded batches help keep each maintenance request predictable.
Review before cleaning
Do not clean a category solely because its count is non-zero.
Examples:
- revisions may still be useful;
- expired transients are usually disposable but can regenerate;
- trashed content may have been placed there temporarily;
- spam moderation may still require review under your site policy.
Example final state
The documentation walkthrough removes only the controlled residual data selected for the demonstration and leaves an unrelated expired transient category untouched by choice.
The goal is safe maintenance, not forcing every counter to zero.