Use case · Site search
Better site search this afternoon, not next quarter.
Connect the catalogue or crawl the site, mint a session token on your server and drop in one script. The search box, facets, typo tolerance and analytics come with it.
What you replace
Exact-match search
Built-in CMS search matches whole words. AACSearch adds prefix search from the first letter and typo tolerance, while keeping model numbers exact.
No filters
Product properties become facets with live counts, including numeric ranges and category trees.
Empty result pages
A ladder of rewrites — learned corrections, layout fix, transliteration, wider typo tolerance — runs before an empty page is shown.
Blind spots
Top queries, queries with no results, clicks and slow queries per index, so you know what visitors look for.
How data gets in
From the CMS
Connectors for 1C-Bitrix, Shopify and WordPress read products and pages on a schedule.
From a feed or the site itself
Import JSON or CSV, or crawl a sitemap and split pages by headings.
Specifications
- Time to first results
- usually under an hour
- Widget size
- one script tag
- Browser credentials
- 15-minute session token, never an API key
- Click tracking
- automatic
Before you start
- A data source (feed, sitemap or CMS)
- A place in your templates for the search box
- One backend endpoint that mints the session token
How to start
- 1
Create an index
In the console, create an index and choose a starting profile; field roles are suggested from your data.
- 2
Load data
Add a connector or upload a file. The first sync usually takes minutes.
- 3
Mint a session token on your server
The browser never sees an API key: your backend exchanges it for a short-lived token scoped to searching one index.
POST /api/v1/embed/session Authorization: Bearer aac_live_… { "index": "products" } - 4
Embed the widget
Add one script with the token. Clicks and impressions are tracked automatically.
<div id="aacsearch"></div> <script src="https://app.example.com/embed/v1/aacsearch.js" data-aac-token="SESSION_TOKEN" data-aac-target="#aacsearch"></script>