The Bitrix smart filter can provide shoppers with a convenient collection, but filter usability and search readiness are different things. First, make sure the URL actually restores the selected criteria and shows the right products. Then decide which collections merit appearing in search as standalone pages.
This article covers the boxed version of “11C-Bitrix: Site Management” and the catalog.smart.filter component. Marketplace solutions may add their own SEO rules. If such a solution is installed, include it in the task description: the standard filter does not automatically guarantee unique text and correct canonical URLs for every combination.
Which collections to open first
Choose a short list of pages that shoppers need as standalone collections. For example, ventilation grilles made of a particular material or intended for a specific use. A page should have a clear topic and a sufficient selection of products; a combination of a service attribute and an arbitrary price range does not become a landing page just because it has a neat URL.
For each selected collection, record the section, filter criteria, expected products and visitor’s goal. If you do not know whether there is demand for the search term, say so: “Demand has not yet been checked.” Technically opening a page does not prove that it will attract visits.
Leave other combinations as a convenient selection tool, but give them a separate indexing policy. Do not open thousands of combinations before checking a few required pages. Scale a verified rule with clear exceptions: empty results, discontinued products, sorting and pagination.
What to check in the smart filter setup
The Bitrix component documentation specifies the data source and URL management parameters. An SEO-friendly URL uses readable path segments instead of a service script address. The relevant settings are SEF_MODE, SEF_RULE and SMART_FILTER_PATH. The filter and product list must apply the criteria consistently: a form with selected checkboxes does not by itself prove that the list is filtered.
Ask the developer to record the actual component parameters and where the component is connected. Check the catalog section, information block ID and output filter name. With a custom implementation, one array may be prepared by the filter while the product list reads another. In that case, the URL and count change, but the products remain the same.
Do not copy the example SEO-friendly URL rule from the documentation wholesale into the live catalog. Your catalog folder and the way its section is identified are site-specific. The task should specify consistent routes for the composite catalog, filter and list, and include a check that the URL opens directly after clearing the browser session.
A teaching example with two materials
Imagine a grille catalog with aluminum and steel products in one section. This is a fictional example. The owner wants a separate page for aluminum grilles, but not a separate page for every price sort order.
They save the URL generated by the actual filter after selecting the material. The illustrative path /catalog/grilles/filter/material-aluminium/apply/ shows the page’s purpose; the specific filter syntax is generated by your site’s component. Give the developer the actual URL, not an invented string from the example.
For testing, list several SKUs that should appear in the collection and one steel product that should not. Then open the URL in a new window. The selected material, heading and products must match the task. If all grilles appear after opening the URL directly, the page has not restored the filter criteria and is not ready for further SEO configuration.
How to set rules for useful pages and duplicates
For the selected aluminum collection, agree on a dedicated URL, title, heading and a brief explanation of the selection. Canonical is a recommendation to the search engine about which URL to treat as primary. It should reflect the decision about whether the page is standalone. If the collection is intended as a separate landing page, a permanent canonical link to the general section conflicts with that goal.
For the same collection with a different sort order, define the primary URL. Check that the products and meaning really are the same. Do not remove the material parameter just because it appears in the URL: the canonical recommendation would then merge different collections.
Yandex describes canonical as a recommendation, that the crawler may not accept. A correct tag does not guarantee that the search engine will make the desired choice. Therefore, the acceptance report should record the site’s rule separately from the verified index status, if recent data is available.
Consider pagination for the selected collection separately; the verification procedure is in the article about canonical on Bitrix pages. For other parameters, see the guide to URLs with filters and tags. The second page contains different products and must not lose its page number just because of a general parameter-cleanup function. An empty collection also needs its own behavior: a message for the user and an agreed search policy, not an accidental canonical to the general page.
How to check the page as an ordinary visitor
Open the source HTML and find the title, robots and canonical tags. Check that the main document contains the expected collection name and links to products. Then compare it with the page displayed in the browser. AJAX filtering is useful to visitors, but it does not replace checking the direct URL and initial response.
Check the same criteria without signing in and after reopening the page. If the result depends on a previous session, find the source of the state: saved filter parameters, component cache or custom code. Reusing a selection conveniently should not make one public URL show different, unpredictable collections.
Remove one selected criterion, add it back, apply sorting and go to the second page. After each action, compare the URL, criteria and products. Returning via a menu link is especially important: it should open the specified collection, not show another user’s last selection because of a misconfigured cache.
What to check after the assortment changes
Recheck the selected collection after adding and removing a test product. If an SKU no longer matches the material, it should disappear from the results; if a new one matches, it should appear. The heading and text should not promise a specific number of products if that number has changed. If the results are completely empty, apply the agreed empty-collection behavior. This check distinguishes a working filter from a static list saved once.
How to specify the task and accept the configuration
In the task, specify the selected collections, actual URLs, required criteria and list of test SKUs. For each page, include the canonical and robots rules, the source of the heading and the action to take when there are no results. If a Marketplace module is used, record its name and version along with the component versions.
Acceptance criteria for the teaching example: opening the aluminum URL directly shows only the required material; the excluded steel SKU is absent; sorting preserves the collection; the second page retains its page number; and the HTML tags comply with the agreed policy. Include the specific values and time of the check.
For additional checks of a published catalog, see the technical site audit; more practical analyses are in the blog. A completed task means having several reproducible pages with the right products and clear rules that can then be applied to the rest of the catalog. The number of URLs created and a message saying that SEO-friendly URLs have been enabled do not, by themselves, confirm the result.