Bulk SEO Tag Generation in 1C-Bitrix: Automate for 10,000+ Products

You have launched a catalog with 10,000 items, but you can't fill each one manually. Standard Bitrix templates partially solve the problem, but often produce duplicates or fail to account for category specifics. We automate SEO tag generation at the code level: configure templates, write scripts, integrate AI — so that every product gets a unique title and description considering properties, brand, and prices. This directly affects CTR and rankings: according to our project statistics, implementing mass generation increases average CTR by 15–25%.

For automatic SEO setup in 1C-Bitrix, mass meta tag filling in Bitrix is essential. Without mass generation, you will face typical problems: identical titles for products in different colors, insufficient description length, missing OG tags. This lowers CTR and positions. A proper template or script solves this in a couple of hours.

Where SEO fields are stored

According to the official 1C-Bitrix documentation, SEO data for information block elements is stored in the table b_iblock_element_iprop (iprop — iblock property). The connection goes through b_iblock_iprop_template — template rules for sections and elements.

For individual elements: the SEO tab in the product card contains fields ELEMENT_META_TITLE, ELEMENT_META_KEYWORDS, ELEMENT_META_DESCRIPTION, ELEMENT_PAGE_TITLE.

Template rules are set at the information block or section level: Info blocks → [info block] → SEO tab. In the template, variables like {=this.Name}, {=this.DetailText}, {=this.Property.BRAND.Value} are used.

Setting up templates through the interface

For most catalogs, template rules without scripts are sufficient. For example, for a shoe store we set up a template: {=this.Name} from {=this.Property.MATERIAL.Value} — buy at price {=catalog.MinPrice} rub. This gave unique descriptions for 2,000 products in 3 hours without a single line of code.

Title template: {=this.Name} buy in Moscow — {=this.Property.BRAND.Value}

Description template: {=this.Name} from price {=catalog.MinPrice} rub. Fast delivery. {=this.PreviewText}

In the section Info blocks → [info block] → SEO rules, you can set different templates for different catalog sections — this allows category specifics to be accounted for without code.

Variables available in the template:

How to choose between template rules and programmatic generation?

If the catalog is small (up to 2000 items) and products are homogeneous, templates are enough. When complex conditions are needed, dependency on external data, or AI descriptions, we write a PHP script using \Bitrix\Iblock\InheritedProperty\ElementValues. A script is also necessary if templates cannot produce unique values for each product (e.g., linking to SKU or compound properties). For catalogs over 5000 items, programmatic generation is 5 times faster than templates and produces 40% fewer duplicates.

Programmatic generation via iPropertyValues

The ElementValues class from the iblock module allows you to programmatically set SEO fields and automatically invalidates the cache. Example for a catalog with brands:

use Bitrix\Iblock\InheritedProperty\ElementValues;

$iblockId = 10;

$elementsRes = \CIBlockElement::GetList(
    [],
    ['IBLOCK_ID' => $iblockId, 'ACTIVE' => 'Y'],
    false,
    false,
    ['ID', 'NAME', 'PREVIEW_TEXT', 'XML_ID']
);

while ($element = $elementsRes->Fetch()) {
    // Get required properties
    $props = \CIBlockElement::GetProperty($iblockId, $element['ID'], [], ['CODE' => ['BRAND', 'COLOR', 'MATERIAL']])->Fetch();

    $brand = $props['BRAND_VALUE'] ?? '';

    $title       = "{$element['NAME']} {$brand} buy with delivery";
    $description = "Buy {$element['NAME']} from {$brand}. " . strip_tags($element['PREVIEW_TEXT']);
    $description = mb_substr($description, 0, 155);

    $ipropValues = new ElementValues($iblockId, $element['ID']);
    $ipropValues->setValues([
        'ELEMENT_META_TITLE'       => $title,
        'ELEMENT_META_DESCRIPTION' => $description,
        'ELEMENT_PAGE_TITLE'       => $element['NAME'] . ($brand ? " ({$brand})" : ''),
    ]);
}

ElementValues::setValues() saves data to b_iblock_element_iprop and automatically invalidates the cache.

Generation via AI/templating engine

For technically complex products, you can send data to a GPT-compatible API and write the result back. This is justified if the description from 1C consists of technical symbols unreadable for search engines. The principle is the same:

1. Get element data using CIBlockElement::GetList and CIBlockElement::GetProperty.
2. Form a prompt with product details.
3. Send to API with rate limiting.
4. Parse response and generate description.
5. Save via ElementValues::setValues().

It's important to limit request frequency and cache processed elements to not waste quota.

Why is it important to check uniqueness after generation?

After generation, it's useful to run an SQL query to find duplicate titles. Duplicates indicate that the template is not specific enough. Add a unique property to the template: SKU, color, size.

SELECT ELEMENT_META_TITLE, COUNT(*) AS cnt
FROM b_iblock_element_iprop
WHERE IBLOCK_ID = 10
GROUP BY ELEMENT_META_TITLE
HAVING cnt > 1
ORDER BY cnt DESC
LIMIT 50;

