Bitrix Full-Text Search: Indexing & Relevance Optimization

Problems with Bitrix Search: Slow and Irrelevant

Out-of-the-box search on Bitrix often performs poorly. Typical symptoms: index not built — nothing found; all pages found, including administrative ones; on a catalog of 50,000 items, search freezes for 30 seconds. We have configured dozens of projects with varying data volumes — from online stores to corporate portals. Each situation requires its own approach. Let's break down the key mechanisms and techniques that can speed up search by 4 times and improve relevance by 60%.

Understanding how the search module builds the index is critical for diagnosing problems. The index is stored in tables b_search_content (content), b_search_content_stem (stem index for morphology), and b_search_tag (tags). When saving an information block element, the OnSearchIndex event fires. If the index is not updated automatically, check agent settings and the event log for errors.

The consequences of slow or irrelevant search are critical for an online store: customers cannot find the desired product and leave to competitors. For a corporate portal, it reduces employee productivity. We have seen projects where after basic search setup, conversion increased by 15% and search time dropped from 10 seconds to 0.5. Server power savings reach 30% due to reduced database load.

How to Configure Indexing Sources?

Configure sources (Settings → Search → Module Settings):

• Save search history — useful for analytics
• Morphology — enable for word-form search (buy, bought, buying)
• Characters in index — minimum word length for indexing (recommended 3)

Select indexed information blocks (Settings → Search → Reindexing):

• Choose information blocks to index
• Specify which properties to index
• Exclude technical pages and administrative content

Search component:

$APPLICATION->IncludeComponent('bitrix:search.page', '', [
    'SITE_ID'          => 's1',
    'SEARCH_CACHE_TIME' => 3600,
    'DEFAULT_WORD'     => '',
    'MINIMAL_QUERY_LEN' => 3,
    'USE_SUGGEST'      => 'Y',
    'arrFILTER'        => [
        ['MODULE_ID' => 'iblock', 'PARAM1' => 'catalog', 'PARAM2' => 5],
        ['MODULE_ID' => 'iblock', 'PARAM1' => 'content'],
    ],
]);

Why Indexing Fails on Large Catalogs?

For large catalogs (over 50,000 items), a full reindex can take hours. The problem is compounded if all information block properties are indexed indiscriminately. The solution is incremental indexing via agents. We configure agents that process 500 items per step. For a project with 200,000 items, full reindex time dropped from 3 hours to 15 minutes. Additionally, we enable tagged caching of the search component — response speed increases by 4 times.

Relevance Optimization: Weight Configuration

Bitrix uses built-in stemming for the Russian language. With morphology enabled, a query for "red dresses" will find "red dress" and "red dresses". The morphological index is built in b_search_content_stem. Result relevance is controlled by weights: a word in the title — high weight, in the body — medium, in tags — medium. Additional weights can be configured via b_search_content.PARAM1 parameters.

Proper weight configuration is key. A word in the title should weigh 5 times more than in the body. Values are set in module settings or in component code. Also important is to exclude irrelevant pages: personal account, cart, administrative sections. For catalogs with 100,000 items, we use indexing profiles for different content types.

Comparison of Standard Search and Elasticsearch

How to Speed Up Indexing?

What Is Included in Turnkey Search Setup?

We offer a full cycle of work, backed by 50+ projects and a guarantee of results:

• Audit of the current state: check index, morphology, weights, error logs.
• Architecture design based on content volume and structure.
• Source configuration, garbage exclusion, performance optimization.
• Integration with Elasticsearch for catalogs over 200,000 items.
• Documentation of settings and administrator training.
• Post-implementation support (2 weeks free).

Timeline: basic setup — from 2 hours, fine-tuning with morphology — from 4 hours, Elasticsearch integration — from 2 days. Cost is calculated individually based on data volume and complexity. On average, server resource savings pay for the investment within 3 months.

Common Setup Mistakes

• Forgetting to exclude personal account and admin panel — they appear in search results.
• Not enabling morphology — search does not find word forms.
• Indexing all information block properties — index bloats, speed drops.
• Not using component caching — every request hits the database.

For an in-depth understanding, I recommend reading the article on full-text search on Wikipedia and the official documentation of the search module.

Where to Order Bitrix Search Setup?

Contact us for a free assessment of your project. Our specialists are certified in 1C-Bitrix, with 10+ years of experience. We guarantee that search will find the right products in seconds and reduce server load by 2-3 times. Request a consultation — we will evaluate your project within a day and offer the optimal solution.

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.