Schema Pro stores its rules as a custom post type, typically aiosrs-schema, where each rule carries a schema type (Article, Product, FAQPage, Service, Review, Event, JobPosting, LocalBusiness, and more) and a set of target locations. Field mappings between schema properties and source fields live in bsf-aiosrs-* postmeta keys on the rule, and per-post overrides live on each target post's postmeta.

The default Schema Pro admin lists rules in a CPT screen with limited columns. Seeing which schema types cover which post types, or which rules carry the same field mapping, requires opening rules individually. SleekView reads from wp_posts and wp_postmeta together to expose every rule's type, target, and field mapping as sortable columns.

Inline edits to field mappings write back to the same bsf-aiosrs-* keys that Schema Pro reads at render time. The plugin still produces the JSON-LD output, so head-tag changes appear on the next page load.

Schema Pro lets SEO leads cover dozens of schema types through a rule system, which is exactly the right tool for a site that needs Article, Product, FAQPage, Service, Event, Review, and LocalBusiness markup in different places. The default admin lists those rules in a CPT screen with a handful of columns, so seeing the full catalogue across types or comparing field mappings between two rules of the same type takes a manual sweep. SleekView reads aiosrs-schema together with the bsf-aiosrs-* postmeta and exposes every rule's type, targets, field mapping count, and status as sortable columns.

Filter to active Article rules to spot duplicates. Filter to draft rules to clean them up. Inline-edit field mappings without opening each rule.

Technical SEO leads catch inconsistencies between rules of the same type. Agency leads export the catalogue per client for monthly reports. Schema Pro still renders the JSON-LD; SleekView just makes the catalogue legible.