Redirect Management Module for 1C-Bitrix

After migrating a site to a new URL structure, Google Search Console often shows thousands of 404 errors. Old URLs like /catalog/product-123.html need to redirect to /catalog/category/product-name/. Writing 8,000 redirects in .htaccess is possible, but Apache slows down parsing that file on every request, and manual editing is painful. Our redirect management module solves this by storing rules in the database with a convenient interface, importing from any format, and providing analytics.

With over a decade of experience on Bitrix and 500+ completed projects, we've built more than 50 such modules for clients ranging from e-commerce stores to large corporate portals.

Why a Module Is Better Than .htaccess

Apache noticeably slows down when the number of RewriteRule directives exceeds 500–1000: the file is parsed for every request unless caching is configured. Nginx reads the config once at startup, but restarting it for each new redirect in production is impractical.

Storing rules in the database and processing them with PHP is a compromise: slightly slower than a hardware-level Nginx redirect (by 20–30%), but it allows real-time rule management without service restarts. Plus, you get change history, hit statistics, import/export, and everything in the familiar Bitrix admin panel.

A cached handler runs 10 times faster than an uncached one: checking a redirect for a static URL takes under 1 ms.

What We Deliver

Architecture

Rule table:

CREATE TABLE myvendor_redirect (
    id          SERIAL PRIMARY KEY,
    source      VARCHAR(500) NOT NULL,
    destination VARCHAR(500) NOT NULL,
    code        SMALLINT NOT NULL DEFAULT 301,
    is_regex    BOOLEAN DEFAULT false,
    priority    INT DEFAULT 100,
    hits        INT DEFAULT 0,
    active      BOOLEAN DEFAULT true,
    created_at  TIMESTAMP DEFAULT NOW(),
    created_by  INT
);

CREATE UNIQUE INDEX idx_redirect_source ON myvendor_redirect(source) WHERE NOT is_regex;
CREATE INDEX idx_redirect_active ON myvendor_redirect(active, priority);

Handler. Rules are loaded in the OnPageStart event. Static rules (exact URL match) are checked first via isset on an associative array — O(1). Regular expressions are evaluated only if no static match is found, iterating over rules sorted by priority.

AddEventHandler('main', 'OnPageStart', [\MyVendor\Redirect\Handler::class, 'handle']);

Documentation for the OnPageStart event is available at dev.1c-bitrix.ru.

Caching. The entire rule list is cached with Bitrix tagged cache. When any rule changes, the cache is invalidated. TTL is 1 hour as a safeguard against missed cache busting.

Import from .htaccess and CSV

After a migration, clients typically have either an old .htaccess or an Excel file with old and new URLs. The module includes parsers for both.

.htaccess parser:

// Example line: RewriteRule ^old/(.*)$ /new/$1 [R=301,L]
preg_match('/^RewriteRule\s+\^([^\$]+)\$?\s+(\S+)\s+\[([^\]]+)\]/', $line, $m);

The module extracts source, destination, redirect code, and the regex flag. Rules with complex conditions (RewriteCond) are imported with a warning — they need manual review.

CSV import:

1. Prepare a CSV file with columns old_url;new_url;code.
2. Upload the file in the module's Import section.
3. The module checks for duplicates and cyclic redirects.
4. After successful validation, rules are added to the database.
5. Verify redirects work via the 404 log.

Before import, validation includes: duplicate sources, cyclic redirect check (A → B → A), and optional destination reachability via HEAD request.

How We Detect 404 Errors

The module logs 404 responses to table myvendor_redirect_404. In the admin interface, a list of the most frequent 404 URLs is displayed with hit counts and a "Create redirect" button for each. This is the primary tool for migration: you see the most requested non-existent URLs and create redirects in one click.

Statistics and Analytics

Each redirect hit increments the hits counter. In the interface, you can sort rules by hits to identify popular redirects and, conversely, find "dead" rules (no hits in 90 days) that are candidates for removal.

A Real-World Case

For a large e-commerce site with 12,000 SKUs, migrating from /category/product.php?ID=123 to /category/subcategory/product-name/ generated over 3,000 404s. Our module imported the old URL mapping from a CSV file, validated for cycles, and implemented redirects with caching. The 404 count dropped to zero within a week, and organic search traffic recovered fully in 14 days.

Process and Timelines

Our typical workflow:

1. Data collection — gather existing URL mappings, logs, and .htaccess files.
2. Audit & Analysis — identify the most frequent 404s, assess impact.
3. Design — define rule structure, caching strategy, and import format.
4. Estimation — provide a fixed quote after analysis.
5. Development — build the module with all required features.
6. Testing — unit tests, import validation, and performance benchmarks.
7. Launch — deploy and monitor 404 reduction.

To get an accurate estimate for your project, contact us — we'll prepare a proposal based on your specific needs.

Common Mistakes to Avoid

• Not clearing the cache after import — always flush the tagged cache to make new rules active immediately.
• Ignoring trailing slashes — inconsistent use of trailing slashes causes misses; we recommend normalizing all URLs.
• Using 302 permanently — use 301 for permanent moves, 302 for temporary, to avoid diluting link equity.
• Forgetting to test — always test a sample of rules after import, especially regex ones, to ensure they match as expected.

Contact our specialists to discuss your project — we'll help set up the import, verify integrity, and enable caching. Eliminate 404 errors and preserve your SEO traffic.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.