The Plus Addons extends Elementor, so its widgets live inside the standard _elementor_data JSON blob in wp_postmeta. The default WordPress admin cannot tell a Plus-using page apart from any other Elementor page, so a per-widget audit normally means opening each page in the editor or writing raw SQL.

SleekView reads wp_postmeta with contains-text filters on widget identifiers like tp-team-member, tp-flipbox, or tp-event-calendar. Pin saved views per widget. Filter by status, author, and last edited to surface drafts, stale layouts, and live pages depending on Plus.

Inline edits to post-level fields run through wp_update_post so other plugin hooks fire normally. The Plus widget JSON inside _elementor_data stays untouched. CSV export of any filtered slice provides a clean deliverable for clients or internal records.

The Plus Addons ships a deep catalogue of Elementor widgets, and most sites that use it accumulate dozens of pages relying on a small set of those widgets. None of that matters until a redesign, a builder review, or a license renewal forces the question of which pages actually depend on Plus widgets. The default Elementor admin cannot answer that question because Plus-using pages look like ordinary Elementor pages in wp_posts.

The data lives inside _elementor_data in wp_postmeta, but it is invisible from any default screen. A queryable inventory turns the audit into a saved view. Filter to Plus-using pages, group by widget identifier, sort by last edited.

The pages that need attention before retiring a widget or moving to another builder become obvious. Agencies use the grid for client handover reports; in-house teams use it to plan widget retirements ahead of a Plus license decision.