✨ 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 Schema Pro

SleekView joins the aiosrs-schema custom post type to the bsf-aiosrs-* postmeta on every matched post and renders one row per rule with schema type, match target, matched posts and rule status ready to sort and filter.

♾️ Lifetime License available

SleekView table view for Schema Pro

Schema Pro applies rules, the table reads the matches

Schema Pro stores each schema rule as an aiosrs-schema custom post type entry. The rule conditions (post type, taxonomy term, URL pattern) and the target schema type live in postmeta on the rule. The actual per-post schema field values (review rating, recipe cook time, course provider, product price) live as bsf-aiosrs-* postmeta keys on every post the rule matches.

The default Schema Pro admin lists rules and lets the SEO lead edit one at a time. There is no per-rule overview that answers questions like how many posts get Article schema, which rules overlap on the same post type and cause conflicts, what percentage of products have a populated price field, or how Schema Pro coverage has grown alongside content velocity over the last year. SleekView reads the aiosrs-schema CPT and the bsf-aiosrs postmeta and turns every rule into a row in a sortable, filterable coverage grid.

Schema Pro keeps owning rule evaluation, schema generation and the per-post field UI. SleekView is a read-and-write layer on top of the same CPT and postmeta, so the rule engine continues exactly as Schema Pro runs it.

Workflow

How SleekView surfaces Schema Pro data

1

Point at the rules and assignments

Register the aiosrs-schema CPT joined to the bsf-aiosrs postmeta on every matched post as a SleekView data source. Each rule becomes one row with the matched-post count expanded.
2

Compose the columns

Drag in Rule name, Schema type, Match target, Matched posts, Status and Rule created columns. Reorder, hide and rename per saved view.
3

Filter and sort like a database

Filter to rules with zero matched posts, sort by matched-post count, or scope to one match target to spot rules that overlap on the same post type.
4

Save and gate the view

Name the view (Rule coverage, Schema mix, Field completeness) and gate it by role so SEO leads, consultants and editors see only the slice the admin allows.

Sample columns

A typical Schema Pro rule coverage view

Schema Pro rules joined to the per-post bsf-aiosrs postmeta on every matched post, rendered as a sortable rule coverage grid.
Source: wp_319_posts (aiosrs-schema) + wp_319_postmeta (bsf-aiosrs-*)
Rule name Schema type Match target Matched posts Status Created
Blog post Article schema Article post_type: post 1,184 active 2024-02-12
Shop Product schema Product post_type: product 842 active 2024-04-08
Recipes RecipeSchema Recipe taxonomy: category=recipes 146 overlap 2025-01-22
Legacy review schema Review url: /reviews/* 0 no matches 2023-09-05
Course schema for academy Course post_type: course 38 active 2026-02-14

Comparison

Default Schema Pro admin vs SleekView

Default Schema Pro admin

  • Rules list shows name and type but no matched-post count as a sortable column
  • Per-post schema fields live in the post editor meta box, one record at a time
  • No filter for rules with zero matched posts or overlapping rules on the same post type
  • No bulk action across the bsf-aiosrs postmeta keys
  • No saved views per role for SEO leads, consultants or editors

SleekView

  • Every Schema Pro rule rendered as a row with matched-post count and match-target columns
  • Filter to zero-match rules or overlapping rules in one click
  • Inline edits to schema-field postmeta on matched posts from the same screen
  • Saved views per role: SEO lead, agency consultant, editor or merchandiser
  • Same dataset the chart view reads, so table and dashboard stay in sync

Features

What SleekView gives you for Schema Pro

Rules and assignments as real columns

Rule name, schema type, match target, matched-post count, status and created date rendered directly from the aiosrs-schema CPT joined to bsf-aiosrs postmeta.

Real sort, filter and inline edit

Sort by matched-post count, filter to overlapping rules on the same post type, and inline-edit the schema-field postmeta on matched posts without opening every record.

Role-scoped saved views

Save views per role and embed them on frontend audit pages so consultants share schema coverage with clients without WP admin access.

Audience

Who uses SleekView for Schema Pro

SEO leads

Pin a saved view scoped to active rules and confirm Schema Pro is keeping up with content velocity instead of leaving new post types without structured data.

Agency consultants

Audit a client install in one grid pass, surface rules that overlap on the same post type and produce a measurable retainer review of schema coverage.

Editors and merchandisers

Filter to one product type or category and check whether every matched post has the schema field values the rule needs populated.

The bigger picture

Rules are records, not a flat list

Schema Pro takes the right architectural decision: instead of dropping schema on individual posts one at a time, it defines rules that apply schema to whole post types, taxonomies or URL patterns. That model scales much better, but it also makes coverage invisible. An SEO lead cannot tell from the rules list whether 1,184 articles all get Article schema, whether two rules overlap on the same post type, whether new post types added last quarter still fall outside any rule or whether the schema field values rules expect are actually populated across the matched posts.

SleekView treats the aiosrs-schema CPT and the bsf-aiosrs postmeta as the structured records they already are. Rules become rows with matched-post counts, match-target and status columns, sortable and filterable, with inline edits flowing through the same Schema Pro write path. The plugin keeps owning the rule engine; SleekView adds the coverage surface a rules list on its own cannot offer.

Questions

Common questions about SleekView for Schema Pro

No. Schema Pro still owns rule evaluation, schema generation and the per-post field UI. SleekView reads the same aiosrs-schema CPT and bsf-aiosrs postmeta as a sortable table and inline edits use the same write path the plugin itself uses, so the JSON-LD on the front end stays exactly as Schema Pro emits it.

 

Schema Pro is sold by Brainstorm Force as a paid plugin (often bundled with Astra Pro and other Brainstorm products). SleekView reads the data the plugin writes regardless of license bundle, as long as the plugin is installed and active.

 

Yes. Filter the rules grid to one match target (for example post_type: post) and sort by matched-post count. Any target with more than one rule is a candidate for overlap, which SEO leads can investigate inline without opening every rule editor.

 

Yes. The per-post bsf-aiosrs-* postmeta keys store the schema field values. Add a derived completeness column on the matched-posts grid that flags rows missing the fields the rule needs, then filter to the missing rows for a cleanup pass.

 

Yes. Schema Pro is independent of theme and page builder, and so is SleekView. The grid reads the same rule and postmeta data on any setup, including Astra Pro themes, Spectra block content and any other front-end stack Schema Pro sits behind.

 

Yes. Open the matched-posts grid for a rule and click the relevant bsf-aiosrs-* cell to update the value. SleekView writes back to the same postmeta key Schema Pro reads on render, so the JSON-LD reflects the change with no additional step.

 

No. Queries hit indexed postmeta keys and the underlying rules and posts tables paginate. Sites with hundreds of rules and tens of thousands of matched posts stay responsive because only the visible page of the underlying table is fetched.

 

Yes. Any saved view exports to CSV with the current filters and columns applied. Consultants typically export the overlapping-rules list as a deliverable for the developer team and the missing-fields list as a brief for the SEO copywriter.

 

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