| 开发者 | achlaai |
|---|---|
| 更新时间 | 2026年8月5日 17:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
achlaai directory under /wp-content/plugins/.Plugins that use your own API key leave you responsible for the model-provider account, a secret stored in WordPress, and a separate bill that changes with token use. They may also limit indexing to content stored as WordPress posts. Achla runs the crawler, index, and model calls as a managed service. It can index permitted public content across the site, including PDFs and pages that are not WordPress posts. There is no model-provider key, separate token bill, or vector database for you to operate.
No. Achla answers questions from your published content and links to the pages it used. It does not open tickets, route conversations to a human agent, or manage a support inbox.
Yes. It includes 100 searches a month and 100 indexed pages, with no payment card. It is an ongoing plan rather than a trial. When the monthly searches are used, search stops until the allowance renews; the plan does not automatically charge you for more. Free projects that remain completely unused are eventually removed after an email warning.
No. Achla runs the crawler, index, and model calls. There is no model-provider key to obtain, paste into WordPress, secure, rotate, or refill.
No. Plans are measured in searches. Paid plans include a fixed allowance, and extra usage is purchased as blocks of searches rather than model tokens.
Achla is designed to show an answer only when it can cite supporting pages from your indexed content. When the available pages do not provide enough support, it says so instead. AI-generated answers can still be imperfect, so visitors should follow the source links when accuracy matters.
Yes. The answer comes back in the language of the question, including right-to-left languages such as Hebrew and Arabic. Your pages do not have to be translated first.
Yes, on a paid plan sized for the site. The free plan indexes 100 pages and is intended for testing one section rather than covering an entire archive. Start with the section visitors ask about most, review the answers, and expand if it works for your content.
This is one of the main reasons to use Achla. Questions are matched against the meaning of indexed pages rather than exact wording, so alternative terms, spelled-out acronyms, and plain-language phrasing can reach the relevant content. Answers still use your indexed pages as their sources.
Only if you choose Attach. Bubble and Inline work alongside your existing search. Attach connects Achla to the search field already on the site.
Public pages that Achla is permitted to crawl, including supported documents such as PDFs. Content behind a login, and content excluded by robots rules, stays out.
No. It does not store visitor questions, IP addresses, page content, cookies, or widget sessions in WordPress. It stores only this site's connection, lifecycle, placement, release, and diagnostic state.
Open Settings > Achla AI Search. The status screen identifies the reason and the next step. Common causes include ownership confirmation still being required, indexing not being complete, placement being switched off, or the signed release needing to refresh.
Attach accepts a narrow set of CSS selectors and tests them on the server before saving. If the element is missing at runtime, the widget falls back to Bubble and records a warning. The warning clears once the field is found again.
The widget disappears and scheduled work stops. The connection is retained, so reactivating the plugin continues from the previous state. Deactivation does not disconnect the site or cancel a subscription.
Uninstall attempts to disconnect the site, then removes this site's options, temporary connection data, locks, and scheduled hooks. It does not cancel an Achla subscription; subscriptions are managed in the Achla dashboard.