✨ 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 Spectra Blocks: posts, pages, and block usage as tables

Spectra (formerly Ultimate Addons for Gutenberg) stores block markup in post_content as standard Gutenberg block comments. SleekView indexes that usage so every Spectra block becomes a filterable column.

♾️ Lifetime License available

SleekView table view for Spectra Blocks

Spectra block usage across the site

Spectra is the rebranded Ultimate Addons for Gutenberg, a Gutenberg-native block library covering Forms, Containers, Image Gallery, Post Grid, Tabs, and more. Block instances are stored as block markup inside post_content using comment delimiters like <!-- wp:uagb/forms --> (the namespace stayed uagb after the rename). Reusable blocks and templates live in standard WordPress CPTs.

SleekView reads post_content across pages, posts, and any public CPTs, indexes Spectra block usage by name, and surfaces each post with its block list as a filterable column. Filter to posts using uagb/forms to audit Spectra form coverage. Filter to posts using uagb/post-grid to find dynamic post lists across the site. Sort by last edited to spot recently touched pages.

Inline edits to status, slug, and author write through standard WordPress update calls. The Spectra block markup in post_content stays editable in the block editor. The grid handles the audit; the editor handles the content.

Workflow

From SQL on post_content to a block usage table

1

Index Spectra block usage

SleekView parses post_content for uagb/* block comments and indexes usage per post. Every page using a specific block becomes a queryable record.
2

Add audit columns

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

Save coverage views

Pin views for forms coverage, deprecated blocks, and post-grid usage. 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 Spectra block usage view

Posts grouped by the Spectra (uagb/*) blocks they contain.
Source: wp_posts (post_content with uagb/* block markup) + wp_postmeta + wp_block (reusable blocks)
Title Type Spectra blocks used Status Last edited Author
Landing page Q2 Page container, forms, post-grid Published Apr 24, 2026 Lena R.
Contact us Page forms, info-box Published Apr 18, 2026 Mira S.
Pricing rework Page tabs, container Draft Apr 22, 2026 Den J.
Old promo Page deprecated-slider Trashed Feb 14, 2026 Mira S.

Comparison

Default Spectra admin vs SleekView

Default Spectra admin

  • No way to filter posts by which Spectra block they contain
  • Forms coverage across the site is invisible from any list view
  • Finding pages with deprecated uagb/* block names needs SQL
  • Reusable block reference counts are not surfaced
  • Bulk status edits across pages using a specific block are manual

SleekView

  • Filter posts by Spectra block used in post_content
  • Saved views for forms coverage, deprecated blocks, or post-grid usage
  • Inline edit status and slug without opening the block editor
  • Reusable block reference counts as a filterable column
  • CSV export of any block usage slice for handovers

Features

What SleekView gives you for Spectra Blocks

Block usage as a filter

Find every page using uagb/forms, uagb/post-grid, or any Spectra block by parsing block comments in post_content. Coverage audits become a filter pass.

Deprecated block detection

Spot pages still using deprecated uagb/* block names before the next Spectra upgrade. The grid surfaces them with last-edited and author so cleanup gets owned.

Metadata edits

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

Audience

Who uses SleekView for Spectra Blocks

Agencies

Audit Spectra block coverage across client sites in one grid. Per-client saved views catch deprecated block usage before plugin upgrades cause render issues.

Development teams

Find every page using a specific Spectra block before refactoring or replacing it. Block-usage filters replace SQL on post_content for routine audits.

Site owners

Track which pages use Spectra Forms and which dynamic post lists exist across the site. Quarterly block audits prevent operational debt from compounding.

The bigger picture

Why Spectra sites accumulate block audit debt

Spectra positions itself as a Gutenberg-native block library with a deep set of layout, form, and dynamic-content blocks, which is why agencies and product teams adopt it for sites that need more than core blocks offer. The trade-off shows up at scale: uagb/* 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 Spectra 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. Reusable blocks orphan when their parent pages are deleted.

None of this is Spectra's fault, it's what happens when a flexible block library meets long-running content. A queryable block usage index changes audits fundamentally. Filter by block name to find every page using Spectra Forms.

Surface deprecated usage before the next upgrade. Prune unreferenced reusables. Agencies use this as a pre-upgrade audit; in-house teams use it as the block coverage documentation they finally have.

Questions

Common questions about SleekView for Spectra Blocks

Block instances are stored as Gutenberg block markup inside post_content using comment delimiters like <!-- wp:uagb/forms -->. The uagb/* namespace stayed after the Spectra rebrand. Reusable blocks live in the wp_block CPT. SleekView reads both directly.

 

No. Block content stays inside the WordPress block editor where Spectra's controls and design panel all work as designed. SleekView edits surrounding metadata (status, slug, author) and indexes block usage as a filterable column. The block markup itself never gets touched.

 

Spectra is the rebrand of Ultimate Addons for Gutenberg. The plugin kept the uagb block namespace for backward compatibility, so block markup in posts created before the rename still uses uagb/* and works without migration. SleekView filters on the live namespace.

 

Yes. SleekView indexes block comment usage in post_content so each post can be filtered by which Spectra blocks it contains. Find every page using uagb/forms or uagb/post-grid in one filter pass.

 

Yes. Reusable blocks in the wp_block CPT surface alongside posts with reference counts showing how many pages use each one. Reusables with reference count zero are easy to prune during a redesign or housekeeping pass.

 

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. As Spectra evolves, older block names get deprecated or replaced. The grid surfaces deprecated block usage as a saved view so the team can fix or remove those pages before a plugin upgrade breaks them. That audit takes one filter pass.

 

Yes. Every saved view exports to CSV with the visible columns including block usage list, status, and last edited. Agencies use forms-coverage and deprecated-block exports as recurring client deliverables; in-house teams use them as inputs to upgrade planning.

 

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