API Reference / API Parameters / searchableAttributes
Type: list of strings
Engine default: [] (all string attributes)
Formerly: attributesToIndex
Parameter syntax
'searchableAttributes' => [
  'attribute2, attribute3', // both attributes have the same priority

Can be used in these methods:

About this parameter

The complete list of attributes used for searching.

This setting is critical to establishing excellent relevance for two main reasons:

  • It limits the scope of a search to the listed attributes. Defining specific attributes as searchable gives you direct control over what information the search engine should look at. Some attributes contain URLs; others exist for display purposes only. Such attributes are not helpful for searching.
  • It creates a priority order between attributes that the engine uses to improve relevance. The order in which the attributes appear determines their search priority. Records with matches in the first attribute(s) of the list score higher on the attribute criterion than records with matches in the second attribute(s), which score higher than records with matches in the third attribute(s), and so on.

Whenever you change this parameter, the engine rebuilds your entire index. If you need to do near real-time indexing, try not to change the setting during your peak-traffic times.

Usage notes

  • Default/empty list: if you don’t use this setting, or use it with an empty list, the engine searches in all attributes.
  • Ordering: in addition to creating attribute-level priority, you can also determine how the engine searches within an attribute. By default, the engine favors matches at the beginning of an attribute, but you can change it to ignore positioning and consider any match within an attribute of equal importance.
  • Same priority: you can create the same priority for several attributes by setting them in the same comma-separated string. Attributes that are on the same priority as others are always unordered.
  • Nested attributes: when you specify an attribute with nested attributes, the engine indexes them all. If you don’t want to search the entire attribute, you can reference a child attribute (such as categories.lvl0.child_attribute.sub_child_attribute).



Any match anywhere in the attribute has the same weight.

By default, searchableAttributes added from the API are ordered, meaning that matches at the beginning of an attribute are more relevant than matches towards the end. Setting them as unordered makes all matches equal regardless of their position in the attribute.

If you add searchableAttributes through the dashboard, the UI defaults to setting your attribute as unordered (select ordered from the dropdown to change it).

If you set searchableAttributes with the same priority, they’re always unordered.


  'searchableAttributes' => [
Did you find this page helpful?