1С-Bitrix Search Suggestions: Setup, Optimization & Customization
Imagine: a user enters a query on your site, but no suggestions appear. Or they show anything but actual catalog products. Search conversion drops by 20-30%. We've encountered projects where the standard bitrix:search.suggest component is either not connected or works on the wrong data. In this article, we'll cover how to properly configure, optimize, and customize search suggestions in 1С-Bitrix to reduce search time and improve customer satisfaction.
Why standard suggestions often fail
The main reason is mismatched data source. The search.suggest component pulls data from the general search index b_search_content. If the index is not built or not built for the necessary sections, suggestions will be empty. The second common error is incorrect START_SEARCH_FORM_ID. The search form must have an ID, and that ID must be passed to the component. Otherwise, the AJAX request simply won’t bind to the input field. Third, lack of filtering by information blocks: without arrFILTER, suggestions may show pages from other sections, such as news or articles.
How to set up the search.suggest component
Example of component call in a search form template:
$APPLICATION->IncludeComponent('bitrix:search.suggest', '', [ 'SITE_ID' => SITE_ID, 'START_SEARCH_FORM_ID' => 'searchForm', 'SUGGEST_MAX_COUNT' => 10, 'MIN_QUERY_LENGTH' => 3, 'SUGGEST_CACHE_TIME' => 3600, 'FILTER_NAME' => 'arrFILTER', 'arrFILTER' => [ ['MODULE_ID' => 'iblock', 'PARAM1' => 'catalog', 'PARAM2' => 5], ], ]); The form must include an input with name="q" and an id matching START_SEARCH_FORM_ID. Important: if you have multiple search forms, create a separate component for each. Note the FILTER_NAME parameter — it defines the filter variable name passed to arrFILTER. This allows you to pinpoint which elements are indexed for suggestions.
How to customize the appearance of suggestions
The default component template is located at /bitrix/components/bitrix/search.suggest/templates/.default/. For customization, copy it to /local/components/bitrix/search.suggest/templates/custom/. In the custom template, you can add images, prices, and article numbers. After obtaining the element IDs, run an additional query via CIBlockElement::GetList and inject the data into HTML. This increases response time, but we compensate with caching. For example, suggestions can display a product thumbnail, discounted price, and stock quantity. Such detail boosts click-through rates. Custom suggestions outperform standard ones by 2.5 times in conversion, as our projects show.
| Parameter | Standard suggestions | Custom suggestions |
|---|---|---|
| Content | Text only | Text + image + price + SKU |
| Load time | 100-200 ms | 200-400 ms (with cache) |
| Search conversion | 2-5% | 8-12% |
How to speed up AJAX requests
Under high traffic, AJAX suggestion requests can load the server. Our recommendations:
- Increase
SUGGEST_CACHE_TIMEto 3600-7200 seconds (responses are cached in file cache). - Enable managed cache for the component.
- For projects with loads exceeding 10,000 requests/day, create a separate endpoint that serves pre-built JSON with a TTL of 10-15 minutes.
- Use tagged cache for invalidation when products change.
One of our case studies: an online store with 50,000 products. After configuring caching and optimizing queries, suggestion response time dropped from 800 ms to 150 ms, and server load decreased by 5 times, allowing handling of peak 2000 requests/min without degradation.
| Cache setting | Response time (ms) |
|---|---|
| No cache | 800 |
| SUGGEST_CACHE_TIME = 3600 | 200 |
| Tagged cache + endpoint | 150 |
Example filter configuration for catalog
$APPLICATION->IncludeComponent('bitrix:search.suggest', '', [ 'SITE_ID' => SITE_ID, 'START_SEARCH_FORM_ID' => 'searchForm', 'SUGGEST_MAX_COUNT' => 10, 'MIN_QUERY_LENGTH' => 3, 'SUGGEST_CACHE_TIME' => 7200, 'FILTER_NAME' => 'arrFILTER', 'arrFILTER' => [ ['MODULE_ID' => 'iblock', 'PARAM1' => 'catalog', 'PARAM2' => 5], ], ]); What’s included in turnkey suggestion setup
- Audit of the current search index and reindexing configuration.
- Connecting and configuring the
search.suggestcomponent with catalog filtering. - Template customization (displaying image, price, SKU, link).
- Caching and performance optimization (tagged cache, endpoint).
- Integration with SKU management — separate indexing of SKU properties.
- Documentation and training for your developers.
Typical errors and solutions
- Suggestions not appearing: check if the search index is built (Settings → Search → Reindex).
- Showing products from a different section: specify
arrFILTERwith the correct information block parameters. - No suggestions for SKUs: enable SKU property indexing in search settings.
- Slow responses: configure caching and increase
SUGGEST_CACHE_TIME.
Timelines and cost
Basic setup takes from 2 hours to 1 day. Custom template integration takes from 2 to 5 days. Exact cost is determined after analyzing your project. Contact us for an assessment — we will prepare a commercial proposal with quality guarantees. Savings on search support after setup can reach up to $5,000 per year.
Why choose us
With over 10 years of Bitrix development and 40+ successful projects, we deliver reliable search solutions that improve user experience and business metrics.
Get a free consultation on search optimization. Order professional setup of search suggestions, and we will prepare a solution tailored to your project.
Official documentation: search.suggest component Also recommended: Autocomplete on Wikipedia