No. SleekAI runs its own vector index over the same ht_kb articles, so answers stay current with the live KB without depending on Heroic's search engine. Heroic's search continues to work on the article pages and shows the existing analytics. Think of SleekAI as a parallel surface for natural-language questions, not a replacement for the search box on the KB index.

Yes. Citations are on by default and customizable in the bot prompt. The bot quotes the relevant section of the article and links the source so the user can verify the steps. For support deflection that citation matters; users follow the link, see the full context, and trust the fix. Turning citations off is possible but rarely advisable for help-desk use cases.

Yes. Exclude them by post status, taxonomy term, or display condition. A draft article never gets indexed; an internal-only article in a private taxonomy can be filtered out of the bot's source list. If you run a public bot and a staff bot, scope each to the appropriate articles and use role-based display conditions to enforce who sees which surface.

Yes. WPML, Polylang, and TranslatePress are all supported, and the bot replies in the active language. Translated Heroic articles feed the bot's context per language, so a visitor on the German version gets German answers grounded in the German translations rather than machine-translated English. The multilingual plugin owns the translation; SleekAI owns the bot.

Every chat is logged inside SleekAI for review and prompt tuning. The logs become a gap-analysis feed: questions that deflected to a form usually point to missing or unclear articles, and that list goes to the docs team. Logs stay on your WordPress install; the LLM provider only sees the request payload at inference time, not a stored copy of past chats.

SleekAI is a one-time WordPress plugin purchase. You bring your own LLM key for usage, so inference and vector storage costs land on your OpenAI, Anthropic, Google, or OpenRouter account directly. That keeps long-term costs predictable; high-volume sites pay for the tokens they actually use rather than a markup baked into a SaaS subscription.

Yes, indirectly. Heroic's built-in search analytics continue to work on the KB pages themselves, recording which queries hit nothing and which articles get the most opens. SleekAI adds its own conversation log, which captures full-question chats the search box would never see. Together they paint a complete picture: search analytics for keyword behavior and chat logs for natural-language problem-solving.

Yes. Heroic articles often include code blocks for API examples or shell commands, and SleekAI preserves them in the retrieved context and returns them formatted in chat. That matters for developer KBs where a half-quoted snippet is worse than no answer at all. If the article has the exact command, the bot quotes it intact and cites the article it came from.