Kadence Blocks Pro extends the WordPress block editor with a Pro library of advanced blocks (Advanced Form, Posts, Slider, Tabs, Conditional Visibility). Block instances are stored as Gutenberg block markup inside post_content using comment delimiters like <!-- wp:kadence/advancedheading -->. Patterns and reusable blocks live in their own custom post types. The default WordPress admin lists posts but offers no way to filter by which Kadence block they use.

SleekView reads post_content across pages, posts, and any other public CPTs, then indexes Kadence block usage so each post can be filtered by block name. Filter to posts using the Advanced Form block to audit form coverage. Filter to posts using Conditional Visibility to find content with role-gated sections. Sort by last edited to find recently changed pages that use a specific Pro block.

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 it belongs. Audit, don't refactor, the markup itself.

Kadence Blocks Pro extends the Gutenberg editor with a deep library of Pro blocks, which is exactly why product teams and agencies adopt it for content-heavy sites. The trade-off shows up at scale: Pro block usage accumulates across years of pages, with no admin surface to filter posts by which block they contain. Default WordPress admin lists posts and pages with no awareness of the Kadence blocks inside.

A page using a deprecated block name keeps rendering until the plugin upgrades and breaks it. Forms coverage across the site is invisible until someone audits page by page. Conditional Visibility blocks gate content for roles that may no longer exist.

None of this is Kadence's fault, it's the operational debt of a flexible block library meeting long-running content. A queryable block usage index changes the cost of audits fundamentally. Filter by block name to find every page using Advanced Form.

Surface deprecated block usage before the next plugin upgrade. Spot Conditional Visibility blocks targeting removed roles. Agencies use this as a pre-upgrade audit deliverable; in-house teams use it as the documentation they finally have, of which page uses which block.