✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Elementor Extras: widgets and pages as tables

Elementor Extras adds extension widgets that live inside the Elementor JSON blob in postmeta. SleekView surfaces every page using an Extras widget as a queryable table for audits and bulk metadata edits.

♾️ Lifetime License available

SleekView table view for Elementor Extras

Every Elementor Extras page in one grid

Elementor Extras is an add-on for Elementor, so its widgets are stored inside the same _elementor_data JSON blob in wp_postmeta as core Elementor. There's no separate custom table, no separate post type. Auditing which pages use a particular Extras widget normally means opening each page in the editor and inspecting it, or running raw SQL against wp_postmeta.

SleekView reads wp_postmeta with a contains-text filter on _elementor_data for widget identifiers like extras-progress, extras-modal, or extras-image-comparison. That gives a real inventory of which pages use which Extras widget. Filter by author, last edited, and status to find drafts, stale layouts, or live pages that depend on Extras.

Inline edits to status, slug, and author write through the standard wp_update_post path so any other plugin hooks keep firing. The Elementor JSON layout stays untouched; only the post and postmeta fields around it change. CSV export of an audit slice gives an agency a clean deliverable showing exactly where Extras is used on a client site.

Workflow

From per-page inspection to one Extras inventory

1

Detect Extras-using posts

SleekView scans wp_postmeta for the _elementor_data key and applies a contains-text filter on Extras widget identifiers. Every Extras-touched page lands in one table.
2

Pick columns and widget filters

Add Title, Status, last edited, Author, URL, and a Widget column derived from the matched identifier. Save a filter chip per Extras widget you care about.
3

Save audit views

Pin views for stale Extras pages, drafts owned by former staff, and pages using widgets you plan to retire. Each view persists per user and per role.
4

Inline edit and export

Update post-level metadata inline. Export any filtered slice as a CSV deliverable for the client or for internal housekeeping records.

Sample columns

A typical Elementor Extras usage view

Pages that use one or more Elementor Extras widgets, with last edited and author visible.
Source: wp_posts + wp_postmeta (Extras widgets live inside the _elementor_data JSON blob)
Title Status Extras widget Last edited Author URL
Pricing comparison Published image-comparison May 02 Lena R. /pricing
Onboarding modal page Draft modal May 01 Mira S. /onboarding
2025 launch recap Published progress Apr 26 Den J. /launch-2025
Old promo banner page Trashed image-comparison Apr 11 Lena R. /promo

Comparison

Default Elementor Extras admin vs SleekView

Default Elementor Extras admin

  • No way to list pages by Extras widget usage from the WP admin
  • Default Elementor list mixes Extras pages with non-Extras pages in wp_posts
  • Last edited and author are not visible in the default Elementor list
  • Auditing widget usage requires opening each page or running SQL on _elementor_data
  • Bulk status or slug changes need plugin-specific bulk-edit screens

SleekView

  • Filter by widget identifier inside _elementor_data directly
  • Saved views for each Extras widget (modal, progress, image-comparison, particles)
  • Inline edit status, slug, and author on the row
  • Filter by last edited to surface stale or never-touched Extras pages
  • CSV export of any filtered usage slice for client deliverables

Features

What SleekView gives you for Elementor Extras

Widget-aware filters

Filter wp_postmeta by contains-text on the _elementor_data blob to find every page using a specific Extras widget. No SQL, no manual page-by-page inspection.

Audit-ready views

Saved views for stale Extras pages, drafts from former staff, or pages using deprecated Extras widgets you plan to retire. Each view persists per user.

Inline edits, layout untouched

Edit status, slug, and author inline. The Extras widget JSON inside _elementor_data stays exactly where Elementor expects it.

Audience

Who uses SleekView for Elementor Extras

Agencies

Audit client sites for which pages still depend on Elementor Extras and which widgets specifically. Per-client saved views turn handovers into a one-click report instead of a manual page sweep.

In-house editorial teams

Track which campaign pages use Extras widgets like progress bars or modals. Status and author filters replace the Trello board for live, draft, and scheduled pages.

Site owners

Spot Extras-powered pages that haven't been touched in months. The same grid drives quarterly housekeeping and pre-redesign inventories.

The bigger picture

Why Elementor Extras sites accumulate hidden dependencies

Elementor Extras is the kind of add-on that quietly ends up on dozens of pages over the course of a year. A modal here, a progress bar there, an image-comparison block on a landing page. None of those decisions are big at the time, but a few years in, an agency planning a redesign or a host migration needs to know exactly which pages still depend on the Extras widget set.

The default WordPress and Elementor admin screens cannot answer that question without opening every page. The Extras widget identifiers live inside the _elementor_data JSON blob in wp_postmeta, which means the data is there, just not surfaced. A queryable inventory turns the question into a saved view.

Filter to Extras-using pages, group by widget, sort by last edited, and the audit becomes a quarterly habit rather than a project. Agencies use the same grid for client handovers; in-house teams use it before retiring a deprecated widget or moving to a new builder. The cost of the audit drops to roughly the cost of opening the grid.

Questions

Common questions about SleekView for Elementor Extras

Inside the same _elementor_data JSON blob in wp_postmeta that core Elementor uses. There is no separate custom table. SleekView reads that postmeta value with contains-text filters to identify Extras-using pages.

 

Yes. A contains-text filter on _elementor_data for the widget identifier (for example extras-progress, extras-modal, extras-image-comparison) surfaces every page using that widget. Save the filter as a named view and reuse it.

 

No. The _elementor_data blob is read-only in the grid. Inline edits go through wp_update_post for post-level fields like status, slug, and author. The layout itself stays the Elementor editor's responsibility.

 

Yes. Both Free and Pro store layouts in the same postmeta key, and Extras widgets attach to either. SleekView reads them identically and shows widget usage regardless of which Elementor tier is active.

 

Every saved view exports to CSV with the columns currently on screen. Agencies use the export as a deliverable in client handovers, with Extras widget usage and last-edited dates per page.

 

Queries against wp_postmeta are paginated and limited, with the contains-text filter narrowing the set before columns are joined. A site with tens of thousands of posts can audit Extras usage in seconds, not minutes.

 

No. SleekView reads structural postmeta and post fields, not internal Extras APIs. Widget identifier strings have been stable across Extras versions, but you can adjust the filter to match new widget names if Extras renames anything.

 

The audit grid shows post-level metadata (title, status, author, dates). Authors are WordPress users whose names you already export via the standard WP user export. No personal data outside the WordPress user table is added.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView