Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Ask My Content - AI Q&A Chatbot

开发者 ugoltsev
更新时间 2026年4月3日 00:27
PHP版本: 7.4 及以上
WordPress版本: 6.9
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

ai chatbot knowledge-base content-search virtual-assistant

下载

1.2.1 0.8.0 0.8.4 1.2.2 0.9.0 0.8.1 0.7.0 0.4.2 0.8.2 0.7.1 0.5.1 0.6.0 0.8.3 1.0.0 1.1.0 0.4.3 1.2.0

详情介绍:

Ask My Content brings AI-powered question answering to your WordPress site. Instead of giving generic chatbot responses, this plugin indexes your site's content and uses it to provide accurate, context-aware answers to visitors. Unlike standard content search plugins that rely on keyword matching, Ask My Content uses semantic embeddings and retrieval-augmented generation to return direct answers in full sentences. Supports Gutenberg, Elementor, Avada, and WooCommerce content. Some highly customized dynamic content may still require review. See FAQ for details. Key Features
Note: Your site's content and user questions are securely sent to an external AI service (OpenAI) for processing.

安装:

  1. Upload the plugin files to /wp-content/plugins/ask-my-content, or install via the WordPress Plugins screen.
  2. Activate the plugin through the 'Plugins' screen in WordPress.
  3. Optionally configure settings in Dashboard -> Ask My Content (floating launcher, indexing posts).
  4. Run the initial indexing from Dashboard -> Ask My Content by pressing "Start Indexing", or run wp amc index from the command line.
  5. Add the chatbot to the website using either:
  6. Enable floating chat launcher site-wide
  7. The shortcode: [ask_my_content]
  8. The Gutenberg block: "Ask My Content"

屏幕截图:

  • Dashboard - `Ask My Content` admin page.
  • Block Editor - `Ask My Content` block with align, size and colors params.
  • Dashboard - `Ask My Content` - `Payments` tab.

升级注意事项:

1.2.0 Improved content indexing support for Gutenberg, Elementor, Avada, WooCommerce, and other post types. If your site was indexed with an older plugin version, email info@pavelweb.com for re-index instructions.

常见问题:

Why is indexing stuck?

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.

Why my indexed token count is low

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.
If your indexed token count still stays unexpectedly low after re-running indexing, see the next FAQ section: What content is supported for indexing? If the chat still answers with "No available content," the page may rely heavily on content generated outside the main WordPress content flow.

What content is supported for indexing?

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', ...)).
That means it usually works well with content that lives inside the main editor content area, but it may still miss text that comes only from:
  • 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.

Does this plugin use my OpenAI API key?

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

Will this slow down my site?

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

Is my data safe?

Yes. Content is transmitted securely to the backend.

Does this plugin support WordPress Multisite?

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).

Can I customize the shortcode output?

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.

更新日志:

1.2.2 Improved content indexing support for premium Elementor components. 1.2.1 Added X button to close the floating chat dialog (also can be closed by the Esc key) 1.2.0 Improved content indexing support for Gutenberg, Elementor, Avada, WooCommerce, and other post types. 1.1.0 Added support for other content types (Products, Books, Events, etc.), including WooCommerce products. 1.0.0 Added Payments tab to Ask My Content Settings, where you can check your usage and pay the balance (currently with Stripe) 0.9.0 Indexing in the backend is now async. Remaining Count = 0 in the table means that all pages/posts have been sent to the backend. The actual indexing status is reflected on the Indexing status line. 0.8.4 Added Use Theme Colors checkbox on the plugin admin page. 0.8.3 In the chat response, source links are now clickable. 0.8.2 Added warnings that WP-CLI may be required for indexing, in case WP-Cron is disabled, and similar cases. 0.8.1 Amended WP-CLI command suite (wp amc) 0.8.0 Added optional floating chat launcher that can appear site-wide. New settings let you enable the floating widget and customize the launcher button label (default: "AI Chat"). To enable: go to Dashboard -> Ask My Content and check "Enable floating chat launcher site-wide", then Save Changes. 0.7.1 Minor fixes. 0.7.0 Chat now behaves more like a real conversation: each visitor/admin gets their own session so replies stick to their thread, and the chat window remembers recent history in the same tab when you come back. 0.6.0 Tested with WordPress 6.9 Fixed new Plugin Check complaints. 0.5.1 Improved chat error handling so the browser console surfaces the underlying API failure while the front-end shows a concise, user-friendly message. Chats now recover automatically when the 12-hour security token expires, so long conversations continue without forcing visitors to reload the page. 0.4.3 Changed the plugin name from "Ask My Content" to "Ask My Content - AI Q&A Chatbot" 0.4.2 Initial release - shortcode, block, automatic content sync, AI-powered answers.