Choose filters from product data and buyer tasks
Start with attributes buyers use to reduce a genuine choice: size, material, compatibility, price range or delivery availability. Check that values are complete and consistently named across the catalogue. A filter that produces unreliable results damages trust even if the interface looks polished.
Keep navigation categories separate from combinations that are useful only after a shopper reaches a product group. Too many filters can make the interface difficult to scan and harder for the team to maintain.
One r/shopify poster says they currently use Magento 2 and are considering a move to Shopify; they want an Apple-only mobile-phone collection to appear as a separate Google landing page. That post illustrates one requirement; it does not establish platform behaviour or how common the need is. Check the store's actual URLs and canonical tags before deciding what to build.
Map the URL states before implementation
Document how a selected filter appears in the URL, whether selections can be shared, how users remove one condition and what happens when no results match. With query parameters, record each filter once and use a working rule ampersand separator. If filters are encoded in the URL path, use a consistent logical order. Match the examples below to the URLs the platform actually generates.
Google's faceted-navigation guidance explains that filter combinations can generate large numbers of URLs and affect crawling. Choose which states may be crawled or published based on their value to shoppers and the site's capacity; do not assume every possible combination deserves a search landing page.
| State | Example | Decision to record | Check before release |
|---|---|---|---|
| Base category | /collections/mobile-phones | Keep the useful, unfiltered category discoverable. If it is indexable, keep its canonical and sitemap URL consistent. | 200 response, useful products, intended canonical and internal links. |
| One filter | /collections/mobile-phones?brand=apple | Make it shareable if helpful. Consider publication only when this stable result serves a distinct shopper need and the platform supports a suitable page. | Stable URL, accurate result set, title/content and canonical treatment. |
| Combined filters | /collections/mobile-phones?brand=apple&memory=256gb | Keep the selection usable for shoppers; allow crawling or publication only when this specific combination has a plain purpose. | One value per parameter; avoid duplicate URLs for the same result. |
| Sort order | /collections/mobile-phones?sort=price-ascending | Treat ordering as a view of the same collection unless the store has a specific reason to create a separate page. | It does not create duplicate crawlable links or enter the sitemap as a separate landing page. |
| Pagination | /collections/mobile-phones?page=2 | Give each actual page of products its own stable URL and working route. | Page 2 has the expected products; nonexistent pages return the planned not-found response. |
| No results | /collections/mobile-phones?brand=not-stocked | Decide how an unavailable combination is shown to shoppers and crawlers. | For a crawlable URL with no matches, Google recommends a 404 response rather than a redirect to a generic error page. |
Make filter behaviour plain and reversible
Show active filters, result count and a plain way to remove one or all selections. Give each control a plain text label and group related options so people can identify what they are changing. Explain when a filter has no effect because its values are not available in the current category.
If filter changes update results without a full page load, make sure the URL and browser history behave in a predictable way. The visitor should be able to share or return to a useful selection where the business intends that behaviour.
Test crawl controls against the actual URL set
Generate representative URLs for a category, one filter, combined filters, sorting, pagination and an empty result. For each one, check the rendered links, HTTP response, canonical, robots directives, sitemap membership and whether the URL is created by internal links. When filters are encoded in the URL path, use a consistent logical order; with query parameters, use each parameter once and a working rule ampersand separator. Confirm the controls do not block a page the business intends search engines to discover or expose endless combinations.
Avoid broad robots rules copied from another store. Google documents different handling depending on whether faceted URLs need to appear in search, and notes the crawl cost of allowing large URL sets. Check the current platform behaviour before changing controls; robots, canonical and link rules do not serve identical purposes.
Use measured demand to decide which combinations deserve pages
If a filtered combination corresponds to a distinct, useful shopper need, consider whether it warrants a curated category page with stable content and navigation. Do not automatically turn every combination into an SEO landing page. Thin or near-duplicate pages can add maintenance without helping the buyer.
Record the business reason, chosen URL treatment and owner for each indexable filter landing page. Revisit the decision when the catalogue or product attributes change.