Turn your WordPress content into answers visitors can trust.<\/p>\n\n
Achla AI Search gives visitors a concise answer drawn from your public pages\nand links every answer to its sources. They can ask naturally, in their own\nlanguage, and get an answer instead of digging through a list of search\nresults.<\/p>\n\n
Achla is managed end to end. You do not need an OpenAI, Gemini, or other model\nAPI key. There is no separate model-provider account to fund, no prepaid model\ncredits to monitor, and no embeddings database or search backend\nto maintain. Achla handles crawling, indexing, model calls, signed widget\nreleases, and usage controls.<\/p>\n\n
Start free with 30 searches per month and up to 30 indexed pages \u2014 no card\nrequired. Paid plans include a fixed number of searches, so you budget in\nsearches rather than LLM tokens.<\/p>\n\n
Connection actions require a WordPress administrator and use short-lived,\nserver-generated proof. Credentials remain server-side. Widget releases are\nsigned and verified before they run in the browser; if verification fails,\nthe widget stays off. A cloned site or a move to another subdomain requires\nownership verification again.<\/p>\n\n
Visual styling is managed in the Achla dashboard. This plugin controls whether\nthe widget is active and where it is placed. HTTP sites show a persistent\nreduced-security warning.<\/p>\n\n
This plugin requires the third-party Achla AI Search service at\n https:\/\/achlaai.com. The service crawls permitted public content, builds and\nmaintains the index, generates cited answers, provides widget configuration,\nand manages service billing.<\/p>\n\n
Ownership connection.<\/strong> When an administrator clicks Connect, Resume, or\nReconnect, the plugin sends the site origin, WordPress callback URL, and a\nshort-lived ownership challenge to Achla. The secret verifier is sent only\nafter WordPress validates Achla's signed callback. WordPress then stores the\nsite binding, project identifier, public widget key, and a server-side\nmanagement credential.<\/p><\/li>\n Lifecycle status and health.<\/strong> While connected, WordPress makes paced,\nauthenticated requests to read project and index status. Diagnostics can\ncontain only the classified states Disconnect.<\/strong> An administrator disconnect, or uninstall best effort,\nrevokes the installation binding and management credential. It does not\ncancel an Achla subscription.<\/p><\/li>\n Signed widget release.<\/strong> WordPress periodically requests a signed control\nand manifest from Achla. The connector checks its signature, expiry,\ncompatibility, rollback state, immutable asset URL, and Subresource\nIntegrity value. The browser loads only a verified release.<\/p><\/li>\n Widget use.<\/strong> The verified widget uses Achla's widget configuration and\nsearch APIs. When a visitor asks a question, Achla receives the question,\nthe site's public widget key, the page origin, and the visitor's IP address\ncarried by the HTTPS request. These data are used for site binding, abuse\ncontrols, and returning an answer from the indexed public content.<\/p><\/li>\n<\/ol>\n\n The plugin's three public WordPress REST routes are limited to a signed\nownership callback, a no-store release decision, and nonce-protected,\nsame-origin runtime diagnostics. All management routes require an\nadministrator capability and WordPress REST nonce.<\/p>\n\n The local bridge does not use cookies, browser storage, advertising\nidentifiers, iframes, or page-content telemetry. Review the service terms\nbefore enabling the widget:<\/p>\n\n The widget renders only when the management binding is valid, the project is\nactive, the index is ready, placement is enabled, and a current signed release\npasses verification.<\/p>\n\n\n Yes. A free Achla account is required to connect and manage the service. The\nFree plan does not require a payment card.<\/p><\/dd>\n No. Achla manages the crawler, index, model calls, and billing. There is no\nmodel key to obtain, paste into WordPress, secure, rotate, or refill.<\/p><\/dd>\n No separate model-token balance is required. The Free plan includes 30\nsearches per month. Paid plans include a fixed search allowance, and optional\nadditional usage is purchased as search blocks rather than LLM tokens.<\/p><\/dd>\n Yes. Achla returns the answer in the language of the question by default.<\/p><\/dd>\n Deactivation stops all front-end output and scheduled connector work. It keeps\nthe local binding so activation can recheck status and resume. Deactivation\ndoes not disconnect the site and does not affect the subscription.<\/p><\/dd>\n Uninstall performs a bounded best-effort local disconnect and emits a local\naudit outcome for WordPress integrations. It then removes this site's options,\ntemporary connection data, locks, and scheduled hooks. If the network request\ncannot be confirmed, the backend stale-credential policy remains the recovery\nboundary. Uninstall never cancels a subscription.<\/p><\/dd>\n Open Settings > Achla AI Search. Rendering remains off when ownership needs\nverification, the project is not active, indexing is not ready, the release is\nexpired, incompatible, rolled back, or killed, or placement is disabled. The\nstatus screen provides the corresponding recovery action.<\/p><\/dd>\n Attach accepts a narrow CSS selector subset and requires a successful server\ntest before saving. If the element is absent at runtime, the widget falls back\nto Bubble and records a classified warning. The warning clears after the\ntarget is observed again.<\/p><\/dd>\n No. The connector does not store visitor questions, IP addresses, page\ncontent, cookies, or widget sessions in WordPress. It stores only site-owner\nconnection, lifecycle, placement, signed-release, and classified diagnostic\nstate for the current site.<\/p><\/dd>\n\n<\/dl>\n\n\nATTACH_TARGET_MISSING<\/code> and\n RELEASE_UNAVAILABLE, software versions, status classifications, and\ntimestamps. They do not contain page content, visitor questions, email\naddresses, IP addresses, cookies, secrets, arbitrary URLs, or stack traces.<\/p><\/li>\n\n
\n
achlaai<\/code> directory under \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Do I need an Achla account?<\/h3><\/dt>\n
Do I need my own OpenAI or LLM API key?<\/h3><\/dt>\n
Do I need to prepay model tokens?<\/h3><\/dt>\n
Can visitors ask in their own language?<\/h3><\/dt>\n
What happens when I deactivate the plugin?<\/h3><\/dt>\n
What happens when I uninstall the plugin?<\/h3><\/dt>\n
Why is the widget not rendering?<\/h3><\/dt>\n
How does Attach fallback work?<\/h3><\/dt>\n
Does the connector store visitor data in WordPress?<\/h3><\/dt>\n
0.3.5<\/h4>\n\n
\n
0.3.4<\/h4>\n\n
\n
0.3.2<\/h4>\n\n
\n