Writing SEO Texts for 1C-Bitrix Product Cards
The product card is the most competitive page in e-commerce. In search for an exact commercial query ("buy Bosch GSH 16-28"), it competes with cards from Wildberries, Ozon, DNS, and official manufacturer sites. The card text must do two things simultaneously: help the search engine understand exactly what is being sold, and persuade a real person to click "Buy." Our team specializes in writing SEO texts for 1C-Bitrix product cards—from audit to full catalog filling turnkey. We will assess your project and offer the optimal solution. The cost is determined after assessing the scope and complexity.
What Problems We Solve
We encounter typical pains of online store owners on Bitrix:
- Duplicate descriptions. Texts are copied from the supplier's site or generated without SEO consideration. Search engines apply filters, traffic drops.
- Uncontrolled output. Cards lack title and meta description, or they are identical for all products. Positions for unique queries are absent.
- Scaling difficulties. Manually writing 1000+ unique texts is impossible, but without them the catalog does not rank. We solve this with a combination of automated templates and priority copywriting.
How We Do It
Our approach is hybrid. For the top 200 SKUs by traffic and margin, we write completely unique texts with semantic research. For the rest, we configure SEO templates in Bitrix and apply autogeneration with post-editing.
Example of a template setup:
Title: {=this.Name} — buy in {=site.NAME}, price {=catalog.MinPrice} ₽
Description: {=this.PreviewText.TextOnly.200} Delivery across Russia. Warranty.
These templates only work when the catalog module is enabled. The {=this.PreviewText.TextOnly.200} variable truncates the text to 200 characters, removing HTML. A properly written PREVIEW_TEXT automatically becomes a quality description.
For text generation, we use an API with editor control. This is 3-5 times faster than manual writing while maintaining uniqueness. Comparison: for 1000 products, manual copywriting would take 2-3 months; automation takes 2-3 weeks. Budget savings average 40–60% compared to full manual writing.
How to Avoid Duplicate Descriptions?
Duplicates occur when texts are copied from one source or generated without uniqueness. The solution is to use templates that substitute product characteristics (SKU, size, color) and check the finished text through plagiarism services. Configuring PREVIEW_TEXT for each SKU with a unique introduction solves the problem at Bitrix level.
Why Is Uniqueness Important for Each SKU?
For products with variants (color, size), search engines see each card as a separate page. If descriptions are identical, it's duplication. Write unique texts for each offer, at least 2–3 sentences of difference. Then all variants will participate in search without filters.
Work Process
-
Semantic audit — gather keys for priority categories and products.
-
Brief and template — define the description structure (problem → features → application → package contents).
- Writing — work in Google Sheets: product ID, Preview, Detail, status.
- Uniqueness check — use Text.ru, Advego, exclude over-optimization (1-3 occurrences of the main key per 500 words).
- Import into Bitrix — load via CSV or REST API, clear component cache.
- Editor training — hand over instructions for maintaining standards.
What Is Included
- Audit of the current catalog state (duplicates, template errors, semantics).
- Writing unique texts for priority SKUs (Preview + Detail).
- Configuring SEO templates in information blocks and trade offers.
- Importing texts into Bitrix via CSV/API with cache preservation.
- Documentation on updating texts for future products.
- Consulting and training your content manager.
Timelines
| Volume |
Timeline |
| 30–50 cards (manual copywriting) |
5–7 working days |
| 100–200 cards (hybrid) |
2–4 weeks |
| Template setup + texts for top SKUs |
1–3 weeks |
Cost is calculated individually after assessing the volume and complexity of products. Contact us—we will prepare a transparent quote.
Comparison of Approaches
Manual copywriting takes 2–3 months and ensures 100% uniqueness. Automation with refinement takes 2–3 weeks achieving 85–95% uniqueness.
Typical Mistakes
- Using the same
PREVIEW_TEXT for all products in a category.
- Over-optimization: 5+ keyword occurrences in 300 characters — Baden-Baden filter.
- Ignoring variants (SKUs): texts are written for the parent product, not for each offer.
- Missing cache clear after import — new information not visible to search engines.
- Copying texts from the manufacturer's site without modification — 100% duplicate.
Why Choose Us
5+ years of experience in development and SEO promotion on 1C-Bitrix. Over 200 implemented e-commerce projects—from small catalogs to large marketplaces. According to Yandex.Webmaster, unique descriptions increase CTR by 15–25%. We guarantee text uniqueness (checked via Text.ru) and no over-optimization. Certified platform specialists. Contact us for an audit of your catalog—we will show what can be improved. Get a consultation right now.
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
-
Audit – analyze current state: meta tags, URL structure, indexing, speed, microdata. Generate a prioritized report.
-
Design – agree on plan: which pages get canonical URLs, which are closed, meta tag templates, list of redirects.
-
Implementation – configure SEO module, SEF URLs,
robots.txt, sitemap.xml, implement JSON-LD. Write custom handlers for auto-redirects and SEO filters.
-
Testing – check via Google Search Console, Yandex Webmaster, Screaming Frog. Ensure duplicates disappear, crawler visits only relevant pages.
-
Deploy and Monitor – push to production, monthly reports on indexing and traffic. Adjust as needed.
What Does SEO Configuration Include?
| Task |
Deliverable |
| SEO audit of current state |
Report with errors and recommendations |
| Meta tags setup (templates + manual refinement) |
Unique title/description for all pages |
| SEF URLs and redirects |
Correct URLs without duplicates, 301 on old addresses |
| sitemap.xml + robots.txt |
Proper indexing, crawl budget protection |
| Schema.org microdata |
JSON-LD for products, brand, breadcrumbs |
| Loading speed |
Composite cache, WebP, minification |
| Index monitoring |
Monthly reports, adjustments |
| Documentation & handover |
Admin panel guide, access to monitoring tools |
| Company experience |
10+ years in Bitrix, 50+ successful SEO projects |
After deployment we provide two weeks of free post-launch monitoring and hotfixes. Extended support is available on a monthly retainer.
Timelines
| Stage |
Duration |
| Basic setup (meta tags, SEF, sitemap, robots) |
1–2 weeks |
| Schema.org for online store |
1–2 weeks |
| Comprehensive technical SEO optimization |
3–5 weeks |
| Speed optimization (Composite, images, CDN) |
2–4 weeks |
| SEO filters with meta tags and SEF |
2–3 weeks |
| Migration with redirects |
1–3 weeks |
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.
