Configuring SEF URLs for 1C-Bitrix Filters
Configuring SEF URLs for Catalog Filters
The standard Bitrix smart filter generates URLs like /catalog/section/?arrFilter_pf_COLOR=red&arrFilter_pf_SIZE=XL — search engines see thousands of parametric pages with duplicate content and cannot determine which one to index. The result: keyword cannibalization, a drop in faceted query traffic, and an endless crawl budget wasted on junk URLs.
SEF URLs for filters solve this problem: each parameter combination gets a readable address /catalog/footwear/sneakers/color-red/size-42/, which can be included in the sitemap, equipped with meta tags, and targeted with link-building.
How the SEF Mechanism Works in the Smart Filter
Bitrix stores SEF settings in the b_iblock_section_url table and in the properties of the bitrix:catalog.smart.filter component. For each property value, a symbolic code (CODE) is defined that is substituted into the URL template.
The template is specified in the SEF_URL_TEMPLATES parameter of the catalog wrapper component:
'FILTER_URL' => 'catalog/#SECTION_CODE_PATH#/#FILTERS#/',
The #FILTERS# variable is assembled from property-code-value pairs separated by a delimiter defined in the component settings (typically /).
The routing engine parses the incoming URL, reconstructs the filter array, and passes it to the component. If a property or value symbolic code contains Cyrillic characters or special symbols, the route will break. Therefore, before configuration, all CODEs must be normalized to latin+digits+hyphen.
What We Do as Part of the Service
Audit of current URL parameters. We export all infoblock properties and check value codes. We identify collisions: identical codes for different properties, empty codes, Cyrillic characters.
Fixing symbolic codes. We update value codes via the admin interface or directly in b_iblock_property_enum with a backup update. For high-load catalogs (50,000+ SKUs) — a batch SQL script with a transaction.
SEF template configuration. We configure SEF_URL_TEMPLATES for the specific catalog structure: single-level, multi-level, with brands in the URL. We account for compatibility with paginated navigation.
301 redirects from old URLs. If the site is already indexed by GET parameters — we configure redirects via .htaccess or nginx map to preserve the accumulated page authority.
Canonical and robots verification. For combinations that should not be indexed (more than two filters, zero results), we configure canonical to the root category and noindex via the meta tag component.
Generation and sitemap inclusion. We collect a list of priority SEF combinations (based on Wordstat or Search Console data) and add them to the XML sitemap via the Bitrix SEO module or a custom agent.
Common Problems and Solutions
Conflict with paginated navigation. Page 2 in a SEF filter gets the URL /catalog/sneakers/color-red/page-2/. If the template does not account for PAGEN_1, the component resets the filter on the second page. Solution: add #PAGE# to the template and handle it in template.php.
Duplicates with different parameter order. /color-red/size-42/ and /size-42/color-red/ — different URLs, same content. Bitrix does not sort parameters by default. We add sorting in the smart filter's result_modifier.php and set a canonical to the canonical sequence.
URLs that are too long. With 5+ parameters, the URL exceeds 200 characters. Search engines index such pages less effectively. We limit SEF to two or three parameters; the rest are delivered via GET with noindex.
Result
After configuring SEF URLs, faceted pages become full-fledged SEO units: a unique URL, manageable meta tags, correct canonical, and inclusion in the sitemap. Typical traffic growth from low-frequency faceted queries — between 20 and 60% within three months of re-indexing.