Astricode Ops can analyze wp_postmeta without modifying or deleting records.
The analyzer reports:
- total records;
- distinct keys;
- data and index size;
- empty keys;
- orphaned postmeta;
- estimated orphaned payload.
The query scans the entire table and is therefore run on demand. The result is stored so the page does not need to repeat the full scan every time it is opened.
Safe orphaned postmeta cleanup
A wp_postmeta row is considered orphaned only when its post_id no longer exists in wp_posts.
Astricode Ops can delete these rows in bounded batches.
This cleanup does not delete metadata attached to posts, pages, properties, revisions or attachments that still exist.
Frequent keys and estimated origin
The analyzer can show frequent meta keys, estimated origin, record count and estimated payload.
Origin classification is diagnostic. It does not mean that a key is safe to delete.
Operational and reversible inspector
The operational inspector lets you search for a specific meta_key.
The table can show:
- estimated origin;
- status;
- number of records;
- affected content items;
- estimated payload;
- protection;
- Inspect action.
Critical WordPress metadata is visibly protected.
Inspect a selected key
The detail view provides:
- total records;
- distinct content items;
- estimated payload;
- largest value;
- estimated origin;
- owner status;
- reversible rows;
- orphaned rows;
- protection status.
The view also provides a protected value sample so you can inspect representative data before deciding what to do.
Export and manual protection
Supported keys can be:
- exported as a complete copy;
- manually protected.
Exported data should be stored securely because metadata can contain sensitive plugin or site information.
Reversible quarantine
For eligible rows whose parent content still exists, Astricode Ops can copy the selected batch into quarantine before removing it from wp_postmeta.
Orphaned rows are intentionally excluded from this reversible path because their missing parent content prevents a meaningful restoration relationship. Use Safe orphaned postmeta cleanup for those rows instead.
Quarantine requires typed confirmation of the exact key.