WP Schema Pro (Brainstorm Force's plugin, sometimes shipped as Schema Pro or AIO Schema) stores its rules as the aiosrs-schema custom post type. Each rule carries a schema type, target locations, and a set of field mappings between schema properties and source fields. The field mappings live in wp_postmeta under keys prefixed by bsf-aiosrs-.

The default WP Schema Pro screen lists rules with a few columns and no way to compare field mappings across rules. Auditing whether two Article rules use the same author mapping, or whether a Product rule still points at a renamed custom field, requires opening rules one by one. SleekView reads wp_posts and wp_postmeta together and exposes type, targets, and mapping count as sortable columns.

Inline edits to field mappings write back to the same bsf-aiosrs-* postmeta keys the plugin reads at render time, so the JSON-LD output picks up the change on the next page load without any extra steps.

WP Schema Pro is a powerful rule engine: SEO leads can map any schema type to any post type, then point individual schema properties at custom fields, taxonomies, or static values. The default admin presents that catalogue as a flat list with few columns, so the picture of which types cover which content (and which rules quietly reference renamed fields) only emerges after a manual sweep. SleekView reads aiosrs-schema with bsf-aiosrs-* postmeta and exposes type, targets, mapping count, and status as sortable columns.

Filter to active rules to audit live coverage. Filter to draft and disabled rules to clean up the catalogue. Inline edit mappings to keep JSON-LD aligned with the current custom-field schema.

Technical SEO leads catch broken references before they show up in Search Console. Agency leads export the catalogue per client. WP Schema Pro still renders the JSON-LD; SleekView turns the rule catalogue into something operable.