How to Set Up Yandex.Turbo Pages for a 1C-Bitrix Online Store

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
How to Set Up Yandex.Turbo Pages for a 1C-Bitrix Online Store
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    694
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    832
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    732
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1075

When a client opens a product card via Turbo page and sees an empty block instead of a price – that's a conversion killer

According to our data, up to 40% of users leave the page if they don't see the price. On projects with catalogs of 10,000+ items, we've encountered this situation many times. The cause is almost always the same: the RSS feed was generated without considering Yandex's Turbo markup requirements. Let's break down how to configure correct Turbo page output for a product catalog on Bitrix.

Problems We Solve

Images not displaying: Yandex requires absolute URLs (with https://) inside <img src>. If the infoblock image is saved with a relative path, the Turbo page will have no photo. On one project, this reduced clickability by 30%.

No buy button: For the button, you need <a data-block="button" href="...">. Without it, the product becomes non-interactive.

Parsing errors: Common issues include incorrect HTML nesting inside CDATA or missing mandatory data-block attributes. Yandex shows the page without styling or refuses to index it.

Why Yandex Refuses to Index RSS

The main reason is non-compliance with the format. Yandex requires RSS 2.0 with the turbo: extension. As stated in official Yandex.Webmaster documentation, the minimum set of fields for a product card:

<item turbo="true">
  <link>https://example.com/catalog/product/</link>
  <turbo:content><![CDATA[
    <header>
      <h1>Product Name</h1>
      <menu>
        <item url="/catalog/">Catalog</item>
        <item url="/catalog/section/">Section</item>
      </menu>
    </header>
    <figure>
      <img src="https://example.com/upload/iblock/xxx/photo.jpg" alt="Turbo product page">
    </figure>
    <p>Product description</p>
    <div data-block="price">
      <span data-value="price">5990</span>
      <span data-value="currency">RUB</span>
      <a data-block="button" href="/cart/?add=ID">Buy</a>
    </div>
  ]]></turbo:content>
</item>

The <menu> block is mandatory – it's the Turbo page navigation. The <figure> with an image is often forgotten, and Yandex does not show the picture. Our engineers check every tag through the Yandex validator before launch.

How We Set Up RSS Generation

We create a dedicated PHP script (e.g., /turbo-feed.xml) that selects active trade catalog items and forms an XML feed. The source code uses Bitrix components with CIBlockElement::GetList() and CCatalogProduct::GetOptimalPrice(). For a catalog of 200 items, without caching, each request generates 200 SQL queries; with an hour-long cache, only 1 query is needed.

// /turbo-feed.xml
define('NO_KEEP_STATISTIC', true);
define('NOT_CHECK_PERMISSIONS', false);
header('Content-Type: application/rss+xml; charset=utf-8');

$res = \CIBlockElement::GetList(
    ['TIMESTAMP_X' => 'DESC'],
    ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'ACTIVE' => 'Y'],
    false,
    ['nTopCount' => 200],
    ['ID', 'NAME', 'DETAIL_PAGE_URL', 'DETAIL_TEXT', 'DETAIL_PICTURE',
     'PREVIEW_TEXT', 'TIMESTAMP_X', 'IBLOCK_SECTION_ID']
);

echo '<?xml version="1.0" encoding="utf-8"?>';
echo '<rss xmlns:yandex="http://news.yandex.ru" xmlns:turbo="http://turbo.yandex.ru" version="2.0">';
echo '<channel>';
echo '<title>Product Catalog</title>';
echo '<link>' . SITE_SERVER_NAME . '</link>';

while ($el = $res->GetNextElement()) {
    $fields = $el->GetFields();
    $price = \CCatalogProduct::GetOptimalPrice($fields['ID']);
    $imgSrc = '';
    if ($fields['DETAIL_PICTURE']) {
        $img = \CFile::GetFileArray($fields['DETAIL_PICTURE']);
        $imgSrc = 'https://' . SITE_SERVER_NAME . $img['SRC'];
    }
    // ... further item generation
}

Images: Absolute URLs Mandatory

Yandex does not accept relative paths. Helper function:

function absoluteImageUrl(string $src): string {
    if (strpos($src, 'http') === 0) return $src;
    return 'https://' . SITE_SERVER_NAME . $src;
}

Apply it to all DETAIL_PICTURE, PREVIEW_PICTURE, and images from the detailed description.

How to Speed Up Turbo Page Updates

Use tagged RSS caching. Without cache, every request regenerates the feed, causing 200 SQL queries for 200 items. An hour-long cache reduces load 3600 times. Implement an agent to clear the cache on product update via OnAfterIBlockElementUpdate events. Our projects show this approach pays off on catalogs from 500 items.

$cache = \Bitrix\Main\Data\Cache::createInstance();
if ($cache->startDataCache(3600, 'turbo_feed', '/turbo')) {
    // RSS generation
    $xmlContent = generateFeed();
    $cache->endDataCache(['xml' => $xmlContent]);
} else {
    $xmlContent = $cache->getVars()['xml'];
}
echo $xmlContent;
More on item generationFor each product, an item block with mandatory elements is formed. Correct currency and price type is important. We use `CCatalogProduct::GetOptimalPrice` for actual price with discounts. If no price type is set, the base price is taken by default.

Comparison: Turbo Pages vs Regular Mobile Version

Parameter Turbo Page Regular Mobile Version
Load speed < 1 sec 2-5 sec
Server load Minimal (cache + Yandex servers) Medium (depends on hosting)
Markup Limited tag set Full HTML+CSS
Indexing Separate Yandex search results Standard search
Ease of implementation RSS + Webmaster Responsive template

Turbo pages are 2–5 times faster and achieve up to 3 times higher conversion than standard mobile pages. For an e-commerce store with heavy mobile traffic, it's a must-have.

Typical Errors and Solutions

Error Cause Solution
No image Relative URL in <img src> Convert to absolute with helper function
No buy button Missing <a data-block="button"> Add element with attribute
Validation error Wrong CDATA nesting Check via Yandex.Turbo documentation

Process and Guarantees

Our process includes: Turbo catalog audit – check infoblock structure, price types, images, alt attributes; RSS generator design – select fields, format, caching; Development – write component, handle images, prices, buttons; Testing – validate via Yandex.Webmaster, check all product types; Launch and monitoring – add RSS, review Turbo page analytics in Webmaster. We've been developing on Bitrix for over 7 years, implemented 50+ projects with Turbo pages. We guarantee correct RSS feed operation and passing Yandex validation during the warranty period. The setup pays off through reduced server load and a 10-15% conversion increase. Basic setup starts at $350 and takes 2 to 5 days. If infoblock modifications or 1C integration are needed, time increases. Order Turbo pages setup and get a ready RSS feed in 2 days. Contact us for a project assessment.

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.

Edition For Whom Key Limitation
Start Business cards, landing pages No infoblocks 2.0, no trade catalog
Standard Corporate sites No e-commerce module
Small Business Small stores 1 price type, 1 warehouse, no 1C exchange
Business Medium stores, B2B Multi-warehouse, multicurrency, CommerceML
Enterprise Highload, cluster Web cluster, CDN, multisite

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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis

Add to .settings_extra.php as above.

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?

Task Timeline
Installation on virtual hosting 2–4 hours
Installation on VPS with stack configuration 1–2 days
Installation on dedicated with architecture design 2–5 days
SSL + email + cron + security 1–2 days
Backup and monitoring setup 0.5–1 day

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.