Title: Achla AI Search Author: achlaai Published: July 27, 2026 Last modified: July 27, 2026 --- Search plugins ![](https://ps.w.org/achlaai/assets/banner-772x250.png?rev=3623963) ![](https://ps.w.org/achlaai/assets/icon-256x256.png?rev=3623963) # Achla AI Search By [achlaai](https://profiles.wordpress.org/achlaai/) [Download](https://downloads.wordpress.org/plugin/achlaai.0.3.5.zip) * [Details](https://wordpress.org/plugins/achlaai/#description) * [Reviews](https://wordpress.org/plugins/achlaai/#reviews) * [Installation](https://wordpress.org/plugins/achlaai/#installation) * [Development](https://wordpress.org/plugins/achlaai/#developers) [Support](https://wordpress.org/support/plugin/achlaai/) ## Description Turn your WordPress content into answers visitors can trust. Achla AI Search gives visitors a concise answer drawn from your public pages and links every answer to its sources. They can ask naturally, in their own language, and get an answer instead of digging through a list of search results. Achla is managed end to end. You do not need an OpenAI, Gemini, or other model API key. There is no separate model-provider account to fund, no prepaid model credits to monitor, and no embeddings database or search backend to maintain. Achla handles crawling, indexing, model calls, signed widget releases, and usage controls. Start free with 30 searches per month and up to 30 indexed pages — no card required. Paid plans include a fixed number of searches, so you budget in searches rather than LLM tokens. #### Why site owners choose Achla * Direct answers, not another results page. Visitors get a concise response with clickable citations to the pages that support it. * Grounded in your content. If the indexed pages do not support an answer, Achla does not present a guess as fact. * No model API keys. There is no OpenAI or LLM key to obtain, paste into WordPress, secure, rotate, or refill. * No separate model-token bill. Plans are measured in searches, not input and output tokens from a second provider. * The visitor’s language by default. Visitors ask in their own language and receive the answer in that language. * Managed indexing. Achla crawls permitted public content, builds the search index, and keeps it fresh as the site changes. * Flexible placement. Use a floating Bubble, an Inline shortcode or Gutenberg block, or attach the widget to an existing search field. #### Connect without AI plumbing 1. Install and activate the plugin. 2. Select Connect, sign in to Achla, and confirm ownership of the site. No API key is copied into WordPress. 3. Achla crawls the permitted public pages and builds the index. WordPress shows the current connection and indexing status. 4. Choose Bubble, Inline, or Attach placement, preview it, and enable the widget when ready. Connection actions require a WordPress administrator and use short-lived, server- generated proof. Credentials remain server-side. Widget releases are signed and verified before they run in the browser; if verification fails, the widget stays off. A cloned site or a move to another subdomain requires ownership verification again. Visual styling is managed in the Achla dashboard. This plugin controls whether the widget is active and where it is placed. HTTP sites show a persistent reduced- security warning. ### External services This plugin requires the third-party Achla AI Search service at https://achlaai. com. The service crawls permitted public content, builds and maintains the index, generates cited answers, provides widget configuration, and manages service billing. 1. **Ownership connection.** When an administrator clicks Connect, Resume, or Reconnect, the plugin sends the site origin, WordPress callback URL, and a short-lived ownership challenge to Achla. The secret verifier is sent only after WordPress validates Achla’s signed callback. WordPress then stores the site binding, project identifier, public widget key, and a server-side management credential. 2. **Lifecycle status and health.** While connected, WordPress makes paced, authenticated requests to read project and index status. Diagnostics can contain only the classified states `ATTACH_TARGET_MISSING` and RELEASE_UNAVAILABLE, software versions, status classifications, and timestamps. They do not contain page content, visitor questions, email addresses, IP addresses, cookies, secrets, arbitrary URLs, or stack traces. 3. **Disconnect.** An administrator disconnect, or uninstall best effort, revokes the installation binding and management credential. It does not cancel an Achla subscription. 4. **Signed widget release.** WordPress periodically requests a signed control and manifest from Achla. The connector checks its signature, expiry, compatibility, rollback state, immutable asset URL, and Subresource Integrity value. The browser loads only a verified release. 5. **Widget use.** The verified widget uses Achla’s widget configuration and search APIs. When a visitor asks a question, Achla receives the question, the site’s public widget key, the page origin, and the visitor’s IP address carried by the HTTPS request. These data are used for site binding, abuse controls, and returning an answer from the indexed public content. The plugin’s three public WordPress REST routes are limited to a signed ownership callback, a no-store release decision, and nonce-protected, same-origin runtime diagnostics. All management routes require an administrator capability and WordPress REST nonce. The local bridge does not use cookies, browser storage, advertising identifiers, iframes, or page-content telemetry. Review the service terms before enabling the widget: * Privacy Policy: https://achlaai.com/legal/privacy * Terms of Service: https://achlaai.com/legal/terms ## Screenshots [⌊A visitor asks in their own language and gets a concise answer with links to the supporting pages.⌉⌊A visitor asks in their own language and gets a concise answer with links to the supporting pages.⌉[ A visitor asks in their own language and gets a concise answer with links to the supporting pages. [⌊Connect without copying an API key, then see ownership, service, and index status in WordPress.⌉⌊Connect without copying an API key, then see ownership, service, and index status in WordPress.⌉[ Connect without copying an API key, then see ownership, service, and index status in WordPress. [⌊Choose Bubble, Inline, or Attach placement and check widget diagnostics before publishing.⌉⌊Choose Bubble, Inline, or Attach placement and check widget diagnostics before publishing.⌉[ Choose Bubble, Inline, or Attach placement and check widget diagnostics before publishing. ## Blocks This plugin provides 1 block. * Achla AI Search ## Installation 1. Install the plugin ZIP through Plugins > Add New > Upload Plugin, or place the ` achlaai` directory under `/wp-content/plugins/`. 2. Activate Achla AI Search. 3. Open Settings > Achla AI Search and select Connect. 4. Complete ownership setup on Achla, then return to WordPress and monitor the connection and indexing status. 5. Keep Bubble placement or choose Inline or Attach. Test an Attach selector before saving it. Enable “Show the widget” only when you are ready to display the widget and its Powered by Achla AI attribution publicly. The widget renders only when the management binding is valid, the project is active, the index is ready, placement is enabled, and a current signed release passes verification. ## FAQ ### Do I need an Achla account? Yes. A free Achla account is required to connect and manage the service. The Free plan does not require a payment card. ### Do I need my own OpenAI or LLM API key? No. Achla manages the crawler, index, model calls, and billing. There is no model key to obtain, paste into WordPress, secure, rotate, or refill. ### Do I need to prepay model tokens? No separate model-token balance is required. The Free plan includes 30 searches per month. Paid plans include a fixed search allowance, and optional additional usage is purchased as search blocks rather than LLM tokens. ### Can visitors ask in their own language? Yes. Achla returns the answer in the language of the question by default. ### What happens when I deactivate the plugin? Deactivation stops all front-end output and scheduled connector work. It keeps the local binding so activation can recheck status and resume. Deactivation does not disconnect the site and does not affect the subscription. ### What happens when I uninstall the plugin? Uninstall performs a bounded best-effort local disconnect and emits a local audit outcome for WordPress integrations. It then removes this site’s options, temporary connection data, locks, and scheduled hooks. If the network request cannot be confirmed, the backend stale-credential policy remains the recovery boundary. Uninstall never cancels a subscription. ### Why is the widget not rendering? Open Settings > Achla AI Search. Rendering remains off when ownership needs verification, the project is not active, indexing is not ready, the release is expired, incompatible, rolled back, or killed, or placement is disabled. The status screen provides the corresponding recovery action. ### How does Attach fallback work? Attach accepts a narrow CSS selector subset and requires a successful server test before saving. If the element is absent at runtime, the widget falls back to Bubble and records a classified warning. The warning clears after the target is observed again. ### Does the connector store visitor data in WordPress? No. The connector does not store visitor questions, IP addresses, page content, cookies, or widget sessions in WordPress. It stores only site-owner connection, lifecycle, placement, signed-release, and classified diagnostic state for the current site. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Achla AI Search” is open source software. The following people have contributed to this plugin. Contributors * [ achlaai ](https://profiles.wordpress.org/achlaai/) [Translate “Achla AI Search” into your language.](https://translate.wordpress.org/projects/wp-plugins/achlaai) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/achlaai/), check out the [SVN repository](https://plugins.svn.wordpress.org/achlaai/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/achlaai/) by [RSS](https://plugins.trac.wordpress.org/log/achlaai/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.3.5 * Security hardening: the runtime placement diagnostic endpoint now requires a WordPress nonce issued with the bridge script. #### 0.3.4 * Move settings maintenance and public runtime diagnostics to asynchronous scheduled work. * Respect lifecycle and release backoff in due-aware status, heartbeat, and release cron callbacks. * Enforce signed CMS control expiry when selecting and downloading self-hosted update packages. #### 0.3.2 * Keep setup in the current tab so registration and email verification can return to the original WordPress connection. * Continue bounded status polling while the first index and signed widget release are being prepared. * Improve WordPress.org compatibility checks, release gates, and package metadata. ## Meta * Version **0.3.5** * Last updated **11 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.0.2** * PHP version ** 7.4 or higher ** * Tags * [AI](https://wordpress.org/plugins/tags/ai/)[ai search](https://wordpress.org/plugins/tags/ai-search/) [customer support](https://wordpress.org/plugins/tags/customer-support/)[faq](https://wordpress.org/plugins/tags/faq/) [search](https://wordpress.org/plugins/tags/search/) * [Advanced View](https://wordpress.org/plugins/achlaai/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/achlaai/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/achlaai/reviews/) ## Contributors * [ achlaai ](https://profiles.wordpress.org/achlaai/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/achlaai/)