✨ 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 GenerateBlocks Pro: pages, global styles, and block usage as tables

GenerateBlocks Pro stores its block markup in post_content with the generateblocks/* namespace, plus global styles in a custom post type. SleekView surfaces both in one filterable audit grid.

♾️ Lifetime License available

SleekView table view for GenerateBlocks Pro

Block usage and global styles in one inventory

GenerateBlocks is a lightweight, performance-focused block library, with GenerateBlocks Pro adding advanced layout blocks, dynamic data, and a global styles system. Block instances live as Gutenberg block markup inside post_content using the generateblocks/* namespace. Global styles are stored as a custom post type (typically generateblocks_styles) referenced by class name from block markup.

SleekView reads post_content across pages, posts, and any public CPTs, indexes GenerateBlocks block usage, and joins it with the global styles CPT. Filter to posts using a specific GenerateBlocks Pro block to audit coverage. Filter global styles by reference count to find styles no block uses. Sort by last edited to spot stale pages that still reference legacy class names.

Inline edits to status, slug, and author write through standard WordPress update calls. The block markup in post_content stays editable in the block editor where the GenerateBlocks controls live. Global styles stay editable in the GenerateBlocks Styles admin.

Workflow

From scattered styles to a GenerateBlocks audit table

1

Index block and style usage

SleekView parses post_content for generateblocks/* block comments and joins the styles CPT by class name reference. Both sources land in one queryable view.
2

Add audit columns

Block usage list, referenced styles, last edited, author, and status become first-class columns. Filter chips replace ad-hoc SQL on post_content.
3

Save audit views

Pin views for orphan styles, deprecated block usage, and Pro block coverage. Each audit becomes a one-click slice instead of a custom database query.
4

Inline-edit metadata

Update status, slug, or author from the row. Block markup stays untouched; the block editor remains the source of truth for block content.

Sample columns

A typical GenerateBlocks usage view

Posts and global styles, with generateblocks/* usage and style references.
Source: wp_posts (post_content with generateblocks/* markup, post_type=generateblocks_styles) + wp_postmeta
Title Type GenerateBlocks used Styles referenced Status Last edited
Spring landing Page container, headline, button primary-button, hero-container Published Apr 24, 2026
Pricing rework Page grid, container card-base Draft Apr 22, 2026
About Page container, headline none Published Apr 18, 2026
Old promo Page deprecated-button legacy-cta Trashed Feb 3, 2026

Comparison

Default GenerateBlocks admin vs SleekView

Default GenerateBlocks admin

  • No way to filter posts by which GenerateBlocks block they use
  • Global styles reference counts are not visible in the styles list
  • Pages referencing deleted global styles aren't surfaced
  • Bulk status edits across pages using specific blocks are manual
  • Pattern usage across the site has no admin surface

SleekView

  • Filter posts by GenerateBlocks block and referenced global style
  • Saved views for Pro block usage, orphan styles, or stale pages
  • Inline edit status, slug, and author on posts and styles
  • Global style reference counts as a filterable column
  • CSV export of any audit slice

Features

What SleekView gives you for GenerateBlocks Pro

Block and style as filters

Find every page using a specific GenerateBlocks block or referencing a specific global style. Coverage audits and refactor planning become filter passes instead of grep.

Orphan styles detection

Surface global styles with reference count zero so unused entries get pruned. Identify pages referencing deleted styles and fix them before the front-end CSS breaks.

Metadata edits

Update status, slug, and author from the row for housekeeping. Block markup in post_content stays untouched and editable in the block editor where the GenerateBlocks controls live.

Audience

Who uses SleekView for GenerateBlocks Pro

Agencies

Audit GenerateBlocks coverage and global styles usage across client sites. Per-client saved views catch orphan styles and deprecated block usage before they cause issues.

Development teams

Find every page using a specific GenerateBlocks block or global style before refactoring. Block-usage filters replace SQL on post_content for routine audits.

Site owners

Prune orphan global styles and find stale pages that reference deleted styles. Quarterly housekeeping prevents the operational debt of long-running performance-focused sites.

The bigger picture

Why performance-focused GenerateBlocks sites still need audits

GenerateBlocks is the block library teams choose when performance and clean markup matter, with GenerateBlocks Pro layering global styles and dynamic data on top. That technical discipline produces sites that perform well on the front end but face the same operational audit debt as any long-running WordPress site. Global styles accumulate across years of design decisions, with no admin surface to show which styles are still referenced by live block markup.

Pages referencing deleted styles fail silently in the CSS. Deprecated GenerateBlocks block names linger in post_content until the next plugin upgrade surfaces them. Pattern usage across the site is invisible from any list view.

None of this is GenerateBlocks's fault, it's the operational debt that performance-focused tools accumulate just like any other. A queryable index changes the audit cost fundamentally. Surface orphan global styles in one filter.

Find pages referencing deleted styles before they break the front end. Spot deprecated block usage before the next upgrade. Agencies running GenerateBlocks across performance-focused client sites use this as a recurring audit deliverable; in-house teams use it as the housekeeping pass they finally have time to run.

Questions

Common questions about SleekView for GenerateBlocks Pro

Block instances are stored as Gutenberg block markup inside post_content using the generateblocks/* namespace. Global styles live in a custom post type (typically generateblocks_styles) referenced by class name from block markup. SleekView reads both directly to build the audit grid.

 

No. Block content stays inside the WordPress block editor where the GenerateBlocks controls and design panel work as designed. Global styles stay editable in the GenerateBlocks Styles admin. SleekView edits surrounding metadata (status, slug, author) and indexes block and style usage as filterable columns.

 

Yes. SleekView indexes block comment usage in post_content so each post can be filtered by which GenerateBlocks blocks it contains. Find every page using generateblocks/container or generateblocks/headline in one filter pass.

 

Yes. SleekView joins global styles to block markup references and surfaces styles with reference count zero as a filterable column. Orphan styles inflate the styles admin and confuse the next person who opens it. Pruning them is a high-value, low-risk audit task.

 

Yes. The grid surfaces pages whose block markup references a global style class name that no longer exists in the styles CPT. That audit prevents broken front-end CSS that would otherwise only surface when someone visits the affected page.

 

Yes. Free GenerateBlocks and Pro both store block markup the same way (generateblocks/* namespace in post_content). The global styles system is a Pro feature, so the styles audit views require Pro to be active. Free-only sites still get the block usage audit.

 

Yes. SleekView is read-mostly and inline edits use standard WordPress update calls. Block markup in post_content is never touched, which means the block editor and the front-end render behave exactly as before. Any plugin hooks on metadata changes still fire normally.

 

Yes. Every saved view exports to CSV with the visible columns including block usage list, style references, status, and last edited. Agencies use orphan-styles and deprecated-block exports as recurring client deliverables.

 

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