GrowthBar's AI outline generation and keyword research live in its app. Its WordPress integration writes a small meta trail on each connected post: an outline id, a target keyword and the word count target the writer was working against. The Posts screen does not surface any of it. GrowthBar's own dashboard reports app usage, not WordPress lifecycle.

SleekView Charts reads the same wp_postmeta keys. A Number card counts published posts connected to a GrowthBar outline. A Pie groups them by primary topic or keyword cluster. A Bar shows posts per target keyword. An Area trends posts per publish month so editorial leads have a measurable cadence number, not a sense of volume.

The scope is honest: GrowthBar's keyword research, SERP analysis and outline generation stay in GrowthBar. SleekView reports on the slice the WordPress integration writes, plus the lifecycle of the resulting posts inside the CMS.

Generating an outline is an input, not an outcome. The outcome is a published post that hits its target word count, sits in a sensible cluster and contributes to a steady cadence. None of that is visible from GrowthBar's app, because the work has long since left the app by the time it ships.

None of it is visible from the WordPress Posts screen either, because the standard admin treats outline-id and target-keyword meta as invisible. SleekView Charts reads the meta the connector writes and surfaces the outcome metrics editorial leads actually care about: cadence, coverage, word count fidelity. The result is an outline tool that reports against its real job rather than against its own activity log.