✨ 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 Bricks Builder: pages and templates as tables

Bricks stores layouts in wp_postmeta under the _bricks_page_content_2 key and uses the bricks_template custom post type for reusable headers, footers, sections, and singles. SleekView surfaces every Bricks-touched post in one sortable grid for audits and housekeeping.

♾️ Lifetime License available

SleekView table view for Bricks Builder Pro

Every Bricks page in one place

Bricks saves builder data in postmeta under _bricks_page_content_2 on the page or template it belongs to, plus _bricks_editor_mode and template-condition keys. Reusable templates use the bricks_template custom post type with their own metadata for type (header, footer, section, single, archive, popup, error). The default WordPress admin treats those as ordinary posts and templates split across separate screens.

SleekView reads every post that has _bricks_page_content_2 in postmeta plus the entire bricks_template CPT and joins them into one queryable table. Filter to Bricks-built pages only. Filter by template type to find every header, every footer, every popup, or every archive template. Sort by last edited descending to spot active campaign pages or ascending to surface stale layouts untouched in over a year.

Inline edits to status, slug, and author write through standard WordPress update calls. The Bricks layout array under _bricks_page_content_2 isn't touched (that's the Bricks visual editor's job) but the surrounding metadata is fair game for housekeeping. CSV export of an audit slice gives an agency a clean inventory of every Bricks page on the client site with last-edited dates and authors.

Workflow

From scattered screens to one Bricks inventory

1

Detect Bricks-built posts

SleekView scans for posts with the _bricks_page_content_2 postmeta key plus the bricks_template CPT, surfacing every Bricks-touched record in one table.
2

Add type and audit columns

Pull template type, last edited, author, and URL into proper columns. Header, footer, section, single, archive, and popup all show as filter chips.
3

Save audit views

Pin views for stale pages, drafts owned by former staff, and templates with no live target condition. Each view persists per user.
4

Inline-edit metadata

Update status, slug, and author in the row for housekeeping. The Bricks layout array stays inside the visual editor.

Sample columns

A typical Bricks Builder pages view

Pages and templates built with Bricks across the site, with last edited and template type visible.
Source: wp_posts (post_type=page,post,bricks_template) + wp_postmeta (_bricks_page_content_2)
Title Status Type Last edited Author URL
Homepage 2026 Published Page Apr 24 Lena R. /
Pricing redesign Draft Page Apr 22 Mira S. /pricing
Site header Published Header template Apr 18 Den J. n/a
Old promo Trashed Popup template Apr 11 Lena R. /promo

Comparison

Default Bricks Builder admin vs SleekView

Default Bricks Builder admin

  • Pages and the bricks_template CPT live on different admin screens
  • No filter to isolate Bricks-built pages from non-Bricks pages
  • Last edited and author columns are absent in the default page list
  • Bulk status changes across templates are clunky
  • Finding orphan or stale templates needs SQL queries

SleekView

  • All Bricks pages plus the bricks_template CPT in one table
  • Saved views for drafts, stale pages, or specific template types
  • Inline edit status, slug, and author per row
  • Filter by template type, author, or last edited
  • CSV export of the audit slice for client handovers

Features

What SleekView gives you for Bricks Builder Pro

Pages and templates together

Every Bricks-built page plus headers, footers, popups, and singles in one place. Type filters scope the grid to exactly the slice an audit needs.

Audit filters

Find pages last edited over six months ago, drafts owned by former staff, or templates without a live target. Each audit becomes a saved view, not a SQL query.

Inline edits

Update status, slug, and author without opening the Bricks editor for housekeeping tasks. The _bricks_page_content_2 array stays untouched.

Audience

Who uses SleekView for Bricks Builder

Agencies

Audit client Bricks sites for stale pages, orphan templates, and abandoned drafts. Per-client saved views keep handovers clean and reports consistent.

In-house teams

Track which Bricks-built pages are live, drafted, or scheduled across the marketing site. Author and status filters replace the editorial spreadsheet.

Site owners

Spot which template types are accumulating cruft (old popups, archived headers, retired singles) and prune them as part of quarterly housekeeping.

The bigger picture

Why Bricks sites accumulate operational debt

Bricks Builder has grown rapidly in the WordPress space and most production Bricks sites have been running through multiple redesigns. Each redesign leaves pages and templates behind: the old launch page, the seasonal popup, the abandoned archive layout. The default WordPress admin lists those as ordinary posts and templates split across separate screens with no indication of which were built in Bricks or when they were last touched in the editor.

Stale layouts pile up quietly. Templates with conditions pointing to deleted content go unnoticed. Drafts owned by former staff sit in the database indefinitely.

None of this is Bricks' fault, it's the operational debt any high-volume builder accumulates without an audit surface. A queryable inventory changes the cost of an audit from a multi-day project to a half-hour pass through the grid. Filter to stale pages and review them in batches.

Find every header template at once and confirm which one is actually live. Spot popup templates targeting pages that no longer exist. Agencies running Bricks across dozens of client sites use this kind of audit as a routine handover deliverable; in-house teams use it as quarterly housekeeping.

Questions

Common questions about SleekView for Bricks Builder Pro

In wp_postmeta under the _bricks_page_content_2 key on each page, post, or template. Templates also use the bricks_template custom post type with their own metadata for type and conditions. SleekView reads both directly so every Bricks-touched post shows in the audit grid.

 

No. SleekView shows the metadata around layouts. The _bricks_page_content_2 array is still edited inside the Bricks visual editor, where the canvas, element settings, and class-based styling all live. The grid handles status, slug, and author.

 

Yes. Header, footer, section, single, archive, popup, and error templates all show as filterable values on the bricks_template CPT. Pin a saved view per template type to audit coverage without scrolling the mixed list.

 

Yes. Template conditions are stored in postmeta on each template, so they show as a column in the grid. You can audit which conditions target which URLs or post types and find templates whose conditions point to content that no longer exists.

 

Yes. Every saved view exports to CSV with visible columns. Agencies often export the stale-pages view as a deliverable in client handovers, with last-edited dates and authors visible so the client knows exactly which pages need a decision.

 

Yes. SleekView is read-mostly. Inline edits use the standard WordPress update path, so any Bricks or other-plugin hooks fire normally. The grid never touches the _bricks_page_content_2 array, which keeps the visual editor as the only source of truth for layout content.

 

The _bricks_page_content_2 array is JSON-encoded, so a contains-text filter on the postmeta value can surface pages using a specific element name. That kind of audit catches pages still using a deprecated custom element or a third-party Bricks add-on you're about to remove.

 

Bricks uses standard WordPress post revisions, so each saved revision is a revision row SleekView can surface in a separate view. The main grid focuses on the live posts and templates so audit slices stay clean.

 

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