LuckyWP Table of Contents inserts a TOC automatically on enabled post types when a post passes the heading threshold, and offers a shortcode plus a Gutenberg block for manual placement. Configuration lives in the lwptoc_options row in wp_options, and per-post overrides land in postmeta as lwptoc_disable_auto and related keys. Readers see a TOC; the editorial team has no aggregate view of where it actually appears.

SleekView Charts reads the same options row and the per-post meta, plus a parsed heading index of post_content. A Number card counts posts where the auto-insert will fire given the current threshold. A Pie splits posts across auto-rendered, manual via shortcode/block, below threshold and disabled by override. A Bar groups TOC posts by post_type. An Area trends post_modified to expose whether long-form content with a TOC is being maintained.

Because the dataset is built from standard WordPress storage, no extra tables are needed. Filters span the audit table and the chart cards on one dataset, and saved views gate by WordPress capability.

Auto-insert is the LuckyWP feature most editors love and most SEO leads forget about. The plugin quietly drops a TOC into long posts on enabled post types, the editor never thinks about it, and the assumption is that coverage just works. The trade-off is that the assumption is the thing that breaks first.

A heading threshold creeps up after a settings change, a rewrite drops a key H2, a per-post override gets clicked during a freelance edit, and a hundred posts silently stop carrying a TOC. SleekView Charts reads the same options, the same per-post meta and the same heading structure and turns coverage into a dashboard. A KPI for posts rendering a TOC, a pie for source mix, a bar for post-type coverage, an Area trend for maintenance.

Same plugin, same TOC output, but a navigation surface that a quarterly review can land on without opening every long article by hand.