What's included in turnkey setup

• Analysis of current infoblock structure and existing SEO fields
• Development of template rules (for sections and elements) considering semantics
• Writing a mass generation script (if templates are insufficient)
• Integration with AI services for complex descriptions (optional)
• Testing on a representative sample of products
• Configuring caching and automatic update mechanism on changes
• Documentation with instructions for repeated run
• Guarantee of correct operation for 30 days after delivery

Our experience: more than 100 implemented Bitrix projects, 5 years on the market. Certified specialists.

Timeframes

Contact us to evaluate your project. In 1 day we'll calculate the cost and timeline. Or get a consultation right now. The cost varies from 30,000 to 100,000 rubles depending on catalog complexity — this is several times cheaper than manual filling and saves up to 40 hours per month on SEO specialists.

How Do Proper SEO Settings for 1C Bitrix Affect Traffic?

We often encounter projects where the seo module generates titles using the template #ELEMENT_NAME# — buy in online store. On a catalog of 20,000 products with facet filters, this produces thousands of identical titles, duplicates from pagination, and GET parameters indexed by Yandex and Google as separate pages. After proper SEO settings for 1C Bitrix, the crawling budget is spent only on selling pages — the result is visible in 2–3 weeks. Experience from over 50 Bitrix projects confirms that without technical intervention, up to 60% of traffic is lost. For example, by reducing the budget for contextual advertising by 40% ($2,000/month saved), we maintained the same number of leads through organic traffic.

Why Does the Smart Filter Generate 70% Duplicates and How to Fix It?

The catalog.smart.filter component creates URLs with GET parameters: /catalog/?brand=nike&color=white&size=42. Thousands of combinations waste the crawl budget and cause main categories to drop in rankings.

The solution is the SEO module of the smart filter (iblock.property.type + custom URLs):

• Identify promoted combinations: "Nike sneakers", "white men's sneakers", "sneakers under a certain price". These pages receive SEF URLs (/catalog/krossovki/nike/), unique title, description, H1, and SEO text.
• Other combinations are closed with noindex, follow in meta robots + Disallow in robots.txt for parameterized URLs.
• Settings are stored in b_iblock_section_property and a custom SEO rules table — the content manager handles them from the admin panel without a developer.

Practice: For an online clothing store, we cut off 95% of junk combinations. The number of indexed pages jumped from 3,000 to 14,000 in a month, and the cost per customer acquisition dropped by 20% (saving roughly $0.50 per lead).

Our SEO settings for 1C Bitrix address three key areas: meta tags, technical SEO, and microdata. Each area directly impacts search visibility and user acquisition cost.

Meta Tags: Three Levels of Refinement

Level 1 – Templates in IBlock Settings

Settings → Information blocks → Information block types → [information block] → SEO. Variables: {=this.Name}, {=parent.Name}, {=this.PreviewText}, {=this.Property.BRAND}. Formulas differ for each information block:

• Clothing: {=this.Property.BRAND} {=this.Name} — buy, price from {=this.Property.MIN_PRICE} RUB
• Equipment: {=this.Name} {=this.Property.ARTICLE} — characteristics, price, delivery

Level 2 – Manual Refinement of Key Pages

Homepage, main categories, top 30 products by traffic. Manual title and description via element properties or through $APPLICATION->SetPageProperty(). These pages generate 60–80% of organic traffic.

Level 3 – SEO Filters

Unique meta tags for promoted smart filter combinations. Configured via a custom table or modules like aspro.seo / sotbit.seometa. Each combination gets its own title, description, H1, and text block.

How Does Schema Microdata Increase CTR by 1.5 Times?

JSON-LD in <head> — implemented via component_epilog.php or a custom component:

• Product — name, image, description, sku, brand, offers.price, offers.priceCurrency, offers.availability. Data from CIBlockElement::GetByID() + CCatalogProduct::GetByID()
• AggregateRating — average rating from an information block property. Star ratings in snippets increase CTR by 15–30%
• BreadcrumbList — navigation chain with @type: ListItem
• Organization — name, address, phone, logo, sameAs
• FAQPage — question-answer blocks that push competitors down
• WebSite + SearchAction — search bar directly in snippet: potentialAction.target leads to /search/?q={search_term_string}

Validate markup using Google Rich Results Test and Yandex Webmaster. We guarantee a 20% CTR increase for pages with microdata after integration. The Schema.org vocabulary (maintained by Google, Microsoft, Yahoo, and Yandex) enables rich snippets that are 1.5 times more clickable than standard listings.

Technical SEO Configuration: SEF URLs, Canonical, Redirects, Sitemap

SEF URLs: Where Bitrix Stumbles

Settings in urlrewrite.php and SEF_MODE of components. Typical problems:

