301 Redirects in 1C-Bitrix: Save Traffic & Rankings

Setting Up 301 Redirects in 1C-Bitrix: How Not to Lose Traffic

When changing a site's URL structure—switching to HTTPS, migrating to new SEF URLs, or merging multiple sites—without properly configured 301 redirects, search rankings plummet. According to our statistics, traffic loss can reach 80% in the first week. A 301 redirect is an HTTP status that tells search engines: the page has moved permanently, pass the link equity to the new address. According to Wikipedia, this code preserves over 90% of ranking signals. Over 90% of link equity is transferred via 301 redirects, and traffic loss can exceed 80% without them. For an e-commerce site with 10,000 monthly visitors, proper 301 redirect setup saves $3,000–$5,000 per month in PPC budget. In 1C-Bitrix, there are several ways to set it up, and choosing the right method is critical for performance and implementation time. Over 10+ years of work on hundreds of projects, we have developed reliable scenarios: from simple protocol redirect to mass migration with thousands of rules via CURLRewrite. Below we break down each approach with code examples and give recommendations for selection.

$res = \CIBlockElement::GetList([], ['IBLOCK_ID' => 5], false, false, ['ID', 'CODE']);
while ($el = $res->Fetch()) {
    \CURLRewrite::Add([
        'SITE_ID'  => 's1',
        'SORT'     => 100,
        'CONDITION'=> '^/catalog/element-' . $el['ID'] . '\.html$',
        'RULE'     => '/catalog/' . $el['CODE'] . '/',
        'TYPE'     => '301',
    ]);
}

Setting Up 301 Redirects in Bitrix: Three Methods

Bitrix offers three approaches: via the 'Site Management' module, the SEO module, and the web server configuration (.htaccess/nginx). Each has its strengths. Apache mod_rewrite directives and nginx location blocks provide server-level redirects.

Site Management module—for global redirects (http→https, www→non-www). Path: Settings → Product Settings → URLs. Check the 'Redirect from HTTP to HTTPS' option—the kernel automatically issues CMain::Redirect() in the prolog. This takes 15 minutes and requires no .htaccess edits. Performance is high thanks to caching, but flexibility is low—only protocol and subdomain.

SEO module—for targeted rules with regular expressions. Marketing → Search Engine Optimization → Redirects. Add a rule with source and destination. Supports priorities and conditions. For over 100 rules, be sure to enable tagged caching to avoid database load.

.htaccess / nginx—for maximum performance. Server-level redirect fires before PHP, making it 2–3 times faster than the SEO module, especially with hundreds or thousands of rules. Example for Apache:

Redirect 301 /old-section/ /new-section/
RewriteRule ^old-catalog/(.*)$ /catalog/$1 [R=301,L]

For nginx:

location ~ ^/old-catalog/(.+)$ { return 301 /catalog/$1; }

Choosing a method depends on volume: up to 100 rules—SEO module; thousands—server rules.

Why Mass Redirects Are Better Done via Scripts

When changing URL structure—e.g., switching from ID to symbolic code in a catalog of 5000 products—manually adding 5000 rules is unrealistic. We use a script with CURLRewrite::Add() that generates records based on ID and the new symbolic code. Example script in the collapsible block above. This approach takes 1–2 hours instead of a week of manual work. For 301 redirects on Bitrix with thousands of URLs, using CURLRewrite scripts ensures efficient redirection and preserves SEO rankings. After generation, we apply tagged caching and verify in Google Search Console—404 errors completely disappear.

Using CURLRewrite for Large-Scale 301 Redirects

If you have more than 500 URLs to redirect and all rules are of the same type (e.g., replacing ID with CODE), the script approach is the only sensible one. It's also useful when migrating from another CMS to Bitrix, when you need to mass-map old URLs to new ones.

Comparison of Redirect Methods

HTTPS redirect via the Site Management module is 1.5 times faster than an analogous rule in .htaccess, but lags behind nginx with a large number of rules.

Typical Scenarios and Solutions

What's Included in the Work

• Audit of current URLs—analysis of broken links, redirect map.
• Rule planning—choosing the method appropriate for volume.
• Rule generation—via SEO module or scripts.
• Testing—check for cyclic redirects and response codes.
• Monitoring—track traffic and errors via Search Console for a week.
• Documentation and dashboard access handover.

Turnkey Setup Process

1. Audit of current URLs—analysis of broken links, redirect map.
2. Rule planning—choosing the method appropriate for volume.
3. Rule generation—via SEO module or scripts.
4. Testing—check for cyclic redirects and response codes.
5. Monitoring—track traffic and errors via Search Console. The entire process takes 2 to 6 hours depending on volume. Starting at $200, you can save up to 80% of your advertising budget by avoiding traffic loss. We guarantee transparency—using only licensed Bitrix and official certificates.

Poorly configured redirects can cost up to 30% of rankings. Savings on proper setup can be up to 80% of the advertising budget. Get a consultation for your project—contact us, and we will propose the best solution.

Order 301 redirect setup and save your traffic.

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.