SleekView reads post_modified and post_date on wp_posts, plus the optional _lmt_disable postmeta key. These are the same fields WP Last Modified Info uses on the front end, so the dashboard exactly matches what visitors see on the rendered last-updated label.

No. The shortcode and template tag from WP Last Modified Info still produce the same front-end string. SleekView only reads from wp_posts and wp_postmeta. The display formatting, the per-post opt-out, and the schema tweaks all stay inside the plugin.

Yes if the data source joins wp_postmeta on _lmt_disable and filters out opted-out posts. Without the join, the dashboard counts every published post regardless of whether the front end actually shows a last-updated date for it.

Yes. The donut bucketing is built from a computed column on post_modified. Bucket boundaries at 30, 90, 180, and 365 days are typical, but the team can switch to 60 and 120 if quarterly refresh cycles are the goal.

Cards filter wp_posts.post_status to publish by default, so scheduled and draft posts do not skew the freshness KPI. A separate view can include scheduled posts when editorial wants to plan upcoming refresh content alongside live freshness debt.

Only if post_modified itself is changed. WordPress only updates post_modified when content is edited, so simply marking a post as sticky does not freshen it for the dashboard. This is intentional: the chart tracks real editorial work, not metadata changes.

Yes. A join to wp_term_relationships and wp_term_taxonomy adds category as a chart dimension. The freshness donut can be filtered or duplicated per category so each editorial lead reads their own slice without affecting the corpus-wide KPI.

Third-party tools cross-reference rankings with last-updated dates. SleekView is just the WordPress side of that question: how much of the catalog is overdue. Combining the chart KPI with a search-console export still produces the best refresh priority list, but the SleekView read-out alone already drives most of the editorial calendar.