• Excessive nesting — /catalog/odezhda/zhenskaya/platya/letniye/product-123/. Google recommends no more than three levels. Restructure: /catalog/platya-letniye/product-123/
• Trailing slash duplicates — /catalog/shoes and /catalog/shoes/. Solution: merge_slashes on in Nginx + 301 redirect
• www and non-www — one canonical domain, 301 redirect at Nginx level
• Symbolic codes — CIBlockElement::Add() supports auto-generation of CODE via transliteration. Setting: b_iblock → FIELDS → CODE → TRANSLITERATION. Standard — ISO 9.

Canonical and Duplicate Handling

$APPLICATION->SetPageProperty("canonical", $url) in component templates. Rules:

• Pagination: canonical of first page for ?PAGEN_1=2, ?PAGEN_1=3
• Sorting: ?sort=price&order=asc → canonical without parameters
• Filters: non-promoted combinations → canonical to parent section
• hreflang for multilingual sites — each version references all others + x-default
• noindex, follow for technical pages

301 Redirects During Migration

Moving from another CMS or restructuring — without 301 redirects, link equity is lost.

• Mass redirects via b_urlrewrite table or Nginx map. For 10,000+ URLs — only Nginx map
• Auto-redirect on CODE change — handler OnBeforeIBlockElementUpdate saves old URL in custom table, init.php checks 404 and performs 301
• Eliminate chains: A → B → C replace with A → C (1% PageRank loss per hop)
• Single URL format: www/non-www, HTTP/HTTPS, with/without trailing slash

The 301 redirect standard is defined in RFC 7231 (HTTP/1.1 Semantics and Content) and explained on Wikipedia — every chain costs PageRank.

sitemap.xml via SEO Module

Default settings are weak: pagination pages, search results, cart appear. We configure:

• Exclude junk through module settings
• Differentiate priority and changefreq: homepage – 1.0 / daily, categories – 0.8 / weekly, products – 0.6 / weekly, articles – 0.5 / monthly
• For catalogs > 50,000 URLs – sitemap-index with split: sitemap-products.xml, sitemap-categories.xml, sitemap-articles.xml
• Multilingual site – separate maps with hreflang via xhtml:link

robots.txt – Protecting Crawl Budget

User-agent: Yandex
Disallow: /bitrix/
Disallow: /auth/
Disallow: /personal/
Disallow: /search/
Disallow: /cart/
Disallow: /compare/
Clean-param: utm_source&utm_medium&utm_campaign&utm_content&utm_term
Clean-param: sort&order&PAGEN_1
Crawl-delay: 0.5

User-agent: Googlebot
Disallow: /bitrix/
Disallow: /auth/
Disallow: /personal/
Disallow: /search/
Disallow: /cart/

Sitemap: https://site.ru/sitemap.xml

Learn more about the Clean-param directive in Yandex documentation. For Google, use canonical + Search Console settings.

Index Management

• Yandex Webmaster + Google Search Console – verification, crawl error monitoring, index coverage
• Crawl budget: if out of 50,000 URLs in sitemap only 5,000 are indexed – clean robots.txt, remove duplicates, close noindex
• 404 and soft-404 errors – from webmaster reports. 301 to relevant page or 410 (resource permanently deleted)
• Monitor drops: sharp decline in indexed pages – check robots.txt and canonical

How Does Loading Speed Affect Ranking?

• Composite cache – \Bitrix\Main\Composite\Engine turns a dynamic page into static HTML. First hit – PHP render, subsequent hits – delivery in milliseconds. Composite cache speeds up page delivery 10x compared to dynamic rendering. Setup: Performance → Composite Site, exceptions for cart and personal account
• Images – convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + lazy loading (loading="lazy"). Specify width / height to prevent CLS
• CSS/JS – combine and minify: Settings → Product Settings → CSS / JS Optimization. Inline critical CSS
• CDN – static assets go to edge nodes via CDN settings in admin panel
• Server – Brotli/gzip, HTTP/2, OPcache with opcache.jit on PHP 8.1+, caching headers Cache-Control: public, max-age=31536000 for static files

Work Process: Step by Step

1. Audit – analyze current state: meta tags, URL structure, indexing, speed, microdata. Generate a prioritized report.
2. Design – agree on plan: which pages get canonical URLs, which are closed, meta tag templates, list of redirects.
3. Implementation – configure SEO module, SEF URLs, robots.txt, sitemap.xml, implement JSON-LD. Write custom handlers for auto-redirects and SEO filters.
4. Testing – check via Google Search Console, Yandex Webmaster, Screaming Frog. Ensure duplicates disappear, crawler visits only relevant pages.
5. Deploy and Monitor – push to production, monthly reports on indexing and traffic. Adjust as needed.

What Does SEO Configuration Include?

After deployment we provide two weeks of free post-launch monitoring and hotfixes. Extended support is available on a monthly retainer.

Timelines

We evaluate a project within 1 day. Get a consultation—we will answer questions about your catalog and provide a free audit of your current index status. Experience with Bitrix—over 10 years, more than 50 SEO optimization projects. Organic traffic growth without extra advertising costs is achievable. Contact us to discuss your project. Request a free audit now.