Which Meta Tags Are Critical for a Bitrix Online Store?
The first and most frequent mistake: a product page displays the section <title> instead of the product name. The reason is incorrectly configured meta tag templates or a missing bitrix:seo.meta component. As a result, search engines see identical titles for hundreds of products, reducing CTR by 40-60%. We configure the SEO module turnkey and have completed over 200 projects. Average setup time per project is 4 hours, saving up to 80% of manual work. This saves up to several hundred thousand rubles per year on SEO specialist costs.
Why Is Proper SEO Module Setup Important?
Incorrect meta tags lead to title duplicates, which search engines penalize. According to our data, after configuring the SEO module, the number of indexed pages grows 2-3 times, and rankings for low-frequency queries improve by 50%. A common mistake is using SetPageProperty() in component templates instead of SEO module templates. This causes chaos in meta tags and duplicates. Our approach centralizes meta information management.
How to Set Up Meta Tags for Infoblocks?
Meta tag templates for infoblock sections and elements are set in Marketing → Search Engine Optimization → Meta Tags. Select the infoblock, type (sections or elements), and specify the template for title, description, keywords. Available variables:
-
#NAME# — element/section name
-
#ELEMENT_NAME# — synonym for #NAME#
-
#SECTION_NAME# — section name
-
#IBLOCK_NAME# — infoblock name
-
#PROPERTY_{CODE}# — property value
Example title template:
#NAME# — buy in online store | #SECTION_NAME#
Example description:
#PROPERTY_SEO_DESCRIPTION# | Buy #NAME# with delivery
If the element has ELEMENT_META_TITLE and ELEMENT_META_DESCRIPTION fields filled, they override the template. The template acts as a fallback. This setup covers 95% of catalog pages.
Step-by-Step Setup Instructions
- Create meta tag templates for all infoblocks (sections and elements). Use variables from the documentation.
- Connect the
bitrix:seo.meta component in the page template before the <head> output:
$APPLICATION->IncludeComponent('bitrix:seo.meta', '', [
'IBLOCK_ID' => $iblock_id,
'ELEMENT_ID' => $element_id,
'SECTION_ID' => $section_id,
]);
- Output meta tags in
header.php:
<title><?= htmlspecialchars($APPLICATION->GetPageProperty('title') ?: $APPLICATION->GetTitle()) ?></title>
<meta name="description" content="<?= htmlspecialchars($APPLICATION->GetPageProperty('description')) ?>">
<meta name="keywords" content="<?= htmlspecialchars($APPLICATION->GetPageProperty('keywords')) ?>">
-
Reset infoblock cache: Settings → Module Management → Infoblocks → Reset cache.
- Verification in Yandex.Webmaster and Google Search Console.
How to Avoid Title Duplicates During Bulk Setup?
A common problem is duplicate titles on product pages. The solution is configuring meta tag templates via the SEO module. After proper setup, indexing increases by 50%. If meta tags do not display, check the presence of the bitrix:seo.meta component in the template and reset the infoblock cache. This resolves the issue in 80% of cases.
Table: Typical Problems and Solutions
| Problem |
Solution |
Result |
| Duplicate titles on product pages |
Configure meta tag templates via SEO module |
50% increase in indexing |
| Meta tags not displaying |
Connect bitrix:seo.meta and reset cache |
Correct output on 100% of pages |
| Verification code not displayed |
Add code via the Webmaster section |
Indexing of new pages within 2-3 days |
Comparison of Meta Tag Setup Methods
| Method |
Flexibility |
Update Speed |
Duplicate Risk |
| SEO module templates |
High |
High |
Low |
Manual via SetPageProperty() |
Medium |
Low |
Medium |
seo.meta component |
High |
High |
Low |
SEO module templates are 3 times faster in update speed than manual setup: adding a new infoblock only requires creating a template, not editing every file.
Webmaster and Indexing
In Marketing → Search Engine Optimization → Webmaster, add verification codes from Yandex.Webmaster and Google Search Console. Bitrix automatically inserts the verification meta tag in <head>. This speeds up indexing of new pages by 2-3 times.
Meta Tags for Static Pages
For the homepage and static pages, meta tags are set via $APPLICATION->SetPageProperty():
$APPLICATION->SetPageProperty('title', 'Home — Online Store');
$APPLICATION->SetPageProperty('description', 'Wide range of products with delivery across Russia');
This call should be before the <head> output, typically in the component template.
What's Included
- Audit of current SEO module and meta tag setup
- Configure templates for all infoblocks and pages
- Connect and configure the
seo.meta component
- Verify site in search engines
- Check and reset cache
Timelines and Guarantees
SEO module setup takes 3 to 5 hours, depending on the number of infoblocks. We guarantee correct meta tag display on all pages. Pricing is individual. Contact us for a consultation and project evaluation.
According to 1C-Bitrix documentation, the SEO module supports templates with arbitrary properties.
Search engine optimization is a set of measures to improve site visibility in search engines. Proper setup of the Bitrix SEO module is the first step to effective promotion.
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.
