Automating SEO Content in 1C-Bitrix with AI

Automating SEO Texts with AI: Experience for 1C-Bitrix

On one project with 800 categories, manual writing of SEO texts would have taken half a year. We automated this process with AI — generation took 3 days, and positions for low-frequency queries increased by 40% in the first month. Content savings for a catalog of 500 sections amounted to up to 60% of the budget compared to freelance copywriters. AI text generation is 3 times faster than manual work, and cost is 2–3 times lower. Our team, with 7 years of experience in Bitrix, has implemented 50+ content automation projects.

Problems We Solve

Freelance copywriter writes 500 sections in a month, an agency takes longer. AI closes this task in 2–3 days with controlled quality. However, simply feeding the API the category name is not enough — context is needed: prices, brands, filter characteristics. Without this, texts turn out template-like and bring no value.

Collecting SEO Data for the Prompt

To generate SEO text, we need to pass to AI:

• Category name and its path in the section tree
• Keywords for the page (from Yandex.Wordstat or SEMrush)
• Number of products in the category and subcategories
• Price range (taken from b_catalog_price via min/max)
• Top brands in the category
• Filter characteristics — what can be filtered on the page

Data collector for a category:

function buildCategoryContext(int $sectionId): array {
    $section = CIBlockSection::GetByID($sectionId)->Fetch();
    $priceRange = getPriceRange($sectionId); // SELECT MIN/MAX from b_catalog_price
    $brands = getTopBrands($sectionId, 5);   // top-5 brands by product count
    $filterProps = getFilterProperties($sectionId); // smart filter properties

    return [
        'name' => $section['NAME'],
        'breadcrumb' => getSectionBreadcrumb($sectionId),
        'count' => $section['ELEMENT_CNT'],
        'price_from' => $priceRange['min'],
        'price_to' => $priceRange['max'],
        'brands' => implode(', ', $brands),
        'filter_params' => implode(', ', $filterProps),
    ];
}

How AI Generates Text Considering Structure?

The prompt contains not only data but also a markup template. We set requirements: H2 and H3, introductory paragraph, "How to Choose" block, USP, call to action. AI fills the template with specifics from the context. For example, for the "Laptops" category, it generates H2 "Buy a laptop in Minsk — competitive prices" and follows the schema. Keywords are passed as a list of requirements: main key "buy laptop Minsk", additional "laptops online store", "laptop price", LSI "processor", "RAM". AI weaves them naturally into the text.

Updating Section SEO Texts

Section SEO text is stored in b_iblock_section.DESCRIPTION. Writing via API:

$ibs = new CIBlockSection();
$ibs->Update($sectionId, [
    'DESCRIPTION' => $generatedHtml,
    'DESCRIPTION_TYPE' => 'html',
]);

For section meta tags — similar to products, via \Bitrix\Iblock\InheritedProperty\SectionValues:

$ipropValues = new \Bitrix\Iblock\InheritedProperty\SectionValues($iblockId, $sectionId);
$ipropValues->save([
    'SECTION_META_TITLE' => $metaTitle,
    'SECTION_META_DESCRIPTION' => $metaDescription,
]);

Update Scheduler

SEO texts become outdated: prices change, new brands appear, assortment updates. Update strategy:

• Automatically: if the price range changes by more than 20% → regenerate
• On schedule: once a quarter — full regeneration for all sections
• On trigger: when a new subcategory is added — regenerate the parent section

Uniqueness Control

Before publication — uniqueness check. Simple option without external services: compare with already published texts via similar_text(). If similarity > 40% — regenerate with a different seed (parameter temperature: 0.8 instead of standard 0.7).

Why AI Is More Profitable Than Manual Copywriting?

Manual copywriting for 500 sections costs several times more and takes up to one and a half months. AI generation provides savings up to 60% of the budget and allows launching content in 3 days. Moreover, texts undergo uniqueness control and are optimized for key queries. SEO copywriting, by definition from Wikipedia, is the writing of texts oriented to search queries.

What's Included in the Work?

Timeline

Total: 5–9 business days. For 500+ sections — initial generation time is 3–8 hours depending on the AI model (e.g., YandexGPT or OpenAI — both supported).

Want to automate content for your catalog? Contact us — we'll evaluate the project and offer a solution for your stack. Request a consultation: we guarantee uniqueness of each text and growth in positions for target queries.

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.