Schema App stores per-URL JSON-LD output and Highlighter selections in wp_postmeta under keys like schema_app_json_ld, schema_app_highlights, and the entity-type fields the plugin syncs back from the cloud. A separate cache table holds the cloud-side entity graph and any reference IDs. The WordPress admin surfaces a list of synced URLs and a per-post sidebar; the corpus view lives behind the Schema App dashboard at app.schemaapp.com.

That separation costs editors context. The post editor confirms one URL has schema; the cloud dashboard confirms the corpus has graph coverage. Neither answers "how many posts published this quarter are still missing entity markup" or "which entity types dominate our graph today" without flipping screens.

SleekView Charts pulls the schema_app postmeta and the local cache table into a single canvas. A Number for posts without JSON-LD, a Pie of entity types from schema_app_entity_type, a Bar of entity coverage per post_type, and an Area of schema_app_json_ld updates per week. The Highlighter still drives the JSON-LD generation. SleekView just renders the result in the same admin where editors already work.

Schema App already stores per-URL entity JSON-LD as postmeta in WordPress, but the corpus-level view lives in the Schema App cloud. That works for SEO leads who live in app.schemaapp.com all day. It does not work for editors who only open WP Admin and never see how the entity graph is shaped.

SleekView Charts reads the same schema_app postmeta and the local sync cache, then renders four cards inside WP Admin that answer the corpus questions in one glance. The data is already correct because Schema App wrote it. Charts just gives the team a dashboard to look at it without leaving WordPress.

The entity graph stops being a separate tool and becomes a panel editors actually see.