LuckyWP Table of Contents is the heavier alternative to Easy Table of Contents, used by sites that publish reference-grade long form content with deep nested structure. The plugin parses headings on save, builds a nested tree of chapters and subsections, and writes the tree into wp_postmeta under the lwptoc_items key. The frontend renders the TOC via the lwptoc shortcode or an auto-insertion filter.

The piece that defaults break is the share image. A reference guide with eight chapters and twenty subsections shares with the same OG image as a regular blog post. SleekPixel reads the nested lwptoc_items tree, counts the top-level chapters and the nested subsections at one level deep, and renders a card naming both. The badge stamps the chapter count, a smaller slot names the subsection depth, and the accent stripe signals a reference guide.

The benefit is for both sides of the share. Readers searching for a reference can pick the right post from a preview, without clicking and reading the first paragraph to figure out scope. Editorial teams that mix quick takes and reference guides get a share that matches the actual scope of each post.

Sites that pick LuckyWP Table of Contents over Easy Table of Contents do it because they care about heading hierarchy. The plugin preserves the full nested structure of a post's headings, which matters for reference guides, technical playbooks and knowledge bases where the difference between a chapter and a subsection is the difference between a section and a sub-step. The piece that defaults break is the share.

A reference guide with eight chapters and twenty subsections shares with the same OG image as a quick take, and readers on Slack or LinkedIn see no signal that the share leads to a multi-chapter reference. LuckyWP already collected the structure in lwptoc_items. SleekPixel turns that structure into a design signal.

The chapter count becomes a badge, the subsection depth becomes a secondary slot, and the accent stripe signals reference scope. Readers searching for a reference pick the right post from the share, editorial teams get a higher quality of engagement on the work they put into deep posts, and the reference guide finally has a share preview that matches the work the post represents.