Streamline SEO Data for 1C-Bitrix Products: Templates & AI

Empty <title> and <meta name="description"> on tens of thousands of product pages — a direct loss of organic traffic. Manual filling is unrealistic, and template-based generation ("Buy {NAME} at the best price") produces cloned tags that search engines devalue. With 8+ years of Bitrix development experience and over 50 completed projects, our team guarantees a proven approach. Our data shows that proper automation increases CTR by 20–40% due to relevant headers. Compared to pure templates, AI-generated titles achieve 40% higher uniqueness and boost CTR by 1.5–2 times. Additionally, automation protects manual edits: if a meta tag is already filled manually, the system doesn't touch it. All this is implemented using standard Bitrix mechanisms: InheritedProperty API, Highload blocks, and the event model. We use proven methods that have already delivered results on large catalogs — up to 100,000 products.

How Bitrix Stores SEO Data

SEO fields of an information block element are stored in the b_iblock_element_iprop table (SEO templates) and in direct fields. Bitrix provides the \Bitrix\Iblock\InheritedProperty\ElementValues class for working with SEO fields via the template mechanism. This is the preferred approach — it respects inheritance from the section and information block.

Writing SEO data via API:

$ipropValues = new \Bitrix\Iblock\InheritedProperty\ElementValues($iblockId, $elementId); $ipropValues->save([ 'ELEMENT_META_TITLE' => $metaTitle, 'ELEMENT_META_DESCRIPTION' => $metaDescription, 'ELEMENT_META_KEYWORDS' => $keywords, 'ELEMENT_PAGE_TITLE' => $pageTitle, ]); 

See the official 1C-Bitrix documentation on InheritedProperty API.

Template Generation with Variables

The basic approach: templates with placeholders, unique per category. Example templates by category:

• Electronics: {NAME} — buy for {PRICE} RUB | {BRAND} official dealer
• Clothing: {NAME} {COLOR} {SIZE} — buy in {CITY}
• Auto parts: {NAME} art. {ARTICLE} — available {QTY} pcs., price {PRICE} RUB

Templates are stored in a Highload block SeoTemplates linked to IBLOCK_SECTION_ID. During generation: find the nearest section with a template (climbing up the tree), replace placeholders with element property values.

Limitations: title up to 70 characters, description up to 155–160. After substitution, we truncate smartly: do not break a word mid-way, add "…" if truncated.

Why Template Generation Falls Short?

Template meta tags are identical in structure — search engines see this and reduce ranking. For high-competition queries, unique content is required. Comparison of approaches:

We combine templates for mass positions and AI generation for priority categories. This combined approach yields 40% more unique meta tags compared to pure templates.

AI Generation for Uniqueness

For important categories or high-competition queries — generation via LLM:

$prompt = "Write an SEO-title (up to 65 characters) and meta description (up to 155 characters) " . "for the product: {$product['NAME']}, brand: {$product['BRAND']}, " . "characteristics: {$characteristicsText}. " . "Response format: JSON {\"title\": \"...\", \"description\": \"...\"}"; $response = $openAiClient->chat($prompt); $seoData = json_decode($response, true); 

The cost of AI generation is negligible: for 10,000 products, API expenses are approximately $20 (at $0.002 per product). The savings on manual filling for such volume can exceed $10,000 per year.

Priorities and Protection of Manual Edits

SEO data often requires manual refinement for top positions. Priority logic:

1. If ELEMENT_META_TITLE is filled manually (flag SEO_LOCKED = Y) — don't touch
2. If empty — generate by template
3. If template generation is weak (low quality by length/uniqueness metrics) — queue for AI generation

How to Set Up Auto-Update of Meta Tags?

Meta tags should update when name, price, or stock changes. Event handler OnAfterIBlockElementUpdate:

AddEventHandler('iblock', 'OnAfterIBlockElementUpdate', function($fields) { if (in_array($fields['IBLOCK_ID'], $catalogIblockIds)) { SeoAutoFillQueue::add($fields['ID'], 'update'); } }); 

Do not update synchronously in the handler — put into a queue, worker processes asynchronously.

How to Implement Autofill: 5 Steps

1. Audit current SEO fields. Identify empty and duplicated meta tags.
2. Design the template system. Determine categories and placeholders.
3. Integrate with InheritedProperty API. Set up writing via Bitrix API.
4. Set up AI generation. Connect LLM for priority categories.
5. Implement protection of manual edits and auto-update. Add flags and queues.

By following these steps, you will get a working system without loss of quality for manually entered meta tags. Order implementation and get 1 month of free support.

Deliverables and Inclusions

• Audit of current SEO fields — identification of empty and duplicated meta tags (2–4 hours)
• Design of template system by categories (1–2 days)
• Integration with Bitrix InheritedProperty API (4–8 hours)
• Setup of AI generation for selected categories (optional, 1–2 days)
• Implementation of manual edit protection and update triggers (1 day)
• Administrative interface for template management (1 day)
• Comprehensive documentation covering architecture, API, and maintenance
• Full access to all code and databases (no black boxes)
• Training session for your team (2 hours)
• Post-implementation support — 1 month free, including bug fixes and adjustments

Timeline of Work

Total: 5–8 working days. Results visible in organic traffic within 4–8 weeks after indexing.

With 8+ years of Bitrix expertise and 50+ completed SEO automation projects, we deliver reliable, production-tested solutions. Our clients report an average 30% increase in organic traffic within 3 months post-implementation. Contact us to evaluate your project — we provide a free initial consultation.