Catalog Search Configuration

Parameter	Default value	Description
Category Name Weight	1	The search weight of category names when used in fulltext search.
Redirect to product page if only one result	Yes	If set to yes, the user will be redirected to the product page, if there is only one product matching a given search query
Use URL Rewrites for Category Filter in category navigation	Yes	If set to yes, users are redirected (and all filters are reset) to the chosen category page when they use the category filter in layered navigation.
Expanded facets	3	Number of facets to display expanded by default.
Enable adaptive slider	No	If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range.
Enable indexing child product SKU in dedicated subfield	No	Controls how SKUs of composite products (e.g., configurable or bundle products) are indexed. Yes: Child product SKUs are indexed in a completely separate field, ensuring the main sku field strictly contains the parent’s SKU. This prevents child SKUs from being merged into the parent’s data, which is highly recommended to avoid confusion when building SKU-based widgets. No: Child SKUs are merged with the parent SKU.
Enable indexing discount on child products	No	Enable this setting if your catalog utilizes configurable products where child variants have different prices and independent discount rules. This ensures the search engine accurately indexes and reflects these specific child-level discounts.
Ignore manual positions of out of stock products	No	If your store is configured to display out-of-stock products on the frontend, setting this to Yes ensures that any product manually pinned to a specific position (either in a category or for a specific search query) will automatically lose its pinned position and stop being pushed to the top when it goes out of stock.
Force zero results for disabled categories	Yes	Yes: Ensures that if a Virtual Category uses a disabled category as its root, or specifically references a disabled category within its attribute rules, it will strictly return an empty result. ⚠️ Warning: Modifying this setting will automatically clear your entire category query cache.
Text scoring algorithm for collector fields	Default	Defines the relevance scoring model (or “similarity”) applied to special Elasticsuite collector fields (like the search and spelling fields, which aggregate data from multiple searchable attributes). • Default: Applies the standard algorithm that rewards term frequency (e.g., a product containing the word “dress” 3 times in its data will score higher than a product containing it only once). • Boolean: Applies a strict boolean model where multiple occurrences do not increase the score. A product with the word “dress” 3 times will receive the exact same score as a product with “dress” only once.

Explicit URL rewrites support

By default, to maximize indexing performance, Elasticsuite reconstructs category and product URLs on the fly using their indexed url_key or url_path combined with your configured URL suffix. This relies on Magento automatically creating 301 redirects whenever a URL key changes. However, if you frequently disable automatic redirects, or if URLs are heavily modified for SEO purposes (manually or via third-party modules), users might click an autocomplete suggestion only to land on a 404 error page. This is especially common for categories that are frequently renamed or moved. The settings below solve this issue by forcing Elasticsuite to explicitly read Magento’s native URL Rewrites table during indexing to fetch the exact, current URL. ⚠️ Trade-off: Enabling this will cause a slight increase in category indexing time, and a slight to moderate increase in product indexing time (depending on the size of your catalog).

Parameter	Default value	Description
Enabled for categories	Yes	Yes: During indexing, Elasticsuite explicitly fetches the exact, current category URL directly from the Magento URL Rewrites table (Marketing > SEO & Search > URL Rewrites) to ensure autocomplete links are strictly accurate. No: Legacy behavior. The category URL is quickly reconstructed using its indexed url_key/url_path and the URL suffix.
Enabled for products	No	Yes: During indexing, Elasticsuite explicitly fetches the exact, current product URL directly from the Magento URL Rewrites table to ensure autocomplete and Instant Search links are strictly accurate. No: Legacy behavior. The product URL is quickly reconstructed using its indexed url_key/url_path and the URL suffix.

Catalog Rules Configuration

Parameter	Default value	Description
Alphabetical sorting of attribute options in the rule engine	No	By default, options for select and multiselect attributes are displayed in the order they were originally created in Magento. Setting this to Yes forces the system to sort these option labels alphabetically when they appear in the rule engine (used for configuring Virtual Categories and Search Optimizers). This is highly recommended if your catalog features attributes with a very long list of options (e.g., a “Brand” attribute with hundreds of values), as it makes finding and selecting the right option much easier.