SEO Automation Module for 1C-Bitrix

We often see an editor manually filling in <title> and <description> for each of 8,000 product cards. A week later, 300 more items are added—again manually. A month later, half the meta tags are out of sync with prices and stock. This is typical for stores on 1C-Bitrix: SEO routine eats time, and automation is absent.

The built-in iblock module allows setting meta-tag templates at the infoblock type level. But capabilities are limited. You cannot reference linked elements, apply conditional logic, or account for price or availability. A custom SEO automation module fills this gap systematically. Over 5 years, we have implemented more than 50 SEO automation projects on Bitrix.

Why SEO Automation Is Critical for an E-commerce Store

Meta tags directly affect ranking. If titles and descriptions are not unique or do not contain current data (price, stock), search engines lower positions. According to Google Search Central, this is an important factor. Manual editing of a catalog with over 5,000 items takes 20–40 hours per week—equivalent to an employee's salary. Automation pays for itself in 2–3 months, saving substantial annual costs.

What the Module Does

The module core is a template engine with syntax like {ELEMENT_NAME} | {CATALOG_PRICE} | {SECTION_NAME}. Templates are compiled into PHP closures and cached via Bitrix\Main\Data\Cache. No additional frontend requests—only cache reads.

Meta-tag generation by template. For each page type (catalog section, element, search, tag), a separate template is configured. Variables are taken from infoblock properties, commercial catalog fields (b_catalog_price, b_catalog_product), and custom sources.

Canonical and hreflang. The module intercepts the OnBeforeIBlockElementUpdate event and automatically sets the canonical URL with the active language taken into account. For more information, see the article on Canonical link element. (Note: link preserved as is, but URL is correct? Actually it's "Cannonical" typo but we keep as in original? The original Russian link was correct: https://en.wikipedia.org/wiki/Canonical_link_element. I'll correct the URL.)

Automatic alt for images. Through an agent (\Bitrix\Main\Agent), a background task runs: it iterates over infoblock elements without filled DETAIL_PICTURE alt and writes the value according to a template. Alt coverage grows from 30% to 95% in two weeks.

Sitemap generation. It connects to the seo module (namespace Bitrix\Seo\SitemapFile) and extends the logic: excludes pages with noindex, considers priority by modification date, splits into parts if exceeding 50,000 URLs.

How the Template Engine Solves Performance Issues

The hardest part is designing data sources so that the template works fast even with 100,000 elements.

// Registering a data source
\MyVendor\SeoModule\TemplateEngine::registerSource(
    'CATALOG_PRICE',
    function(int $elementId, array $context): string {
        $price = \Bitrix\Catalog\PriceTable::getList([
            'filter' => ['=PRODUCT_ID' => $elementId, '=CATALOG_GROUP_ID' => 1],
            'select' => ['PRICE'],
            'limit'  => 1,
        ])->fetchObject();
        return $price ? number_format($price->getPrice(), 0, '.', ' ') : '';
    }
);

Data sources are registered via a static registry. During template rendering, the engine determines which sources are needed and makes exactly as many database queries as necessary. For lists, batch loading is used via DataManager::getList with an IN filter on the ID array.

Caching. The rendering result is cached with the tag iblock_id_N. This allows clearing the cache pinpoint when an element is changed via \Bitrix\Main\Data\TaggedCache.

Monitoring. The module maintains a meta-tag coverage log: for each section, the percentage of pages with non-empty <title>, <description>, and canonical is displayed. The myvendor_seo_coverage table is updated via an agent once a day.

What Is Included in Module Development?

1. Audit of current infoblocks: property structure, number of languages, presence of commercial catalog.
2. Design of data source architecture based on the audit.
3. Configuration of meta-tag templates for all page types (catalog, sections, elements, search, tags).
4. Implementation of canonical and hreflang with multilingual support.
5. Integration with commercial catalog for price and stock substitution.
6. Agent for automatic alt filling of images.
7. Sitemap generation considering noindex and priorities.
8. Meta-tag coverage table for monitoring.
9. Operational documentation and administrator training.
10. 12-month warranty on the module, support for Bitrix updates.

Comparison of Manual vs. Automated Approach

Development Timeline

Typical Mistakes in Automation Setup

• Ignoring custom infoblock properties—incomplete templates.
• Missing tagged cache—site crash under load.
• Wrong event order: OnBeforeIBlockElementUpdate conflicts with 1C synchronization.
• Forgetting multilingual support: canonical without hreflang—penalty from Google.

Before starting, it is important to audit current infoblocks. Property structure, number of languages, presence of commercial catalog—all affect the architecture of data sources. We guarantee an individual approach and fixed cost after agreeing on the technical specification.

Get a consultation—we will assess your project and offer the optimal solution. Order development, we work throughout Russia and CIS.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.