SleekView for LuckyWP Table of Contents
SleekView reads the lwptoc_options row LuckyWP Table of Contents writes plus the per-post lwptoc_disable_auto meta and a parsed heading index of post_content, then renders the result as a per-post audit grid with TOC source, headings and last edit inside WP Admin.
♾️ Lifetime License available
Auto-insert is convenient. Coverage should still be visible.
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 or whether it arrived through auto-insert, a shortcode or the block.
SleekView reads the same options row and the per-post meta, plus a parsed heading index, and renders the result as a sortable audit table. One row per post, with TOC source (auto, shortcode, block, below threshold, disabled), heading count, post type, author and last modified. Filter to long posts where auto-insert is suppressed, scope to manual-only post types, sort by heading count to plan structural rewrites that unlock auto-insert.
Because the dataset is built from standard WordPress storage, no extra tables are needed. The plugin keeps owning rendering, the shortcode and the block; SleekView adds the per-post audit table a global settings screen cannot offer.
Workflow
How SleekView surfaces LuckyWP Table of Contents data
Point at the LuckyWP config
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical LuckyWP Table of Contents coverage view
wp_posts
| Title | Type | TOC source | Headings | Deepest | Last edited |
|---|---|---|---|---|---|
| The complete guide to ergonomic desks | post | Auto | 14 | H3 | 2026-05-10 |
| Spring sourdough starter guide | post | Auto | 9 | H3 | 2026-04-28 |
| Founder interview: scaling to 50 staff | post | Shortcode | 7 | H2 | 2026-05-09 |
| Office redesign on a $500 budget | post | Disabled by override | 11 | H3 | 2026-05-08 |
| Five quick weeknight pastas | post | Below threshold | 3 | H2 | 2026-05-04 |
Comparison
Default LuckyWP Table of Contents admin vs SleekView
Default LuckyWP Table of Contents admin
- Settings screen is global with no per-post coverage table
- Auto-insert versus manual placement is invisible without opening posts
- Per-post lwptoc_disable_auto overrides hide inside each editor
- No native column for TOC source across the post list
- Heading-count rollups across the content base require raw SQL
SleekView
- TOC source (auto, shortcode, block, disabled) as a native column
- Filter to long posts where auto-insert is suppressed in a click
- Joined post type, author and last modified for content audits
- Saved views per role: SEO lead audit, editor refresh shortlist, agency report
- Same heading index the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for LuckyWP Table of Contents
Source mix as a real column
Auto-insert, shortcode and block placement render as a single TOC source column instead of states inferred from scattered settings and per-post toggles.
Composable coverage filters
Stack filters on TOC source, post type and heading count to land cohorts like long posts disabled by override or manual-only docs in one query.
Export the audit
Any filtered view exports to CSV. The auto-insert-suppressed cohort and the manual-only list become the next sprint's editorial deliverable.
Audience
Who uses SleekView for LuckyWP Table of Contents
Editorial teams
Confirm auto-insert actually fires on long articles and use the source column to spot posts that lean on a manual block which may have been deleted during a rewrite.
SEO leads
Trust the TOC layer for on-page navigation only after the per-post table confirms it renders across every template you actually care about.
Agency consultants
Export the no-TOC long-form list for the next editorial sprint and revisit the source column monthly so manual blocks do not silently replace auto-insert.
The bigger picture
Why auto-insert is exactly when coverage starts hiding
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 reads the same options, the same per-post meta and the same heading structure and renders the result as a sortable grid with TOC source, headings and joined post fields. Filters stack so the auto-insert-suppressed cohort, the manual-only post types and the below-threshold rows become one-click views.
The plugin keeps owning rendering; editorial gets the per-post audit a global settings screen cannot offer.
Questions
Common questions about SleekView for LuckyWP Table of Contents
From lwptoc_options in wp_options, per-post lwptoc_disable_auto and related meta in wp_postmeta and a parsed heading index of post_content. Standard WordPress storage, no new tables and no separate sync layer.
No. SleekView builds and caches a per-post heading index when the dataset is first queried and refreshes it when post_content changes, so the table reads from the index instead of re-walking every post.
Yes. TOC source is a native column with values auto, shortcode, block, below threshold and disabled by override. The same field works as a filter so the auto-insert-suppressed cohort is one click away.
Yes. lwptoc_options include which post types auto-insert applies to, and the table respects that. Filter post_type to compare coverage across posts, pages, docs and any custom type you opted in.
TOC toggles still belong inside the post editor where LuckyWP owns the UI. SleekView surfaces coverage and gaps, not a write surface for the per-post override itself.
No. The plugin still owns TOC rendering, styling, the shortcode and the Gutenberg block. SleekView adds the per-post audit surface the global settings screen cannot offer.
No. The heading index is built and read inside WP admin. The front end keeps rendering the TOC through LuckyWP exactly as today, with no extra queries during page load.
Yes. Any filtered view exports to CSV with the columns the table shows. Editorial leads typically export the long-without-TOC list as the next sprint's content fixes.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout