AI chatbot for PublishPress Blocks: permission and visibility aware
SleekAI reads the rendered PublishPress Blocks output (Advgb Tabs, Accordions, Pricing Table, Contact Form, Recent Posts) from the current page and respects per-role visibility, so the bot only sees what the visitor sees. Bring your own AI key.
♾️ Lifetime License available
A chatbot that respects your block permissions
PublishPress Blocks (formerly Advanced Gutenberg) ships 27 blocks under the advgb/* namespace: Advgb Tabs, Advgb Accordions, Advgb Pricing Table, Advgb Contact Form, Advgb Recent Posts, Advgb Woo Products, and more. They serialise into wp_posts.post_content with markers like wp:advgb/adv-tabs and resolve to real HTML at render time. SleekAI reads the rendered page, so a Pricing Table becomes plan rows, an Accordion becomes Q&A pairs, and Recent Posts becomes an in-page index.
What's particular about PublishPress Blocks is the Block Controls layer: visibility rules per role, schedule, device, browser, cookie, user meta, post meta, query string, and capability. Because SleekAI reads the post-render HTML, the bot inherits those exact rules. A block hidden from logged-out visitors stays out of the prompt. A block scheduled for next week doesn't leak its content today.
Display conditions and multibot mode then let you also scope the chatbot itself by user role, post type, or URL pattern. Conversations log in WordPress with model name and token usage. The JS API and PHP embed open the bot from any block click.
Workflow
How SleekAI talks to PublishPress Blocks
Let Block Controls do the gating
Map fields that matter
wp:advgb/* blocks by attribute. The bot then references those by name in its answers.
Scope with display conditions
Ship with your own AI key
Try it now
Try it on a PublishPress Blocks pricing page
Comparison
Generic chatbot vs SleekAI for PublishPress Blocks
Generic chatbot
- Ignores per-role block visibility rules set in the editor
- Can't read Advgb Pricing Table, Accordion, or Tabs content
- Risks leaking content hidden from the current visitor
- Hallucinates plan details and discount eligibility
- Requires manual retraining when block permissions change
SleekAI chatbot
-
Reads
wp:advgb/*markup from rendered HTML - Respects Block Controls visibility (role, schedule, device, etc.)
- Won't leak blocks hidden from the current site visitor
- Run a different chatbot per role or template (multibot)
- Logs every conversation with model, tokens, and page URL
Features
What SleekAI gives you for PublishPress Blocks (Advanced Gutenberg)
Visibility-aware by default
Block Controls hide blocks per role, schedule, device, or cookie. Because SleekAI reads the visitor-facing rendered HTML, those rules apply automatically, so the bot won't leak content the visitor isn't supposed to see.
Block-aware answers
Advgb Pricing Table, Accordion, Tabs, Testimonial, Recent Posts, and Woo Products blocks flow into the prompt as structured data, so the bot quotes plans, FAQs, and product lists using the page's own copy.
Role-scoped chatbots
On top of Block Controls, multibot mode and display conditions let you scope the chatbot itself by user role, so an editor bot, a member bot, and a public-visitor bot can share the install with separate prompts.
Use cases
Where PublishPress Blocks sites use SleekAI
Pricing and discount Q&A
Answer plan comparison, discount eligibility, and refund questions inline. The bot reads the Advgb Pricing Table and FAQ Accordion, with role-gated notices auto-hidden for the wrong audience.
Members-only knowledge base
On a members-only docs site, the bot reads only the blocks visible to the visitor's role. Members get answers from the gated docs; non-members get answers only from public sections.
WooCommerce browsing
The Advgb Woo Products block lists products on a page; the bot can recommend, compare, and link to specific items using the rendered grid plus any ACF fields you mapped.
The bigger picture
Why this matters for PublishPress Blocks sites
PublishPress Blocks is often picked for sites that need fine-grained control over what each visitor sees. Block Controls let you hide a notice from logged-out visitors, schedule a sale block for next Monday, or restrict a download link to a specific user-meta value. A generic chatbot ignores all that, so it can leak content the visitor isn't supposed to see or reference blocks they don't have access to.
SleekAI inherits the visibility rules automatically because it reads post-render HTML for the current visitor. A members-only docs page only feeds member content to a member's bot. A scheduled launch block stays invisible to the bot until its scheduled date.
On top of that, multibot mode and display conditions let you scope the chatbot itself by role, so admins get an admin bot, members get a member bot, and public visitors get a public bot. Conversation logging tracks which audiences struggle with which content so you can tighten the page or the prompt without breaking the gating. The result is a chatbot that respects the access model you already designed rather than working around it.
Questions
Common questions about SleekAI for PublishPress Blocks (Advanced Gutenberg)
Yes, automatically. PublishPress Blocks hides blocks before they render to the wrong visitor, and SleekAI reads the post-render HTML for that visitor. Anything Block Controls hides also stays out of the chatbot's context for that session.
You need an account with at least one supported provider: OpenAI, Anthropic, Google, or OpenRouter. Usage and billing stay on your provider account. A common setup is a cheap fast model for plan-comparison Q&A and a stronger one for billing or migration questions.
Yes. Multibot mode plus display conditions let you scope each bot by user role, post type, or URL pattern. An editor-only admin bot, a logged-in member bot, and a public-visitor bot can coexist on the same install with their own data scope.
Block Permissions control who can use each block in the editor, not who sees the block on the frontend. The bot doesn't interfere with editor permissions; it only reads what's published and rendered. You can still run an editor-only bot with admin display conditions if you want.
Yes. Auto-Insert Blocks injects reusable blocks into matching posts at render time. The bot reads the final rendered output, so injected blocks land in context just like any other block on the page.
No. Block Controls' schedule rule keeps the block out of the rendered HTML until its scheduled date, so the bot has no way to see it. The same applies to blocks restricted by query string, cookie, device, or operating system.
Yes. The Advgb Recent Posts / Content Display block renders a list of post cards with title, excerpt, and meta. The bot uses that as a small in-page index, suggesting which linked article best matches a visitor question.
Yes. Conversation logging is per chatbot, with user messages, assistant replies, model name, token usage, and page URL stored in WordPress. Use it to spot recurring confusion and tighten the prompt or the page content.
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