AI chatbot for Easy Table of Contents: navigate long posts
SleekAI reads ez-toc-settings, the _ez-toc-disabled and _ez-toc-alttext postmeta, and each post's heading structure so the bot can answer with a deep link to the right H2 using your own OpenAI, Anthropic, Google, or OpenRouter key.
♾️ Lifetime License available
Tables of contents help, until the post is too long to scan
Easy Table of Contents is the small plugin that does one thing well: it auto-generates a clickable TOC from your H2 and H3 headings and inserts it near the top of each long post. Settings live in the ez-toc-settings wp_options entry. Per-post overrides go to _ez-toc-disabled and _ez-toc-alttext postmeta. For a typical 1,500-word post, the TOC is enough. For a 6,000-word ultimate guide with 14 H2s, readers still get lost. The TOC scrolls off-screen the moment they start reading.
SleekAI reads the same headings the TOC plugin uses, plus the post body, and turns that into a chat-driven navigator. A reader asks "where does this article talk about pricing?" and the bot replies with the exact H2 anchor link. They click, jump, and stay on page. No scrolling, no scrubbing, no opening a competitor's article instead.
Generic chatbots don't know your post's heading structure. They might know the title, but they can't deep-link to a section. SleekAI's variable mapping exposes the post object, the headings, and the ez-toc-settings behavior, so the bot understands not just what's in the post but how the TOC has been configured. It also respects _ez-toc-disabled so it doesn't recommend a TOC that you intentionally hid on a specific post.
Workflow
How SleekAI plugs into Easy Table of Contents
Map post content and TOC config
Add deep-link instructions
Scope to long-form posts
Review and tune presets
Try it now
A reader navigating a long guide
Comparison
Generic chatbot vs SleekAI for Easy Table of Contents
Generic chatbot
- Can't see ez-toc-settings or per-post _ez-toc-disabled overrides
- Doesn't read the post's heading structure to build deep links
- Sends readers back to the top of the post instead of a section
- Misses anchor slugs and the alttext set in _ez-toc-alttext
- No awareness of which posts intentionally hide their TOC
SleekAI chatbot
-
Reads the
ez-toc-settingsoption and respects per-post overrides - Indexes H2 and H3 headings to generate accurate anchor deep links
-
Surfaces
_ez-toc-alttextwhen custom heading labels are set -
Skips TOC suggestions on posts with
_ez-toc-disabled - Per-post scoping so the bot's answers match the article in front of the reader
Features
What SleekAI gives you for Easy Table of Contents
Section-aware deep links
The bot reads the H2 and H3 heading structure and returns the exact anchor slug for the section a reader asks about. No more sending people to the top of a 5,000-word article and hoping they scroll.
Topic-to-heading mapping
Readers phrase questions in their own words, not your H2 titles. SleekAI's model matches a question to the closest heading using the post body as context, so a question about cost lands on Section 7 Plans and pricing even if the word price isn't in the H2.
Respects your TOC overrides
If you've disabled the TOC on a specific post via _ez-toc-disabled or customized labels via _ez-toc-alttext, the bot follows those rules. Editorial choices stay editorial, the bot doesn't override them.
Use cases
Where this chatbot earns its keep
Ultimate guides and pillar posts
Posts that take 25 minutes to read end-to-end. The bot turns them into a queryable index so readers leave with the answer they came for.
Documentation sites
Long docs pages with 20+ sections. Readers ask for the exact piece they need rather than scrolling. Deep links also become shareable in support tickets.
Editorial publishers
Magazine sites running explainer features. Readers ask for the part of the story relevant to them and stay on page longer, which lifts session time and ad views.
The bigger picture
Why a long-post chatbot beats a static TOC
Static tables of contents solve the navigation problem at the top of the post, then disappear as soon as the reader scrolls past them. For posts under 2,000 words, that's fine. For pillar content, ultimate guides, and documentation, the reader is lost again by the third H2.
They scroll back up, look at the TOC, scroll down again, and lose their place twice. A chatbot fixes that by staying available throughout the scroll. Readers ask where the pricing section is, get an anchor link, and click.
That single click costs them five seconds and saves them five minutes. Multiplied across thousands of readers on a pillar post, that's hours of cumulative reader time you didn't waste. The deeper benefit is matching reader vocabulary to your headings.
Most readers don't phrase questions the way you phrase H2s. They ask about cost when your heading says Plans and pricing. A static TOC requires the reader to translate their question into your wording.
A chatbot does that translation automatically. Posts ranking on competitive keywords usually win or lose based on dwell time. A long post that readers actually navigate through stays longer in search rankings than one they bounce out of.
Easy Table of Contents helps. A chatbot reading the same content helps more.
Questions
Common questions about SleekAI for Easy Table of Contents
Global settings live in the ez-toc-settings wp_options entry. Per-post overrides use the _ez-toc-disabled (hide TOC) and _ez-toc-alttext (custom heading) postmeta. SleekAI maps both, so the bot's answers respect global behavior and post-specific exceptions.
It uses the same anchors Easy Table of Contents generates from each heading. That guarantees the deep link the bot returns actually works in the rendered page, since both plugins are looking at the same H2 and H3 slugs.
SleekAI doesn't strictly need Easy Table of Contents installed. The bot reads the post's heading structure directly from the post content. If you're on a different TOC plugin, you'll lose the per-post override semantics but the deep linking still works.
Yes. The bot keeps the conversation context, so after jumping to Section 7, a reader can ask is there an annual discount and the bot answers from the same post content. The chat works like a guided reader sitting next to them.
Yes, if you've enabled Easy Table of Contents on those post types and mapped them in SleekAI. The bot reads the heading structure from any post object you expose, including custom post types like docs, courses, or guides.
It works in any language the model supports, which covers most modern languages. The headings are read as text, the bot replies in the language the reader uses. Multilingual sites can run one bot that adapts to the visitor's language naturally.
Yes, you can configure it to. With the post body in context, a request like summarize this post yields a 4-bullet summary tied to the H2 structure. Some publishers offer this as a CTA in the chat presets to demonstrate the bot's value.
No measurable impact on SEO since the chatbot widget loads after first paint and isn't seen by search engines as content. Page speed is preserved by lazy-loading the widget. Easy Table of Contents continues to add the TOC server-side as it always has.
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