This page is for Visual Composer Website Builder from visualcomposer.com, the modern frontend editor. WPBakery Page Builder, despite the shared history, is a different product with its own meta keys and has a separate SleekView page. SleekView detects each by the marker the respective plugin saves on a page.

It checks for the vcv-source-id postmeta key, which Visual Composer writes on every saved page, plus the custom post types VC registers for templates and theme builder parts. Pages without that marker stay in their normal lists, so the table never mixes a plain WordPress page with a VC layout.

No. Layout structure, columns, widgets and design controls all stay in Visual Composer where they belong. SleekView edits the metadata around the page: title, slug, parent, status, menu order. A one-click action opens the row in the Visual Composer editor when an actual layout change is needed.

Yes. The Visual Composer template each page uses is exposed as a sortable, filterable column. The values match exactly what you see in the editor template picker, so VC Default, VC Landing and any custom templates registered through the Hub appear with the same labels.

No. SleekView virtualises rows, so a thousand-page Visual Composer install renders as quickly as a hundred-page one. Sorting and filtering happen against indexed columns, and the SQL it generates is closer to a wp_query than a slow generic table scan.

Yes. Multi-select rows from any filtered view and trash them in one action. The same capability checks the default admin uses are applied, so editors without delete_pages still get a permission prompt and the trashed items remain recoverable from the WordPress trash.

Yes. Visual Composer registers separate post types for headers, footers and theme builder layouts, and SleekView surfaces them as their own tab in the same view. You can audit a header used across the site and a campaign landing page from one screen without switching admin pages.

Yes. Each role can save its own default filters, so a marketer only sees pages with VC Landing template while an editor opens a view filtered to drafts. Views are stored per-user, so saved layouts do not leak between teams or accidentally override another editor's working set.