Ask My Content - AI Search Chatbot

The admin "Start Indexing" button schedules a background task via WordPress cron. If your site uses aggressive caching (e.g., LiteSpeed Cache, WP Super Cache), cached pages may bypass cron triggers, causing indexing to appear stuck at "scheduled..." or "stopping...". Solutions:

1. Refresh the settings page -- stale state is auto-detected and reset.
2. Use wp amc index from the command line -- it runs synchronously and doesn't depend on cron. See Command Line Usage section.

Enable Automatically re-index modified pages, posts, and content if you want content edits to appear in chat results quickly without running manual indexing. Keep it disabled if your site has frequent edits to large pages (for example long landing pages or content-heavy builder pages). In that case, each update can trigger additional background embedding requests, which may increase API usage and add server/backend load. Practical guideline:

• Enable it for low-to-moderate edit frequency or smaller pages.
• Disable it for high-frequency editing of large pages, and run indexing in batches when convenient.

Low indexed token count usually means the plugin did not find much readable page content to send for indexing. This can happen if:

1. The page is mostly built from theme templates, banners, sliders, or other repeated global sections.
2. The important content is loaded by a plugin or builder widget that does not expose much text to WordPress.
3. Indexing finished before the latest content changes were re-run. Ask My Content now supports common WordPress content builders much better, including Gutenberg, Elementor, Avada, and WooCommerce product content.

Ask My Content is designed to index the main readable text of your site content. Currently supported:

• Standard WordPress pages and posts
• Gutenberg block content
• Elementor content in many common setups
• Avada content in many common setups
• WooCommerce product content, including product descriptions, short descriptions, price, SKU, weight, dimensions, and attributes
• Other public post types, if enabled in plugin settings In general, the plugin reads the main post content the way WordPress normally renders it, using the standard content pipeline (apply_filters('the_content', ...)).

• headers or footers
• sliders, popups, and announcement bars
• heavily customized builder widgets
• content injected from external sources or loaded later with JavaScript If a page is important for search quality, open it in WordPress and make sure the main text is actually stored in the page, post, or product content itself before re-running indexing.

By default, the plugin uses the developer's AI API key on a secure backend (with generous usage limits). This means you don't need your own AI API key.

No. Heavy AI processing (embeddings, search, completions) happens on a separate Node.js backend service.

Yes. Content is transmitted securely to the backend.

Not yet. Ask My Content is not currently compatible with WordPress multisite installations, so it must be activated on individual sites (no network-wide support yet).

Yes. The [ask_my_content] shortcode accepts optional attributes such as title, sessionId, width, height, and the various color tokens (headerBackground, headerTextColor, chatBackground, chatUserBubble, chatBotBubble, inputBackground, inputTextColor). They map to the same style variables used by the block. See the inline comment above amc_render_chat_shortcode() in ask-my-content.php for the current list and defaults.