GraphComment is a hosted commenting platform that replaces the native WordPress comment system with an embedded widget. Conversation threads live in GraphComment's cloud, which is the right place for them. What WordPress owns is the embed configuration: which posts and post types render the widget, when the integration was enabled per post and the bridge options the plugin stores. That coverage layer is what editors, migration leads and site ops actually need an audit surface for.

SleekView reads wp_posts joined to wp_postmeta on graphcomment_enabled and any related graphcomment_* keys, and renders the dataset as a configurable table. Filter to posts with the embed disabled in the last 30 days to spot rollout drift, scope by post type to verify which CPTs are in scope, or sort by post_date to confirm the migration window held. Saved per-role views give migration leads a rollout grid, editors an authoring audit and site ops a post-type coverage check.

Scope stays honest. SleekView does not mirror conversation threads, votes or moderation actions, all of which live in GraphComment and would only rot if duplicated. It surfaces the WordPress half of the integration as a row-level audit table.

GraphComment moves comment threads to a hosted platform, which is the right call for sites that want a managed conversation layer. The trade-off is that WordPress no longer owns the conversation data, only the embed configuration. The shape of the audit matters precisely because of that: a per-post grid of post_id, post_type, author, embed flag and enablement date shows whether the rollout is sticking, where it skipped post types and which authors quietly drop the toggle.

Same plugin meta, same embed flag, completely different posture toward the rollout. The table renders the WordPress half of the integration as a row-level audit, which is the difference between assuming GraphComment is everywhere and proving it.