Achla AI Search – Cited AI Answers from Your WordPress Content

Description

Visitors do not always use the same words you used on the page. They ask a
question in everyday language, use a synonym, or type an acronym you spelled
out somewhere else. Keyword search misses the match even when the answer is
already on your site.

Achla AI Search turns that question into a short answer drawn from your
published content, with numbered links to the pages that support it. Visitors
can ask in their own language and receive the answer in that language.

Achla answers questions about your content. It is not a live chat, helpdesk,
or support inbox.

Free plan: 100 searches a month and 100 indexed pages. No payment card.

What visitors get

• An answer with sources. Instead of another results page, visitors get a
  concise response and links to the pages behind it.
• Meaning, not exact keyword matching. Synonyms, alternative terminology,
  spelled-out acronyms, and plain-language questions can reach the relevant
  content.
• Answers in the visitor’s language. Questions in Hebrew, Arabic, French,
  German, Spanish, and other supported languages receive answers in the same
  language, including right-to-left layout where needed.
• Answers grounded in your pages. Achla is designed not to show an answer
  without citations from your indexed content. When the available pages do
  not provide enough support, it says so.

As with any AI-generated output, visitors should check the cited pages when
accuracy matters.

No API keys or search infrastructure

Achla includes the parts that site owners would otherwise have to assemble
and operate themselves:

• No OpenAI or Gemini key. There is no model-provider account or secret to
  configure, store in WordPress, rotate, or top up.
• No separate token bill. Plans are measured in searches, so you do not
  have to estimate input and output token costs.
• No vector database or search server. There is no indexing
  infrastructure to deploy, size, or maintain.
• The crawler is included. Achla reads permitted public content on your
  site, including PDFs and pages that are not WordPress posts, and maintains
  the search index.

Achla runs the crawling, indexing, and model calls as a managed service. You
install the plugin, connect the site, and choose where the widget appears.

How it works

1. Install and activate the plugin.
2. Select Connect, sign in to Achla, and confirm that you own the site. No key is
   copied into WordPress.
3. Achla reads your permitted public pages and builds the index. The plugin
   shows the connection and indexing status.
4. Choose a placement, preview it, and switch the widget on.

Where it fits best

Achla works on a small site, but its advantage becomes clearer when useful
information is spread across more pages than a visitor can browse:

• technical documentation and knowledge bases
• research groups, laboratories, and institutes
• university departments and faculty sites
• scientific publications, proceedings, and open archives
• medical, legal, and regulatory reference sites
• large catalogs, directories, and databases

Specialized terminology is a natural fit. A visitor can ask about protein
folding when a page discusses conformational dynamics, use a field-specific
name for a method, or enter an acronym that is defined elsewhere on the site.
Achla matches the question to the meaning of the indexed content rather than
requiring the same wording.

Three ways to place it

• Bubble — a floating button in the corner. This is the default and
  requires no page editing.
• Inline — a shortcode or Gutenberg block placed inside your content.
• Attach — connects Achla to an existing search field.

Bubble and Inline work alongside the WordPress search you already have.
Attach lets you reuse the search field already present in your design.

Plans and pricing

• Free — $0. 100 searches a month and 100 indexed pages. No payment card.
  This is an ongoing plan, not a trial that expires.
• Paid plans start at $15 a month and include a fixed number of searches.

Extra usage is purchased in blocks of searches rather than model tokens. That
makes usage easier to understand and budget.

Worth knowing before you install

• An Achla account is required.
• The free plan stops after 100 searches in a month. It cannot overspend or
  charge you automatically.
• The free plan indexes up to 100 pages. On a large site, use it to test one
  section rather than an entire archive.
• Achla indexes only public pages it is permitted to crawl. Content behind a
  login is not indexed.
• The widget displays a “Powered by Achla AI” credit.
• An administrator must connect the site. Moving to a new domain requires
  ownership confirmation again.
• On an HTTP site, the plugin displays a permanent reduced-security warning.
  HTTPS is recommended.
• Colors and styling are configured in the Achla dashboard, not in WordPress.

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.

6. Plugin code updates (self-hosted package only). The self-hosted package
checks signed update metadata at
https://achlaai.com/api/plugin/releases/wordpress and downloads a selected
immutable ZIP from
https://achlaai.com/api/plugin/releases/download/wordpress/…. The
WordPress.org package does not contain this updater and receives code updates
only through WordPress.org.

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