What this solution does
The module tracks HTTP 404 errors, generates a list of the most frequent broken URLs, manages redirect rules (301, 302, and others), and suggests similar pages to fix 404 errors.
Settings are available via Settings → Product Settings → Module Settings → ecl.404monitor, or through the Settings button on the dashboard.
The module is enabled by default, activating both tracking and redirect functions. Logging of 404 errors is turned on, while requests from bots and crawlers are skipped based on the User-Agent header. URLs are normalized by removing the query string. Raw visit data is stored for 90 days (minimum 7) before being automatically cleaned. The Top 404 list includes only URLs with a hit count of at least three.
The default redirect code is 301. Only valid codes are supported: 300, 301, 302, 303, 307, 308. For finding suggestions, specific information blocks can be selected, or all active blocks can be used. Search is performed across fields: Name, Code, Preview, Detailed description, Tags, and via the Bitrix search module. System paths such as /bitrix/ or /upload/ are excluded from logging.
Entering invalid HTTP codes in settings or redirect forms is rejected. The main interface is located in Services → 404 Monitor, where the module status and current logging state are displayed.
The 404 Monitor with Redirects module by eCom Labs provides a management panel for analyzing errors and handling redirects. The dashboard displays key metrics: the number of 404 errors in the last 24 hours and 7 days, the count of unique URLs with errors, and the number of active redirect rules. Quick links allow immediate access to the list of top 404 errors, the general redirect list, or system settings.
The top 10 error URL section displays a table showing the hit count and the dates of the first and last occurrence for each page. If no redirect rule exists for a URL, a button to create a new redirect is available. If a rule already exists, the system offers to open the redirect, displaying the target address. The list can be filtered by the minimum hit count configured in the settings.
The redirect rules list includes information on the source and target URLs, the HTTP code used, activity status, and the number of triggers. Bulk operations are available for all rules, including deletion, activation, and deactivation. The interface also supports adding new rules.
When editing or creating a redirect, users fill in the source and target fields and select an HTTP code (301, 302, or another code from the whitelist). The system provides suggestions for source URLs based on search settings; clicking a suggestion automatically populates the target field. Rule saving is handled via the Redirector::addRule method, which automatically validates fields for emptiness, checks for redirect loops, and verifies the code.
The ecl:404.suggest component is designed to display similar pages on the 404 error page. To include it in a 404.php template, use the $APPLICATION->IncludeComponent method with parameters LIMIT (number of suggestions from 1 to 20) and TITLE (block header, which defaults to the language file if empty). The component logic relies on the current request URL.
The 404 monitor with redirects module by eCom Labs sanitizes tokens in paths: only letters and digits are allowed, length limits are applied, and SQL injection is prevented. Search across selected information base fields (NAME, CODE, etc.) is performed via the information block API. The search module functionality is enabled when the corresponding attribute is present. Styling is located in the file templates/.default/styles.css.
General iT can connect “404 Monitor with Redirects (EcomLabs)”, install and configure the module, and make sure the integration works correctly.