Writing SEO texts for 1C-Bitrix product cards

Writing SEO Texts for 1C-Bitrix Product Pages

A product page is the most competitive page in e-commerce. In search results for a precise commercial query ("buy Bosch GSH 16-28"), it competes with pages from Wildberries, Ozon, DNS, and official manufacturer websites. The product page text must do two things simultaneously: help the search engine understand exactly what is being sold, and convince a real person to click "Buy."

Writing SEO Texts for 1C-Bitrix Product Pages

How 1C-Bitrix Stores and Renders Product Page Text

In the infoblock element (table b_iblock_element):

• PREVIEW_TEXT + PREVIEW_TEXT_TYPE — short description, displayed in listings and used in meta tag templates
• DETAIL_TEXT + DETAIL_TEXT_TYPE — full description on the product page, can contain HTML

SEO data for a product page is stored in b_iblock_iblock SEO templates, which 1C-Bitrix applies to elements via the iblock module:

Title template:       Buy {=this.Name} for {=catalog.MinPrice} RUB
Description template: {=this.PreviewText.TextOnly}. Order online.

These templates are the entry point for SEO texts: a well-written PREVIEW_TEXT automatically becomes a good description.

SEO Text Structure for a Product Page

PREVIEW_TEXT (up to 200 characters): One or two sentences covering the main consumer benefit and a key parameter. Used as the meta description — must be self-contained, with no references to "the full text below."

Poor: The Bosch GSH 16-28 demolition hammer is a high-quality tool for professional use.

Good: Bosch GSH 16-28 demolition hammer, 1750 W, 45 J. For demolishing walls and working with reinforced concrete. Weight 16 kg, 3-year warranty.

DETAIL_TEXT (300–800 words, HTML):

<p>[Task the product solves: specific, professional]</p>

<h2>Features of {product name}</h2>
<ul>
    <li>[Key characteristic and what it delivers to the user]</li>
    <li>[Technology or material + practical benefit]</li>
</ul>

<h2>Technical Specifications</h2>
<table>
    <tr><th>Parameter</th><th>Value</th></tr>
    <!-- Main parameters — duplicate the product properties in a convenient format -->
</table>

<h2>Package Contents</h2>
<ul>
    <li>Item</li>
</ul>

<h2>Applications</h2>
<p>[Where and how it is used, compatibility]</p>

Keywords in Product Page Text: Avoiding Over-Optimization

A common mistake is inserting the key phrase into every paragraph. Yandex algorithms (Baden-Baden, 2017) and Google detect over-optimization and apply filters to the entire site.

Effective keyword density: 1–3 occurrences of the main keyword (in different forms) per 500 words of text. Everything else consists of semantically related terms, synonyms, and specifications. Verify using Advego Semanalysis or Text.ru.

Semantics for Product Page Texts: What to Use

Main key (transactional): "buy Bosch GSH 16-28"
Informational keys: "Bosch GSH 16-28 specs", "Bosch GSH 16-28 reviews"
LSI keys: "demolition hammer for concrete", "SDS-max breaker", "45 J rotary hammer"
Brand + model in different forms: "Bosch hammer", "Bosch GSH"

For catalogs with thousands of SKUs, writing unique texts for each product is not feasible. Strategy:

1. Unique texts — top 100–200 SKUs by traffic and margin
2. Template texts — for the rest, using 1C-Bitrix SEO templates with characteristic substitution
3. API auto-generation + editor review — for the middle tier

SEO Templates for Automatic Title and Description Generation

1C-Bitrix supports templates based on element fields. Examples for a tool shop:

Title:       {=this.Name} — buy at {=site.NAME}, price {=catalog.MinPrice} RUB
Description: {=this.PreviewText.TextOnly.200} Delivery across Russia. Manufacturer warranty.

The {=catalog.MinPrice} variable requires the catalog module to be enabled. {=this.PreviewText.TextOnly.200} truncates text to 200 characters and strips HTML tags.

Texts for Products with Variants (SKUs in 1C-Bitrix)

In 1C-Bitrix, trade offers (SKUs) are child elements of b_iblock_element in a separate offers infoblock. SEO texts are written for the parent product, not for each SKU — otherwise thousands of duplicate pages are created.

For products with fundamentally different variants (e.g., different tile collections), each variant can be a separate infoblock element with its own page and unique text.

Bulk Text Writing: Process Organization

1. Semantic audit → Priority SKUs (traffic + margin)
2. Category brief → Description structure template
3. Writing → Google Sheets with columns ID | Name | Preview | Detail
4. Uniqueness check → Text.ru / Advego
5. Upload to 1C-Bitrix → CSV import via API
6. Clear page cache → \CBitrixComponent::clearComponentCache

Timelines