Human-Readable URLs for Bitrix Smart Filter

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

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

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.

How Do Proper SEO Settings for 1C Bitrix Affect Traffic?

We often encounter projects where the seo module generates titles using the template #ELEMENT_NAME# — buy in online store. On a catalog of 20,000 products with facet filters, this produces thousands of identical titles, duplicates from pagination, and GET parameters indexed by Yandex and Google as separate pages. After proper SEO settings for 1C Bitrix, the crawling budget is spent only on selling pages — the result is visible in 2–3 weeks. Experience from over 50 Bitrix projects confirms that without technical intervention, up to 60% of traffic is lost. For example, by reducing the budget for contextual advertising by 40% ($2,000/month saved), we maintained the same number of leads through organic traffic.

Why Does the Smart Filter Generate 70% Duplicates and How to Fix It?

The catalog.smart.filter component creates URLs with GET parameters: /catalog/?brand=nike&color=white&size=42. Thousands of combinations waste the crawl budget and cause main categories to drop in rankings.

The solution is the SEO module of the smart filter (iblock.property.type + custom URLs):

• Identify promoted combinations: "Nike sneakers", "white men's sneakers", "sneakers under a certain price". These pages receive SEF URLs (/catalog/krossovki/nike/), unique title, description, H1, and SEO text.
• Other combinations are closed with noindex, follow in meta robots + Disallow in robots.txt for parameterized URLs.
• Settings are stored in b_iblock_section_property and a custom SEO rules table — the content manager handles them from the admin panel without a developer.

Practice: For an online clothing store, we cut off 95% of junk combinations. The number of indexed pages jumped from 3,000 to 14,000 in a month, and the cost per customer acquisition dropped by 20% (saving roughly $0.50 per lead).

Our SEO settings for 1C Bitrix address three key areas: meta tags, technical SEO, and microdata. Each area directly impacts search visibility and user acquisition cost.

Meta Tags: Three Levels of Refinement

Level 1 – Templates in IBlock Settings

Settings → Information blocks → Information block types → [information block] → SEO. Variables: {=this.Name}, {=parent.Name}, {=this.PreviewText}, {=this.Property.BRAND}. Formulas differ for each information block:

• Clothing: {=this.Property.BRAND} {=this.Name} — buy, price from {=this.Property.MIN_PRICE} RUB
• Equipment: {=this.Name} {=this.Property.ARTICLE} — characteristics, price, delivery

Level 2 – Manual Refinement of Key Pages

Homepage, main categories, top 30 products by traffic. Manual title and description via element properties or through $APPLICATION->SetPageProperty(). These pages generate 60–80% of organic traffic.

Level 3 – SEO Filters

Unique meta tags for promoted smart filter combinations. Configured via a custom table or modules like aspro.seo / sotbit.seometa. Each combination gets its own title, description, H1, and text block.

How Does Schema Microdata Increase CTR by 1.5 Times?

JSON-LD in <head> — implemented via component_epilog.php or a custom component:

• Product — name, image, description, sku, brand, offers.price, offers.priceCurrency, offers.availability. Data from CIBlockElement::GetByID() + CCatalogProduct::GetByID()
• AggregateRating — average rating from an information block property. Star ratings in snippets increase CTR by 15–30%
• BreadcrumbList — navigation chain with @type: ListItem
• Organization — name, address, phone, logo, sameAs
• FAQPage — question-answer blocks that push competitors down
• WebSite + SearchAction — search bar directly in snippet: potentialAction.target leads to /search/?q={search_term_string}

Validate markup using Google Rich Results Test and Yandex Webmaster. We guarantee a 20% CTR increase for pages with microdata after integration. The Schema.org vocabulary (maintained by Google, Microsoft, Yahoo, and Yandex) enables rich snippets that are 1.5 times more clickable than standard listings.

Technical SEO Configuration: SEF URLs, Canonical, Redirects, Sitemap

SEF URLs: Where Bitrix Stumbles

Settings in urlrewrite.php and SEF_MODE of components. Typical problems:

• Excessive nesting — /catalog/odezhda/zhenskaya/platya/letniye/product-123/. Google recommends no more than three levels. Restructure: /catalog/platya-letniye/product-123/
• Trailing slash duplicates — /catalog/shoes and /catalog/shoes/. Solution: merge_slashes on in Nginx + 301 redirect
• www and non-www — one canonical domain, 301 redirect at Nginx level
• Symbolic codes — CIBlockElement::Add() supports auto-generation of CODE via transliteration. Setting: b_iblock → FIELDS → CODE → TRANSLITERATION. Standard — ISO 9.

