Title: AuditAE AI Search Toolkit
Author: aaronkaltman
Published: <strong>June 24, 2026</strong>
Last modified: June 24, 2026

---

Search plugins

![](https://ps.w.org/auditae-ai-search-toolkit/assets/icon-256x256.png?rev=3584668)

# AuditAE AI Search Toolkit

 By [aaronkaltman](https://profiles.wordpress.org/aaronkaltman/)

[Download](https://downloads.wordpress.org/plugin/auditae-ai-search-toolkit.0.19.3.zip)

 * [Details](https://wordpress.org/plugins/auditae-ai-search-toolkit/#description)
 * [Reviews](https://wordpress.org/plugins/auditae-ai-search-toolkit/#reviews)
 *  [Installation](https://wordpress.org/plugins/auditae-ai-search-toolkit/#installation)
 * [Development](https://wordpress.org/plugins/auditae-ai-search-toolkit/#developers)

 [Support](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/)

## Description

AuditAE bundles the practical wins of “AEO” (Answer Engine Optimization / AI search)
into one free plugin. Everything works the moment you activate, with zero signup.

**AI Readiness Score.** One 0–100 number, with a letter grade, that summarizes how
ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, and Google
AI Overviews — computed entirely from local signals (are citation bots blocked in
robots.txt, FAQ and Article schema coverage, Organization schema, unresolved AI-
bot 404s, content freshness, llms.txt). Every check that isn’t passing shows exactly
what to fix and how many points it’s worth, and the score tracks a 7-day delta so
you can see it climb as you ship fixes. Surfaced on its own tab and on the wp-admin
Dashboard widget.

**1. AI Crawler Tracker.** Identifies hits from ~30 AI search-engine crawlers — 
GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Perplexity-
User, Google-Extended, Applebot-Extended, Bytespider, CCBot, Meta-ExternalAgent,
Bingbot, and more. Get a real-time count of AI bot hits over the last 30 days, a
by-bot breakdown with time-since-last-hit per bot, a per-day activity table, top
crawled paths, one-click CSV export, and an at-a-glance wp-admin Dashboard widget.
A built-in **robots.txt audit** flags any tracked AI bot your robots.txt is blocking—
the silent killer of AI visibility. Answers the question Google Search Console can’t:_“
Are AI engines actually reading my site?”_

**2. llms.txt Generator.** Serves a live `/llms.txt` file at the root of your site,
conforming to the [llmstxt.org](https://llmstxt.org) spec — a markdown manifest 
that helps LLM-powered tools find the right pages on your site. Builds defaults 
automatically from your public post types, with per-section customization, optional
links list, and a one-click “Reset to defaults” if you want to start fresh.

**3. Schema Graph.** Per-post and site-wide schema.org JSON-LD injection. Add structured
data for Organization, Article, Product, HowTo, FAQPage, BreadcrumbList — all linked
together by `@id` so AI engines can resolve “this org wrote this article” without
guessing. Plays nicely alongside Yoast and Rank Math (we reuse their `@id`s when
present instead of duplicating).

**Plus FAQ schema injection.** A `<script type="application/ld+json">` block on 
singular post views, sourced from question/answer pairs stored in post_meta. Post
content is not modified.

No external service is required for any of the above. All data is stored locally
in your `wp_options` table (rolling 500-entry crawler log, no custom database tables,
no telemetry).

**Optional — pair with AuditAE (auditae.app).** AuditAE is a separate paid service
that measures whether AI engines _cite_ your brand for the prompts your buyers ask.
Pairing this plugin with an AuditAE account lets the AuditAE assistant (AEBOT) also
draft posts, update existing posts, edit Yoast/Rank Math meta, manage the schema
graph, and curate `/llms.txt` for you. Pairing is fully optional; everything above
remains free regardless. $5 free credit at signup, no subscription.

### External Services

This plugin can connect to one external service, and only when you opt in.

**AuditAE (https://auditae.app)** — _Optional, opt-in only._
 The free features (
crawler tracker, llms.txt, schema graph, FAQ schema) do **not** call any external
service. The plugin only contacts AuditAE if you explicitly use the “Connect to 
AuditAE” tab to pair the site. When paired, the AuditAE service sends authenticated
REST API requests to this site (over HTTPS, with a per-site bearer token you can
revoke from the admin) to read posts, write drafts, manage schema, or update SEO
metadata — only for the capabilities you grant. The plugin itself does not send 
analytics, telemetry, or usage data to AuditAE.

 * Terms of service: https://auditae.app/terms
 * Privacy policy: https://auditae.app/privacy

The admin UI uses the Instrument Serif typeface, which is **bundled locally** in`
assets/fonts/` under the SIL Open Font License 1.1. No font requests are made to
Google or any third party.

## Screenshots

[⌊The AI Readiness Score — one 0–100 score with a letter grade and a 7-day trend
for how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, 
and AI Overviews, with a one-click fix on every check.⌉⌊The AI Readiness Score —
one 0–100 score with a letter grade and a 7-day trend for how ready your site is
to be read and cited by ChatGPT, Perplexity, Gemini, and AI Overviews, with a one-
click fix on every check.⌉[

The AI Readiness Score — one 0–100 score with a letter grade and a 7-day trend for
how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, and 
AI Overviews, with a one-click fix on every check.

[⌊The AI Crawlers tab — which AI bots are reading your site, plus a robots.txt audit
that flags when you're blocking citation engines like GPTBot, ClaudeBot, or PerplexityBot.⌉⌊
The AI Crawlers tab — which AI bots are reading your site, plus a robots.txt audit
that flags when you're blocking citation engines like GPTBot, ClaudeBot, or PerplexityBot
.⌉[

The AI Crawlers tab — which AI bots are reading your site, plus a robots.txt audit
that flags when you’re blocking citation engines like GPTBot, ClaudeBot, or PerplexityBot.

[⌊The Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-LD
block (and per-post Article/Product/FAQ schema), working alongside Yoast and Rank
Math.⌉⌊The Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-
LD block (and per-post Article/Product/FAQ schema), working alongside Yoast and 
Rank Math.⌉[

The Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-LD block(
and per-post Article/Product/FAQ schema), working alongside Yoast and Rank Math.

## Installation

 1. Install and activate the plugin.
 2. Go to **Settings  AuditAE**. You’ll land on the AI Crawlers tab. As AI bots crawl
    your site, hits will populate the dashboard automatically.
 3. Visit the **llms.txt** tab to review or edit the manifest served at `https://example.
    com/llms.txt`.
 4. (Optional) Visit the **Connect to AuditAE** tab to pair with an AuditAE account
    if you want the citation-audit and AEBOT writing features.

## FAQ

### Do I need an AuditAE account to use the plugin?

No. The Crawler Tracker, llms.txt generator, schema graph, and FAQ schema are all
fully free and standalone. They work the moment the plugin is activated. The Connect
to AuditAE tab is optional and only relevant if you want the paid citation-audit
+ AEBOT writing features.

### Which AI bots does the Crawler Tracker identify?

GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Claude-
Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended,
Bytespider, CCBot, cohere-ai, Diffbot, FacebookBot, Meta-ExternalAgent, Meta-ExternalFetcher,
Bingbot, YouBot, Amazonbot, DuckAssistBot, PetalBot, TimpiBot, MistralAI-User, AI2Bot,
iaskspider, AwarioRssBot, AwarioSmartBot, plus a few others. The list is curated
to AI engines; we deliberately exclude Googlebot because that’s already covered 
by Google Search Console.

### Will the plugin slow down my site?

No. Crawler detection is a single substring scan of the User-Agent on `template_redirect`,
and the write to `wp_options` is bounded to 500 entries (oldest entries are pruned).
The `/llms.txt` response is cached in a transient and regenerated only when you 
save changes. Schema injection runs once per page render in `wp_head`. On any reasonable
host, the per-request cost is well under a millisecond.

### Where is data stored?

Locally, in your site’s `wp_options` table. Keys: `auditae_crawler_log` (rolling
hit log), `auditae_crawler_stats` (per-day / per-bot counters, bounded to 90 days),`
auditae_redirects` (redirect rules), `auditae_audit_log` (action log for the optional
Connect tab), `auditae_llms_txt_config` (llms.txt manifest), `auditae_organization_schema`(
site-wide schema), plus per-post meta `_auditae_schema_graph` (per-post schema) 
and `_auditae_faq_schema` (per-post FAQ Q&A). No custom database tables. No telemetry.
No data leaves your site unless you opt in to pairing with AuditAE.

### Does the schema graph conflict with Yoast or Rank Math?

No. If Yoast or Rank Math is active and emitting their own JSON-LD, AuditAE detects
their `@id` values and links to them instead of duplicating Organization/WebSite
nodes. You can layer AuditAE’s per-post schema on top of any SEO plugin.

### What does the AuditAE connection cost?

Pairing is free. AuditAE itself is pay-per-use ($0.05 per AI-engine prompt check,
$0.05 per WordPress mutation action) with $5 free credit at signup, no subscription.
Sign up at https://auditae.app.

### How do I revoke the AuditAE connection?

Settings  AuditAE  Connect to AuditAE tab  Disconnect. The bearer token is wiped
instantly.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“AuditAE AI Search Toolkit” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ aaronkaltman ](https://profiles.wordpress.org/aaronkaltman/)

[Translate “AuditAE AI Search Toolkit” into your language.](https://translate.wordpress.org/projects/wp-plugins/auditae-ai-search-toolkit)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/auditae-ai-search-toolkit/),
check out the [SVN repository](https://plugins.svn.wordpress.org/auditae-ai-search-toolkit/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/auditae-ai-search-toolkit/)
by [RSS](https://plugins.trac.wordpress.org/log/auditae-ai-search-toolkit/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.19.3

 * Branding: the admin screen now shows the new AuditAE logo and green accent so
   it matches the WordPress.org listing. No functionality change.

#### 0.19.2

 * Compliance: changed the text domain to “auditae-ai-search-toolkit” to match the
   plugin slug, per WordPress.org plugin review. No functionality change.

#### 0.19.1

 * Compliance: shortened the display name to “AuditAE AI Search Toolkit” per WordPress.
   org plugin review. No functionality change.

#### 0.19.0

 * New: **AI Readiness Score streak** — a 🔥 flame appears once your score has climbed
   two or more readings in a row, on the Score tab, the wp-admin Dashboard widget,
   and the Score nav chip. Completes the score + 7-day-delta + streak momentum loop,
   so the number is worth coming back to.
 * Improved: the “AI crawlers are reading your site” check is no longer a dead end
   when no bot has visited yet — it now offers a fix that asks AEBOT for the concrete
   steps to get discovered (and run a live citation audit on paired sites), so every
   not-passing check stays actionable.

#### 0.18.1

 * Compliance: sanitize the Organization-schema `sameAs` and redirect `source`/`
   destination` admin form inputs at the point of access (WordPress.org Plugin Check).
   No behavior change — values were already sanitized downstream.
 * Compliance: bumped “Tested up to” to WordPress 7.0 and trimmed the short description
   to the 150-character limit.

#### 0.18.0

 * New: **AI Readiness Score** — a 0–100 score with a letter grade that summarizes
   how ready your site is to be read and cited by AI engines, computed entirely 
   from local signals (no account or external call beyond the existing hourly robots.
   txt fetch). Eight weighted checks: citation bots allowed in robots.txt (20), 
   FAQ schema coverage (16), Organization schema (12), Article/Product schema coverage(
   12), unresolved AI-bot 404s (12), AI crawlers actually reaching the site (12),
   llms.txt served (8), and content freshness (8). Each check shows its status, 
   points, a one-line explanation, and a direct “fix” link.
 * New: the Score is the new default landing tab and shows a **7-day delta** (“▲
   +6 points in the last 7 days”) plus a “N points to grade B” target, from a bounded
   daily score history kept locally. The wp-admin Dashboard widget now leads with
   the score + delta.
 * New: every not-yet-passing check links to the fix — robots.txt/redirects/schema/
   llms.txt checks deep-link to the right settings tab; schema, FAQ, and freshness
   checks offer to hand the work to AEBOT (paired sites) or prompt you to connect(
   unpaired). On paired sites the AEBOT links carry the exact task, so the assistant
   opens with the fix already requested.

#### 0.17.0

 * New: **robots.txt audit** on the AI Crawlers tab. Fetches your site’s robots.
   txt and classifies every tracked AI bot as allowed, limited, or blocked — with
   a red callout when a citation engine (GPTBot, ClaudeBot, PerplexityBot, Bingbot,…)
   is blocked outright. A stale `Disallow` aimed at scrapers routinely takes citation
   bots down with it, and from the outside that looks identical to “AI just doesn’t
   cite me”. Re-checked hourly; also exposed to paired accounts at `GET /auditae/
   v1/robots-audit` (read capability).
 * New: persistent crawler statistics. The rolling 500-entry log only spans a few
   days on a busy site, so 30-day totals, by-bot counts, and “since last hit” silently
   undercounted or went stale once entries were pruned. The tracker now also keeps
   compact per-day per-bot counters (90 days, one wp_options row) plus an exact 
   per-bot last-seen timestamp that never falls out of the window.
 * New: the By bot breakdown now shows **when each bot last hit** (“3 hours ago”),
   not just a count — and a Daily activity table shows per-day hits for the last
   14 days.
 * New: wp-admin **Dashboard widget** — 30-day AI hit count, distinct bots, last-
   hit recency, and the top three bots, without opening Settings  AuditAE.
 * New: **Export log as CSV** button on the AI Crawlers tab (timestamp, bot, path,
   status).
 * New: the llms.txt tab now edits the **Optional links** section (enable toggle,
   title, one link per line as `Title | URL | description`) — previously this was
   only reachable via the REST API.
 * Fix: corrected a stale docblock in the redirect handler that still described 
   the pre-0.15.1 hook ordering.

#### 0.16.0

 * Security: capability-consent hardening on three REST surfaces. (1) `PATCH /media/{
   id}` (alt text + caption) now requires the `write_seo` capability as documented—
   it was previously reachable with read-only consent because the action-dispatch
   permission gate fell through to `read` on routes with no `action` param. (2) `
   POST /llms-txt` with `action=write`, `action=reset`, or no action now requires`
   write_seo`; previously `reset` and a missing action slipped through the read 
   gate, letting a read-only token rewrite or reset the manifest. (3) Updating a
   post that is already published (`PATCH /posts/{id}` and `POST /posts/{id}/internal-
   link`) now requires the `publish` capability — `draft` consent (“create and update
   draft posts”) no longer allows changing live content. The bearer token still 
   gates everything; this tightens what each granted capability permits.
 * The Permissions card now labels `publish` as “Publish posts and edit already-
   published content” to match the enforced behavior. If AEBOT reports a missing`
   publish` capability after this update, grant it from Settings  AuditAE  Connect.
 * Fix: deleting the plugin now also removes the `auditae_redirects` option — redirect
   rules were the one key uninstall.php left behind.
 * Fix: the “Redirect to” field in the suggested-redirects table rejected relative
   destinations like `/new-path` (it was a `url`-type input, so browsers demanded
   an absolute URL). Now a text field, matching the manual-add form.
 * Crawler tracker: added Claude-User and Claude-SearchBot (Anthropic’s current 
   fetcher user-agents — previously only ClaudeBot/Claude-Web were detected), MistralAI-
   User (Mistral’s Le Chat fetcher), and AI2Bot to the signature list.

#### 0.15.1

 * Fix: bot hits to URLs that had a matching 404301 redirect rule were being silently
   dropped from the AI crawler log. The redirect handler was hooked on `template_redirect`
   at priority 0 and called `exit` before the crawler logger (priority 1) could 
   run, so the AI Crawlers tab’s “since last hit” stat stayed stale while bots actively
   pinged redirected paths. The logger now runs first (priority 1) and the redirect
   handler runs after (priority 2). Hits to paths with an active redirect rule are
   stamped with the rule’s status (301/302) instead of 404, so the suggested-redirects
   rollup (which keys on status=404) keeps working unchanged.

#### 0.15.0

 * New REST surface for the 404  301 redirect manager: `GET /auditae/v1/redirects`(
   list rules) + `POST /auditae/v1/redirects` (dispatches on `action`: `list` | `
   suggest` | `write` | `delete`). The `suggest` action wraps the same “AI bots 
   404’d here” rollup the admin tab uses, so paired AuditAE accounts can ask AEBOT_“
   check my redirect suggestions”_ and the assistant returns the same one-click 
   proposals the human-facing tab shows. `write` and `delete` are gated by the `
   write_seo` capability and write to the existing `auditae_audit_log` so every 
   bot-initiated rule change is auditable from the admin tab.
 * No behavior change for the human-facing admin tab — same storage, same matcher,
   same template_redirect hook. Drop-in upgrade from 0.14.x, no re-pair required.

#### 0.14.0

 * New **Redirects** admin tab. Wired to the AI crawler log: shows paths that AI
   bots (GPTBot, ClaudeBot, PerplexityBot, etc.) hit and got a 404, with a one-click
   form to add a 301 to wherever the content actually lives now. Rules only fire
   on 404s, so they can never hijack a real page. Also includes a manual add form(
   301 or 302) and an active-redirects table with per-rule hit counters + “last 
   hit” timestamps. Same wp_options storage pattern as the rest of the plugin — 
   no new tables.

#### 0.13.0

 * New **Schema** admin tab: build site-wide Organization JSON-LD from a small form(
   name, URL, logo, description, sameAs). Renders on every front-end page so AI 
   engines can resolve “what brand is this site?” without an LLM call. Same shape
   AuditAE’s hosted Schema Generator emits.

#### 0.12.3

 * Plugin Check follow-up: `$_POST['sections']` in the llms.txt save handler now
   flows through `map_deep( …, 'sanitize_text_field' )` so every leaf value is sanitized
   before the per-field casts run. No behavior change.

#### 0.12.2

 * WordPress.org Plugin Check pass: hardened JSON-LD output (`JSON_HEX_TAG|JSON_HEX_AMP`)
   so `</script>` breakouts are impossible, ran every `$_SERVER` and `$_POST` field
   through `wp_unslash()` + a sanitizer, replaced `unlink()` with `wp_delete_file()`,
   removed the redundant `load_plugin_textdomain()` call (WP auto-loads since 4.6),
   and aligned the plugin header with the directory title. No behavior changes.

#### 0.12.1

 * WordPress.org submission readiness: bundled the Instrument Serif font locally(
   SIL OFL 1.1) instead of loading it from Google Fonts, so the admin UI makes no
   third-party requests. Added a translation template at `languages/auditae.pot`.

#### 0.12.0

 * New: Media library REST endpoints (`GET /media`, `GET /media/{id}`, `PATCH /media/{
   id}`, `POST /media`). Paired AuditAE accounts can audit images with empty alt
   text, write descriptive alt + caption in bulk (gated by `write_seo`), and sideload
   generated hero images from a URL for AEBOT-drafted posts (gated by `draft`).
 * New: Internal-link graph endpoints (`GET /links/graph`, `GET /links/post/{id}`).
   Surfaces per-post incoming/outgoing counts and orphan posts so AEBOT can recommend
   where to weave new internal links.
 * New: `POST /posts/{id}/internal-link` — safe text-replace link insertion. Wraps
   the first unlinked occurrence of an anchor in `<a>` without rewriting the rest
   of the post. Refuses external URLs. Returns previous_state for undo. Gated by
   the same `draft`/`publish` rule as `wp_update_post`.
 * Fix: `/llms.txt` Sections editor table layout. The “On” column header was crashing
   into “Section title” because the table inherited the activity-log fixed layout.

#### 0.11.0

 * New: `/llms.txt` generator. Serves a markdown manifest at the site root following
   the llmstxt.org spec. Defaults are auto-built from your public post types; a 
   new admin tab lets you customize the H1, blockquote intro, per-section titles,
   and an optional links section. Cached in a transient and regenerated on save.
 * Three matching REST endpoints (`GET /llms-txt`, `POST /llms-txt`, `POST /llms-
   txt/reset`) so paired AuditAE accounts can curate the manifest from chat. Gated
   by the `write_seo` capability.

#### 0.10.0

 * New: Schema Graph. Per-post JSON-LD (Article, Product, HowTo, BreadcrumbList)
   stored in `_auditae_schema_graph` post_meta and emitted in `wp_head`. Site-wide
   schema (Organization, WebSite) stored in `auditae_organization_schema`. All nodes
   linked by `@id` so AI engines resolve relationships without guessing. Detects
   and reuses Yoast/Rank Math `@id` values when present.
 * REST endpoints: `POST /posts/{id}/schema`, `POST /organization-schema`, `GET /
   probe-schema`. Gated by `write_seo`.

#### 0.9.0

 * WordPress.org submission prep: `uninstall.php` cleans up every option, transient,
   and per-post meta key on plugin delete. `load_plugin_textdomain` registered on`
   init` and visible admin strings wrapped in `__()` / `esc_html__()` so translations
   can ship without code changes.

#### 0.8.0

 * Reorganized admin into tabs. The AI Crawlers tab is the default landing surface;
   the AuditAE pairing flow moved to its own tab. Reinforces that the crawler tracker
   works without an AuditAE account.

#### 0.7.0

 * New: AI Crawler Tracker. Logs hits from ~27 AI bots on every front-end request
   and surfaces summary, by-bot counts, and top paths on the admin dashboard. Rolling
   500-entry log in wp_options — no custom tables, no telemetry, no external calls.
 * New REST endpoint `GET /auditae/v1/crawler-hits` (gated by the existing `read`
   capability) so paired AuditAE accounts can ingest the log into AEBOT.

#### 0.6.0

 * Branded admin UI. Settings  AuditAE uses the AuditAE visual language (terracotta
   accent, serif headings, card-based layout). CSS is scoped to the AuditAE screen
   so the rest of wp-admin is untouched.

#### 0.5.0

 * FAQ JSON-LD schema injection via new `POST /posts/{id}/faq-schema` endpoint. 
   Stores question/answer pairs in post_meta and emits a schema.org/FAQPage `<script
   type="application/ld+json">` block in `<head>` on singular post views. Post content
   is NOT modified. Capped at 25 Q&A pairs per post; gated by the `write_seo` capability.

#### 0.4.0

 * `GET /posts` — list recent posts with pagination, status filter, search, and 
   post_type. `GET /posts/{id}` — full post snapshot including per-post SEO meta
   for Yoast + Rank Math. Both require the `read` capability.

#### 0.3.0

 * HTTPS enforced on `/pair` and every bearer-protected route. Local dev installs
   can opt out with `define('AUDITAE_ALLOW_INSECURE', true)`.
 * `/pair` brute-force lockout (10 failed attempts in 10 minutes  429).
 * Drafts now authored by the admin who generated the pairing code, not user 0.
 * Create + update now accept excerpt, slug, categories, tags, featured_image_id.

#### 0.2.0

 * Per-post SEO meta editing for Yoast SEO and Rank Math via `/posts/{id}/seo`. 
   Generic post meta passthrough now rejects SEO-prefixed keys so the `write_seo`
   consent boundary holds.

#### 0.1.0

 * Initial release: pairing flow, `/status`, `/posts` (create + update), `/seo/yoast/
   settings`, `/audit-log`, `/disconnect`.

## Meta

 *  Version **0.19.3**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.0**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [AI](https://wordpress.org/plugins/tags/ai/)[ai search](https://wordpress.org/plugins/tags/ai-search/)
   [gptbot](https://wordpress.org/plugins/tags/gptbot/)[llms.txt](https://wordpress.org/plugins/tags/llms-txt/)
   [seo](https://wordpress.org/plugins/tags/seo/)
 *  [Advanced View](https://wordpress.org/plugins/auditae-ai-search-toolkit/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/reviews/)

## Contributors

 *   [ aaronkaltman ](https://profiles.wordpress.org/aaronkaltman/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/)