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.

How to speed up AJAX requests

Under high traffic, AJAX suggestion requests can load the server. Our recommendations:

• Increase SUGGEST_CACHE_TIME to 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.

$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.suggest component 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 arrFILTER with 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

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.