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.
Bulk Rule Generation Script via CURLRewrite
$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
| Method | Performance (requests/sec) | Flexibility | Implementation complexity |
|---|---|---|---|
| Site Management module | High (with cache) | Low | Minimal |
| SEO module | Medium (up to 1000 rules) | High | Medium |
| .htaccess / nginx | Maximum (no PHP) | Medium | Requires server access |
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
| Situation | Solution | Tool |
|---|---|---|
| Domain change | Permanent redirect from each URL | .htaccess / nginx |
| Page deletion | Redirect to a relevant page | SEO module |
| Catalog SEF change | Mass rules by ID via CURLRewrite | Script |
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
- 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. 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.