1C-Bitrix Blog Content: SEO, Automation, and Images

Why a Blog on Bitrix Requires a Dedicated Approach?

We often hear from clients: "We need a blog on Bitrix, like everyone else." We open the admin panel – a standard news infoblock with a couple of properties. But a real blog is not a press release feed. Each article should be a search magnet: answer a specific query, have a unique structure, and internal links to other articles. In one of our practices, after restructuring the blog and configuring all SEO fields, organic traffic grew by 70% in three months. CommerceML is an exchange protocol often used for catalog synchronization, but the blog is not transferred via it, so we implement import separately.

With a systematic approach, each new article strengthens the entire section: cross-linking via tags, auto-selection of related materials, and semantic closeness of headings. Our team has accumulated 10+ years of experience in Bitrix development and completed over 500 content projects. We know that a blog is not just a news feed but a full-fledged content marketing tool requiring deep infoblock, template, and SEO setting refinement.

Blog Infoblock: Differences from News

In the typical Bitrix structure, blog and news share the same mechanism, differing only in settings. For a blog, the infoblock is extended with additional properties:

• READING_TIME — reading time (in minutes, automatically calculated)
• AUTHOR_ID — link to an element of the "Authors" infoblock via property type "Element"
• RELATED_ARTICLES — multiple property for the "Read Also" block
• TABLE_OF_CONTENTS — auto-generated table of contents (JSON or HTML)
• TAGS — tags, multiple property

A separate "Authors" infoblock allows outputting biography and other articles via CIBlockElement::GetByID() with minimal database queries.

How to Set Up a Table of Contents for Long Articles?

Blog articles are often longer than 3,000 characters. Without a table of contents, the user doesn't understand what awaits them and leaves. The standard TinyMCE in Bitrix does not generate a table of contents automatically – it needs to be implemented.

Option 1: PHP script in component template. After obtaining DETAIL_TEXT, parse H2/H3 headings via DOMDocument, assign them id attributes, and form an array for the table of contents:

$dom = new DOMDocument('1.0', 'UTF-8');
$dom->loadHTML('<meta charset="UTF-8">' . $arResult['DETAIL_TEXT']);
$headings = $dom->getElementsByTagName('h2');
$toc = [];
foreach ($headings as $h) {
    $text = $h->textContent;
    $id   = Cutil::translit($text, 'ru', ['replace_space' => '-', 'replace_other' => '']);
    $h->setAttribute('id', $id);
    $toc[] = ['id' => $id, 'text' => $text];
}
$arResult['DETAIL_TEXT'] = $dom->saveHTML();
$arResult['TOC'] = $toc;

Option 2: Client-side JS. A script after page load finds all h2 in .article-body, assigns IDs, and builds the table of contents in a side column. Easier to implement, but the table of contents is not visible until JS runs.

Internal Cross-Linking

Blog articles should link to each other by topic. Manual placement of links in the text is labor-intensive and requires updates. A semi-automatic approach:

1. In the RELATED_ARTICLES property, the content manager selects 3–5 related articles.
2. In the detail page template, the "Read Also" block outputs these elements via CIBlockElement::GetByID().
3. Additionally, a script automatically searches for keywords in the text and highlights them with links to relevant articles (based on the TAGS property).

SEO Optimization During Filling

Each article is a potential landing page. A minimum set of SEO settings at the infoblock element level:

• META_TITLE: key query + brand, up to 65 characters
• META_DESCRIPTION: answer to query + call to action, 150–160 characters
• Canonical URL: if the article is available via multiple URLs, canonical points to the main one. Follow the recommendations from official Bitrix documentation for canonical setup.

In Bitrix, canonical is added in the template:

$APPLICATION->SetPageProperty('canonical', 'https://example.ru/blog/' . $arResult['CODE'] . '/');

If the blog is large (500+ articles), configure a sitemap via bitrix:main.map.google with a separate map for the blog, with priority 0.7–0.8 for fresh articles.

Images for the Blog

For social sharing, the OG image size is critical. Standard – 1200x630 px. In Bitrix, when uploading a detail picture, the component does not resize it for OG. We add automatic resizing:

$ogImage = CFile::ResizeImageGet(
    $arResult['DETAIL_PICTURE'],
    ['width' => 1200, 'height' => 630],
    BX_RESIZE_IMAGE_PROPORTIONAL_ALT
);
$APPLICATION->SetPageProperty('og:image', SITE_SERVER_NAME . $ogImage['src']);

Alt text for images is mandatory. In Bitrix, it is stored in the DESCRIPTION field of the b_file table record. When uploading via the standard form, the content manager must fill the "Description" field – this is the alt.

Categories and Tags: Navigation Structure

A typical mistake is creating 20 tags without a system, each with 1–2 articles. The correct structure:

• Infoblock sections (blog categories) – broad topics: "Marketing", "Development", "Analytics". They are displayed as the main blog menu.
• Tags – specific subtopics. They should appear in at least 3–5 articles.

Category and tag pages require separate SEO descriptions – via the section description in b_iblock_section (DESCRIPTION field) or via section properties.

How to Automate Blog Filling?

For a regular blog with high publication frequency, we use:

• Excel/CSV import via the standard iblock module or a custom script with CIBlockElement::Add()
• Parser of external sources – a Bitrix agent run via cron, fetching RSS or API, creating drafts with "inactive" status
• OpenAI API for generating drafts based on headings and keywords (via \Bitrix\Main\Web\HttpClient)

Experience shows that automation pays off in 2-3 months if publishing 10+ articles per week.

What Is Included in the Work

• Analysis of the current infoblock structure and SEO
• Configuration of the blog infoblock with additional properties
• Development of a template with automatic table of contents
• Setup of SEO fields and canonical
• Content import (up to 100 articles) with cross-linking
• Automatic image resizing
• Integration with 1C (if necessary)
• Training of the content manager
• Technical support for 1 month after deployment

Timelines

The blog does not generate traffic immediately – first search positions appear after 2–4 months. But with a properly built process, each new article strengthens the entire section through internal links.

We will assess your project within 1 business day. Contact us for a consultation – we will prepare a commercial proposal with a detailed filling plan. Order turnkey blog content with a guaranteed result.

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.