Sign In

Chatbot and Semantic Search for WordPress with AI-Kit

AI-Kit helps visitors find answers in your WordPress content through a site-wide chatbot and an embeddable DocSearch component. Both can use the same indexed knowledge base; the chatbot can also use approved read-only REST/MCP integrations and selected web sources.

  • Visitor answers (Pro): connect the site to WP Suite with an active subscription and configure a compatible backend, typically in your own AWS account. Site connection does not deploy or authenticate that backend automatically.
  • Authoring tools (Free): use supported Chrome on-device AI for editor and Media Library workflows without a subscription. Browser and device support determine availability.

Start with Answers​

Open SmartCloud → Answers to select knowledge content and configure the assistant. Setup can be replayed with existing values; completing it with the chatbot off is a valid choice. The status view distinguishes source configuration from backend access. A successful administration check does not prove that visitor replies or ingestion are working.

Chatbot and connected information​

Configure the assistant's role, tone, topic boundaries and evidence requirements. The chatbot can select knowledge-category filters appropriate to the question, reducing irrelevant retrieval context. Approved read-only REST and MCP tools can retrieve shop or service information from endpoints you configure. Web grounding fetches selected, allowlisted HTTPS pages; it is not unrestricted web search. External tools that change data are not enabled.

Use Answers setup to start from a reviewed assistant preset, connect a supported live product catalog, and pair catalog products with your own public WordPress pages. Catalog data remains the source for prices and availability; the selected local pages provide the destination for visitors.

Semantic search and page summaries​

Place the AI-Kit Doc Search block in a page or another Gutenberg block area to return a knowledge-base summary with source cards. DocSearch keeps retrieval broad and presents relevant sources below the AI summary. Category and tag filters narrow results only when visitors explicitly choose them; the chatbot can instead use inferred taxonomy filters to target the question. DocSearch uses knowledge retrieval rather than the chatbot's external tools. This filtering distinction requires the corresponding AI-Kit backend update, not only a plugin update. Add an AI-Kit Feature block in summarizer mode when visitors need a shorter version of longer page content. These visitor-facing features require Pro and appropriate backend configuration.

Free and Pro requirements​

You can choose knowledge-source policies before a backend is connected, but content selection alone does not deliver documents or enable visitor answers. Knowledge Sync needs its configured server-side transport; search can use the content after backend indexing finishes.

Protected backend administration may require a separate sign-in to the site's Cognito pool, with appropriate permissions. A WordPress administrator session or WP Suite workspace session does not automatically provide that access. AWS and external-service charges are separate from the plugin subscription.

Where AI-Kit shows up in WordPress​

Gutenberg editor​

  • AI-Kit Sidebar: generate post SEO metadata (title/excerpt/etc.), write content with an Apply/Insert workflow.
  • Inline tools: Proofread / Rewrite / Translate in a compact toolbar group for editable text selections.
  • Image blocks: a dedicated SEO Metadata panel for image-like blocks (core/image, core/cover, core/media-text).

Media Library​

Generate image SEO metadata (alt text, title, caption, description) from:

  • List and Grid views
  • Attachment details panel
  • Attachment edit screen
  • Bulk generation + preview + accept flows

Frontend (Pro)​

  • AI‑Kit Chatbot
  • AI‑Kit Feature block
  • AI‑Kit Doc Search block
  • [smartcloud-ai-kit-feature] shortcode
  • [smartcloud-ai-kit-doc-search] shortcode

Use the chatbot for conversations, DocSearch for focused knowledge retrieval, and the Feature component for page summaries or other configured AI actions. Review the selected sources and test representative questions before making visitor answers available.

Knowledge Base (Pro)​

Automatically synchronize approved public WordPress posts, pages, and selected custom post types into the Knowledge Base. Configure per-type approval policies, combine manual policy with external and WordPress-derived vocabularies, and inspect delivery and ingestion status in the admin. See Knowledge Sync for enrollment, cron scheduling, metadata layers, and source URL overrides.

What this documentation covers​

This section focuses on how to use AI‑Kit inside WordPress, plus a few developer reference pages:

  • Editor tools — Sidebar, inline selection tools, image SEO panels
  • Media Library — image SEO metadata generation for attachments
  • Blocks — Feature + Doc Search Gutenberg blocks (Pro)
  • Shortcode — Feature + Doc Search shortcodes (Pro)
  • Chatbot — configure the site chatbot from Chatbot Settings (admin UI)
  • Knowledge Sync — approved content synchronization, metadata layers, URL overrides, and delivery status
  • Theming (CSS variables) — customize --ai-kit-* design tokens
  • Capabilities & Modes — on-device vs backend, capability decisions, fallback rules
  • JavaScript API — the public runtime surface for developers (features.*, renderFeature, readiness helpers)
  • Backend API — REST endpoints (OpenAPI)

For setup and deployment guides (SAR template, AWS configuration, security hardening), see your project docs outside of this reference section.