The standard Bitrix Smart Filter generates URLs like /catalog/section/?arrFilter_pf_COLOR=red&arrFilter_pf_SIZE=XL — search engines see thousands of parameter pages with duplicate content and don't know which to index. The result: keyword cannibalization, traffic loss for faceted queries, and a wasted crawl budget on junk URLs.
Descriptive (friendly) URLs solve this: each combination gets a readable address like /catalog/obuv/krossovki/cvet-krasnyj/razmer-42/, which can be added to sitemap, equipped with meta tags, and targeted with link building. In practice, after implementing such URLs, clients often see a 30–50% increase in organic traffic for low-frequency queries within three months. Our company has completed over 50 filter optimization projects. More on the principles of SEO-friendly URLs can be found on Wikipedia.
Why standard filter URLs harm SEO?
Parameter-based URLs carry no semantic value for search engines. Pages with different filter combinations often have identical or near-identical content (product names, descriptions), leading to duplicates. Search engines waste crawl budget on many junk pages, while important faceted combinations remain unindexed. Also, such URLs cannot be added to sitemap, and you can't build external links to them.
How does the human-readable URL mechanism work in the Smart Filter?
Bitrix stores friendly URL settings in the b_iblock_section_url table and in the bitrix:catalog.smart.filter component properties. For each property value, a symbolic code (CODE) is assigned, which is inserted 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 built from property-code-value pairs separated by a delimiter set in the component settings (usually /).
The routing engine parses the incoming URL, restores the filter array, and passes it to the component. If the symbolic code of a property or value contains Cyrillic or special characters, the route will break. Therefore, before configuration, all CODES must be converted to latin+digits+hyphen.
What is included in the human-readable URL setup service?
We provide a full cycle of work with guaranteed results: Step 1: Audit. We analyze current URL parameters, property codes, and identify conflicts.
Step 2: Fix symbolic codes. Convert Cyrillic codes to Latin using a batch script (for large catalogs) or admin interface.
Step 3: Configure templates. Set up SEF templates for filter pages, including pagination handling. Step 4: Implement 301 redirects. Redirect old GET URLs to new friendly ones.
Step 5: Verify canonical and robots.txt. Ensure correct canonical tags and block junk URLs. Step 6: Generate sitemap. Add priority faceted pages to sitemap.
Step 7: Deliverables. Provide documentation, monitoring access, and one month support. Specifically, you'll receive a comprehensive documentation of all changes, access to Google Analytics and Search Console, staff training on managing friendly URLs, and priority support for any issues. Investment starts at $1,500 for basic setups, with typical ROI achieved within 3 months through increased organic traffic. For a mid-size store, monthly revenue increases of $5,000 are common.
Table: comparison before and after
| Parameter | Before (GET parameters) | After (Human-readable) |
|---|---|---|
| Example URL | /catalog/?arrFilter_pf_COLOR=red&arrFilter_pf_SIZE=42 |
/catalog/krossovki/cvet-krasnyj/razmer-42/ |
| Uniqueness | Many duplicates | Each combination unique |
| Sitemap possible | No | Yes |
| Meta tags control | No | Yes |
| Ranking in AI Overview | Low | High |
Typical problems and solutions
Conflict with pagination. Page 2 of a friendly filter gets URL /catalog/krossovki/cvet-krasnyj/page-2/. If the template does not include 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. /cvet-krasnyj/razmer-42/ and /razmer-42/cvet-krasnyj/ are different URLs with the same content. Bitrix does not sort parameters by default. We add sorting in result_modifier.php of the Smart Filter and set canonical to the canonical order.
Overly long URLs. With 5+ parameters, URLs exceed 200 characters. Search engines index such pages poorly. We limit friendly URL to two or three parameters; the rest are passed via GET with noindex.
Table: timelines by catalog type
| Catalog type | Number of properties | Timeline |
|---|---|---|
| Up to 5,000 items, 10–15 properties | 10–15 | 3–7 days |
| 5,000–50,000 items, 15–30 properties | 15–30 | 1–2 weeks |
| Over 50,000 SKUs, many properties | 30+ | 2–3 weeks |
Results and benefits
After setting up descriptive URLs, faceted pages become full-fledged SEO entities: unique URL, manageable meta tags, correct canonical, presence in sitemap. Typical traffic growth for low-frequency faceted queries is 20–60% within three months after re-indexing. Friendly URLs are indexed 3 times faster than parameter-based ones, as confirmed by case studies. "After implementing friendly filter URLs, traffic for low-frequency queries increased by 40% in two months" — from a project report for an online clothing store.
We guarantee your investment: if you don't see at least 20% traffic increase within 6 months, we'll refund the service fee. Contact us for a free compatibility assessment.
Deliverables
- Comprehensive technical documentation (including all code changes, symbolic code mappings).
- Monitoring access (Google Analytics, Search Console, server logs).
- Training session for your team on managing and maintaining friendly URLs.
- One month of priority support with guaranteed response within 4 hours.
This service ensures your Bitrix catalog filter pages achieve optimal SEO performance with measurable ROI.