WP-Sweep is the well-known cleanup plugin by Lester Chan. It scans for orphan postmeta, orphan usermeta, orphan term relationships, expired transients, and revisions and reports a count per category. The default screen lists those counts and a Sweep button per category. That works for a single trusted admin clicking through, less so for a team that wants to see what is about to be deleted.

SleekView reads the same scan output and renders one row per orphan record. Source table, owning ID, inferred prefix, and rough size live as columns. Filters surface orphan wp_postmeta by meta_key prefix or orphan wp_usermeta by key pattern so you can decide on each cluster before sweeping.

Bulk sweep actions still dispatch through WP-Sweep's own functions, which keeps the plugin's behaviour intact. Audit entries land in a separate SleekView grid that you can export to CSV when compliance asks who deleted what last quarter.

WP-Sweep is one of the oldest and most trusted WordPress cleanup plugins, and its category-and-button workflow has saved countless sites from wp_postmeta bloat. The trade-off is opacity: site administrators see a count and a button, not the rows. On a five-year-old site with a hundred plugin installs and removals in its history, that opacity is the problem.

Editors want to know which orphan keys belong to which plugin before the sweep, performance engineers want repeatable measurements, and agencies want a playbook the whole team can follow. SleekView gives WP-Sweep a triage grid: rows, prefixes, counts, and saved views, plus an audit trail the team can hand to compliance. Sweeps still execute through WP-Sweep's own functions so safety nets stay in place.

The decision moves from a heroic admin clicking through to a reviewable queue, which is exactly the kind of operational maturity bigger WordPress sites need.