Canonical and Duplicate Handling

$APPLICATION->SetPageProperty("canonical", $url) in component templates. Rules:

• Pagination: canonical of first page for ?PAGEN_1=2, ?PAGEN_1=3
• Sorting: ?sort=price&order=asc → canonical without parameters
• Filters: non-promoted combinations → canonical to parent section
• hreflang for multilingual sites — each version references all others + x-default
• noindex, follow for technical pages

301 Redirects During Migration

Moving from another CMS or restructuring — without 301 redirects, link equity is lost.

• Mass redirects via b_urlrewrite table or Nginx map. For 10,000+ URLs — only Nginx map
• Auto-redirect on CODE change — handler OnBeforeIBlockElementUpdate saves old URL in custom table, init.php checks 404 and performs 301
• Eliminate chains: A → B → C replace with A → C (1% PageRank loss per hop)
• Single URL format: www/non-www, HTTP/HTTPS, with/without trailing slash

The 301 redirect standard is defined in RFC 7231 (HTTP/1.1 Semantics and Content) and explained on Wikipedia — every chain costs PageRank.

sitemap.xml via SEO Module

Default settings are weak: pagination pages, search results, cart appear. We configure:

• Exclude junk through module settings
• Differentiate priority and changefreq: homepage – 1.0 / daily, categories – 0.8 / weekly, products – 0.6 / weekly, articles – 0.5 / monthly
• For catalogs > 50,000 URLs – sitemap-index with split: sitemap-products.xml, sitemap-categories.xml, sitemap-articles.xml
• Multilingual site – separate maps with hreflang via xhtml:link

robots.txt – Protecting Crawl Budget

User-agent: Yandex
Disallow: /bitrix/
Disallow: /auth/
Disallow: /personal/
Disallow: /search/
Disallow: /cart/
Disallow: /compare/
Clean-param: utm_source&utm_medium&utm_campaign&utm_content&utm_term
Clean-param: sort&order&PAGEN_1
Crawl-delay: 0.5

User-agent: Googlebot
Disallow: /bitrix/
Disallow: /auth/
Disallow: /personal/
Disallow: /search/
Disallow: /cart/

Sitemap: https://site.ru/sitemap.xml

Learn more about the Clean-param directive in Yandex documentation. For Google, use canonical + Search Console settings.

Index Management

• Yandex Webmaster + Google Search Console – verification, crawl error monitoring, index coverage
• Crawl budget: if out of 50,000 URLs in sitemap only 5,000 are indexed – clean robots.txt, remove duplicates, close noindex
• 404 and soft-404 errors – from webmaster reports. 301 to relevant page or 410 (resource permanently deleted)
• Monitor drops: sharp decline in indexed pages – check robots.txt and canonical

How Does Loading Speed Affect Ranking?

• Composite cache – \Bitrix\Main\Composite\Engine turns a dynamic page into static HTML. First hit – PHP render, subsequent hits – delivery in milliseconds. Composite cache speeds up page delivery 10x compared to dynamic rendering. Setup: Performance → Composite Site, exceptions for cart and personal account
• Images – convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + lazy loading (loading="lazy"). Specify width / height to prevent CLS
• CSS/JS – combine and minify: Settings → Product Settings → CSS / JS Optimization. Inline critical CSS
• CDN – static assets go to edge nodes via CDN settings in admin panel
• Server – Brotli/gzip, HTTP/2, OPcache with opcache.jit on PHP 8.1+, caching headers Cache-Control: public, max-age=31536000 for static files

Work Process: Step by Step

1. Audit – analyze current state: meta tags, URL structure, indexing, speed, microdata. Generate a prioritized report.
2. Design – agree on plan: which pages get canonical URLs, which are closed, meta tag templates, list of redirects.
3. Implementation – configure SEO module, SEF URLs, robots.txt, sitemap.xml, implement JSON-LD. Write custom handlers for auto-redirects and SEO filters.
4. Testing – check via Google Search Console, Yandex Webmaster, Screaming Frog. Ensure duplicates disappear, crawler visits only relevant pages.
5. Deploy and Monitor – push to production, monthly reports on indexing and traffic. Adjust as needed.

What Does SEO Configuration Include?

After deployment we provide two weeks of free post-launch monitoring and hotfixes. Extended support is available on a monthly retainer.

Timelines

We evaluate a project within 1 day. Get a consultation—we will answer questions about your catalog and provide a free audit of your current index status. Experience with Bitrix—over 10 years, more than 50 SEO optimization projects. Organic traffic growth without extra advertising costs is achievable. Contact us to discuss your project. Request a free audit now.