An SEO filter page should solve a specific shopping task: show suitable products at a clear URL and retain that selection when opened directly. Before creating pages in bulk, choose three selections and prepare a specification for each. Record the reason for choosing it, selection rules, reference products, URL and acceptance criteria.
This guide is for owners of a catalogue built on 1C-Bitrix: Site Management who are coordinating an SEO specialist and a developer. The standard Smart Filter component includes URL, caching and session persistence settings. Having these settings does not determine which selections your customers and search visitors need.
Choose a task that needs its own page
Start with known customer questions, internal site searches and available search query data. Record the exact task and where you observed it. For example, someone may need a cabinet of a particular height because space is limited. That gives you a selection rule and a reason for the page.
If you have no demand data, mark the page as a research hypothesis. Do not assign invented impressions or sales to it. A list of combinations that a module can generate is not evidence of demand. Even an observed query needs checking: does your range match it, and does a separate selection actually help the customer choose?
Compare the proposed page with an existing category. If its task, product set and conditions are identical, first decide which URL should be primary. Improving the existing category may be enough. If the task differs, describe that difference in terms a sales representative can explain without SEO terminology.
Make the selection rule unambiguous
Our training example is “Metal cabinets 1800 mm high”. The rule is a metal body and a height of 1800 mm. A cabinet 1800 mm wide does not qualify. The number 1800 in a product name is no substitute for a populated height attribute.
Specify units, allowed values and how missing attributes are handled. If some products store height in centimetres, first standardise the data. Otherwise, the filter may appear to work while returning an incomplete set.
For products with variants, decide whether you are selecting a particular configuration or a model family. If a family has a matching variant, the customer should see and select it without searching again. Check that the price and availability belong to that variant.
| Training item | Expected result | Reason |
|---|---|---|
| Metal, height 1800 mm | Included | Both conditions met |
| Metal, width 1800 mm | Excluded | Height not confirmed |
| Wood, height 1800 mm | Excluded | Different material |
| Height missing | Data review | Eligibility cannot be confirmed |
In your real specification, replace these descriptions with catalogue item codes. Keep one matching and one non-matching example for every condition. These items will help you verify the implementation after updates, even when the page looks almost unchanged.
Separate the shopping filter from search landing pages
A visitor may combine many attributes to narrow their choices. For search, agree a limited list of standalone pages. Maintain the two lists separately so that adding an interface attribute does not automatically make every combination indexable.
Google’s faceted navigation guidance explains how numerous URL combinations can consume crawling resources. For crawlable filters, it recommends a consistent ordering of conditions and no duplicate filters; empty or invalid combinations and nonexistent pagination should return 404 at their original URL.
These recommendations apply to the scenario Google describes. Existing store URLs, especially those already receiving visits, need an individual decision before changes. Do not block the entire catalogue with a broad pattern just to reduce URL counts. First list the affected URLs and test the rule against useful exceptions.
Agree indexing behaviour for each URL type
For each chosen landing page, record its preferred URL, crawl permission, absence of an indexing prohibition and discovery through internal links. Define separate behaviour for sorting that same selection, technical parameters and incidental combinations. There is no universal “correct SEO” switch.
A canonical identifies a preferred URL for identical or very similar content, but does not require Google to select it. It is not a way to explain why completely different selections should count as one page. Check the content and consistency of signals against Google’s documentation.
Noindex and robots.txt serve different purposes. If you block Googlebot from crawling a page, it cannot read a noindex directive inside it, as explained in the indexing exclusion documentation. Plan the removal of already discovered unwanted pages separately from limiting the crawling of new combinations.
Record both the setting and its expected result. For example: “The selection opens directly, its preferred URL matches internal links, and the sitemap contains no technical variants.” Ask the developer to show the actual page response, because module settings may conflict with a template or another extension.
Test without an existing session
Copy the proposed URL and open it in a new private window after closing all previous private windows, or use a separate clean browser profile. The correct conditions and products should appear immediately. If the selection only works after visiting a category, it depends on saved session state and needs fixing.
- Compare the heading and active conditions with the page specification.
- Find the matching reference product and confirm that the non-matching one is excluded.
- Open the product page and check its variant, price and attributes.
- Change sorting: the qualifying products must still match the same conditions.
- Open the next results page, if one exists; save its URL and open it separately.
- Clear the filter and check that you return to the expected category.
Ask the developer to compare the original server response with the content after JavaScript runs. If headings and products only appear after browser activity, account for that when checking discovery and rendering. Visually similar states do not prove equal content accessibility.
Test caching and changes to the range
Open two different selections in sequence, then repeat in reverse order. Products and headings must not be replaced by the previous request’s result. Test a URL with a tracking parameter: the parameter must not change product selection.
On a test copy, change a reference product’s attribute and run the agreed data refresh. Check that the item leaves one selection and enters another where the rules require it. Then restore the training changes. Do not use live stock quantities or prices as test switches without the catalogue owner’s agreement.
Review zero results separately. An impossible combination, temporary lack of stock and a permanently discontinued product group are different cases. Agree the server response, customer message and future of the URL for each. Do not promise a wide choice above an empty list.
What useful selection pages should say
Explain what the chosen constraint means and what else the customer should check before ordering. For a cabinet of a specific height, this might include external dimensions, access through doorways, included components and assembly. Add only information supported by the range and your team.
The heading must match the actual selection. The description helps people compare options, while links lead to suitable models and purchase terms. Do not multiply identical paragraphs by replacing a single attribute. If there is nothing useful to explain and the page repeats a category, reconsider whether it needs its own URL.
A sample acceptance record
Page: metal cabinets 1800 mm high. Fault: a cabinet 1800 mm wide but of another height appears in the results. Evidence: item code and attribute values saved. Task: filter on the height attribute, checking units and variants. Acceptance: the matching reference item is present and two non-matching items are absent; direct access, sorting and catalogue refresh preserve the correct selection.
After the fix, repeat the test on a neighbouring selection that uses the same mechanism. Save configuration versions and actual results in the report. “Module installed” confirms an installation; completion requires testing the promised pages.
When a module or bulk page creation is unnecessary
If the range is small and existing categories already solve customer tasks, another landing-page layer may make maintenance harder. If attributes are incomplete, fix the data first. If demand is only assumed, begin with research and a few manually agreed selections.
A working filter does not necessarily need a new module for one heading or URL. Establish what the current implementation cannot do and the cost of a focused change. Use identical acceptance examples for both options so that price comparisons are meaningful.
After publication, check page access and product selection, then monitor indexing, search entry visits and enquiries separately. Inclusion in a sitemap does not prove inclusion in search; inclusion in search does not guarantee sales. For a broader catalogue check, see the store SEO guide.
Glossary
- Faceted navigation: selecting products through combinations of attributes.
- Landing page: a standalone page for a particular customer task.
- Search-engine-friendly URL: a page address that people can understand.
- Pagination: splitting a list into pages with separate URLs.
- Selection specification: a record of a selection’s task, rules and test examples.
If behaviour remains unclear, you can submit three selection specifications for a technical review. This makes it possible to estimate a focused change before buying a catalogue extension.
Apply this to your own project
Prepare three selection specifications and accept the product rules, URLs and page behaviour before expanding the catalogue in bulk.
SEO filter page specification and acceptance: open the worksheet · Download the CSV to complete. Free access, no registration. Use it independently or pass it to your contractor.