Revive Old Posts cycles older content back through social networks on a configurable schedule, which keeps evergreen content earning distribution long after publication. The plugin writes a share-log table and a per-network queue alongside post-level meta keys for next-share time and share-count history. The default Logs panel shows recent shares as a list and the queue as a calendar; cross-cutting questions about which posts have been re-shared which number of times to which networks live as ad-hoc SQL.

SleekView reads the share-log table and the queue table together and pivots them into a queryable surface. One view shows post-level history (Source post, Times shared, Last shared, Next scheduled, Networks). Another view shows the dispatch log (Source post, Network, Shared-at, Status, Result). Editorial gets the post-level rotation cadence; ops gets the per-dispatch failure triage; both surfaces read the same plugin tables.

The Times shared column is the editorial signal that the default UI mostly hides. A post that has been re-shared 18 times is hitting diminishing returns on social distribution; a post that has been re-shared 0 times is leaving evergreen value on the table. Sort the post-level view by Times shared and both ends of the rotation become obvious in one screen, which is exactly what an evergreen-content strategy needs.

Evergreen-content strategy lives or dies on rotation cadence. A post that gets re-shared every other week to four networks earns ten times the distribution of one published once and forgotten, but only if the rotation actually runs and only if editorial can see what is rotating, what is over-rotating, and what is excluded. Revive Old Posts handles the dispatching well; the visibility into the rotation, the share log, and the per-post cadence is left as flat lists and calendar views that do not answer the editorial questions cleanly.

Which posts have been over-rotated and need rest, which evergreen posts have never been re-shared, which exclusions were intentional and which were accidents from a bulk-edit a year ago. SleekView reads the share log and queue tables and pivots them into per-post and per-dispatch grids: rotation cadence in one view, dispatch failure triage in the other, the same plugin data feeding both. Editorial gets a rotation strategy surface, ops gets a failure triage queue, and the rotation that drives long-tail distribution becomes a verifiable, exportable system rather than a cron job people hope is running.