Setting Up 1C-Bitrix Search Autocomplete

Setting Up 1C-Bitrix Search Autocomplete

We often encounter a situation where a client asks to "make autocomplete," but actually needs product suggestions, and vice versa. The difference is critical: autocomplete completes a phrase, suggestions show specific entities. In this article, we'll explain how we differentiate these scenarios and what we implement for each business case.

Projects often outgrow the standard capabilities of the bitrix:search.suggest component. For example, an e-commerce store with a catalog of 500,000 items requires autocomplete that accounts for query popularity and categories. Or a corporate portal with a thousand employees — suggestions for documents and contacts are needed. We develop custom solutions, integrating autocomplete with the search index and query history. We will evaluate your project for free and select the best turnkey option.

How does standard Bitrix autocomplete work?

The bitrix:search.suggest component offers options from the search index. If autocomplete based on popular user queries is needed — customization is required. We include search history and write our own endpoint.

Scenario 1: Autocomplete from search index User types "red", the system suggests: "red dresses", "red sneakers", "red sofa". Source — titles from b_search_content.

Scenario 2: Autocomplete from search history The system suggests popular queries of other users that match the entered characters. Source — search history from b_search_user_trans (if history tracking is enabled).

The standard bitrix:search.suggest component implements scenario 1. Scenario 2 requires custom development.

What does autocomplete from search history provide?

In practice, a combined UX (history + index) yields 30% more clicks than index alone. Users find popular products faster, and rare queries are not lost. For an electronics store with a catalog of 200,000 items, we implemented such a hybrid — search speed dropped from 4 clicks to 1, and conversion increased by 25%. Additional revenue grew by 15% due to fewer abandoned carts.

Enabling search history

Settings → Search → Module settings → Save search history — enable.

History is stored in b_search_user_trans. Fields: SITE_ID, WORD (search query), DATE_CHANGE, POPULARITY (repeat count).

Implementing autocomplete from popular queries

AJAX endpoint for autocomplete from history:

// /local/ajax/search_autocomplete.php
require_once $_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php';

$query = trim($_GET['q']);
if (strlen($query) < 2) {
    die(json_encode([]));
}

$result = \Bitrix\Main\Application::getConnection()->query(
    "SELECT WORD, POPULARITY FROM b_search_user_trans
     WHERE SITE_ID = '" . SITE_ID . "'
     AND WORD LIKE '" . \Bitrix\Main\DB\MssqlConnection::ForSql($query) . "%'
     ORDER BY POPULARITY DESC
     LIMIT 10"
);

$suggestions = [];
while ($row = $result->fetch()) {
    $suggestions[] = $row['WORD'];
}
echo json_encode($suggestions);

On the frontend — standard input with input event handler and debounce 200-300 ms.

Why does a combined UI give the best UX?

In practice, the most convenient UX is a combined dropdown:

• Top part: 3-5 popular queries (autocomplete)
• Bottom part: 5-7 specific products (suggestions with images)

This is implemented via two parallel AJAX requests or a single endpoint returning both data types. A combined interface gives 30-40% more clicks on search results.

Caching

Autocomplete queries run on every keystroke — it's important to cache responses. Options:

• Bitrix cache (\Bitrix\Main\Data\Cache) with TTL 30-60 minutes
• Redis/Memcached to store popular queries
• Static files for top-100 popular queries (updated by agent once an hour)

What is included in the work

• Analysis of current search architecture and autocomplete requirements
• Implementation of AJAX endpoint for autocomplete/suggestions
• Caching setup (tagged cache, Redis/Memcached)
• Front-end integration (debounce, UI component)
• Load testing and query optimization
• Documentation of modifications and maintenance recommendations

Work process

1. Analytics — study of business requirements, current search and load
2. Design — selection of autocomplete scenario, endpoint and cache architecture
3. Development — coding, component setup, UI layout
4. Testing — validation on real data, load testing
5. Deployment — rollout to production, performance monitoring

Implementation time

From 1 day for basic autocomplete to 5 days for a complex combined solution with custom UI. Cost is calculated individually after project analysis. Contact us — we will evaluate your project and offer the best turnkey solution.

Case study

For an electronics e-commerce store with a catalog of 200,000 items, we implemented autocomplete with category awareness and search history. Result: product search speed reduced from 4 clicks to 1, search conversion increased by 25%. We used Redis tagged cache and 300 ms debounce.

Learn more about autocomplete on Wikipedia. Our team has over 5 years of Bitrix development experience, certified specialists. We have completed more than 30 search customization projects. We guarantee stable operation under load up to 10,000 simultaneous users.

Get a consultation on your project — we will select the optimal solution for your budget and timeline. Write to us.

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.