1C-Bitrix Sitemap Configuration: Step-by-Step Guide

Configuring Sitemap in 1C-Bitrix

On one project, we found that the sitemap included 120,000 URLs, 70% of which were duplicates with sorting parameters. After setting up exclusion rules, the number of URLs dropped to 35,000, and the indexing of key pages increased by 60% within two weeks. Without a correct sitemap, search engines index service pages while important categories remain unnoticed. Our team, with over 5 years of experience and 50+ Bitrix projects, helps avoid these mistakes. This article explains how to configure sitemap in 1C-Bitrix properly to speed up indexing by 2-3 times.

How is the sitemap generated in Bitrix?

The sitemap is created by the SEO module (seo). It generates an XML file according to the Sitemap Protocol 0.9. Configuration is done in the admin interface: Marketing → Search Optimization → Sitemap. Each source (ruleset) defines a set of URLs, update frequency (changefreq), priority (priority), and last modification date (lastmod).

For large catalogs, source configuration is critical: one wrong filter can add thousands of duplicates. For example, a source with type "Site pages" includes all URLs, including /bitrix/ and /local/, if no exclusions are set. Therefore, it's important to use exclusion patterns.

Why is it important to exclude technical pages?

A common mistake is not excluding pages with parameters: /catalog/?sort=price, /catalog/?page=2. Search engines treat these as separate URLs, wasting the crawl budget. Bitrix allows exclusion via patterns:

/catalog/*?*
/search/*
/bitrix/*
/local/*
/personal/*
/auth/*

Also disable the option "Include elements with empty detail URL" in the source settings — this removes products without SEO-friendly URLs. On one project, we eliminated 40,000 duplicates with just this action.

How to set up automatic generation?

Manual generation is only for testing. In production, the sitemap must be created automatically. Enable the option Automatic creation via agent. The agent CSeoSitemapAgent::generateSitemap() runs on schedule: once a day for most sites, once an hour for news sites. If the site is large and the agent doesn't complete, use cron. Configuring sitemap via cron is 2 times faster than the standard agent because it's not dependent on hit load.

0 3 * * * /usr/bin/php -f /home/bitrix/www/bitrix/modules/seo/lib/sitemap/generator.php

Official 1C-Bitrix documentation: helpdesk.bitrix24.ru

What to do when exceeding 50,000 URLs?

Bitrix automatically splits the map into multiple files and creates an index sitemap_index.xml. In settings, you can specify the maximum size of one file. Example resulting structure:

/sitemap_index.xml        → links to separate files
/sitemap_0.xml            → site pages
/sitemap_1.xml            → catalog sections
/sitemap_2.xml            → products 1–50000
/sitemap_3.xml            → products 50001–...

Generating 50,000 URLs takes about 10 seconds on a typical hosting. If your site has more than 200,000 pages, we recommend splitting sources by category for speed.

Registration in Webmaster Panels

After generation, submit the sitemap URL to Yandex.Webmaster and Google Search Console. In Bitrix, this can be done directly from the section Marketing → Search Optimization → Webmaster after adding verification codes. Also add a line to robots.txt:

Sitemap: https://your-site.ru/sitemap_index.xml

Comparison of efficiency before and after configuration:

What's included in turnkey sitemap configuration?

• Audit of current sitemap (identify duplicates, errors, missing sections).
• Configuration of sources with optimal changefreq and priority.
• Setting up exclusion rules for technical pages.
• Enabling automatic generation via agent or cron.
• Checking index file and submitting to search engines.
• Integration with robots.txt.
• Documentation of settings and recommendations for updates.

Timeline

Basic sitemap configuration takes 1 to 2 hours. For complex projects with thousands of sources, up to half a day. Cost is calculated individually based on the scope. Contact us for a free audit of your sitemap. Order turnkey sitemap configuration and get a consultation from certified specialists.

How we do it?

1. Analyze current site structure and identify problem areas.
2. Design source configuration considering business logic.
3. Implement settings in the admin section.
4. Test generation and verify correctness of sitemap_index.xml.
5. Deploy to production server and monitor indexing.

Contact us — we'll evaluate your project and offer the optimal solution with a result guarantee. We guarantee the quality of sitemap configuration in Bitrix.

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.