Search presets

A named, reusable bundle of search parameters — which fields to query, which filters to apply, how to sort — so a frontend calls the preset instead of repeating the same options on every request.

A storefront usually runs the same handful of search shapes over and over: a header search box, a category listing, an “in stock only” variant. A preset captures one shape's query_by, filter_by and sort_by options under one name, so the client sends a preset id and a query string instead of the full parameter list every time.

Presets also make relevance changes safe to ship: tune the preset once in the console and every caller picks up the change immediately, with no client deploy and no risk of one integration drifting from another because it hand-copied the old parameters.

Related terms

Collection aliases Faceted search

Test AACSearch on your own problem

The best way to evaluate a search platform isn't reading one more comparison table.

Upload your own data.
Run real queries.
Look at the Query Trace.
Compare relevance.
Work out the cost.

Only then make the decision.

Start free Open Playground See the documentation