The filter shows red sneakers, but the canonical points to the entire catalog. First decide whether the red-filter page needs its own URL in search. Then check that the canonical tag, links, and sitemap point to the URL you chose. Sorting and standalone collections need different rules.
Which filters should have their own page
Canonical tells Google which URL is preferred; the search engine may choose a different one. Official documentation.
Suppose a store sells shoes. The /shoes/ page shows the entire section, ?sort=price reorders the products, and /shoes/red/ filters for red styles. For sorting, it makes sense to look for the primary version of the same content. First assess whether the red filter works as a standalone result: does it have enough products, a stable URL, a description of the selection, and a matching search query? If people search for red styles separately and the collection is useful to shoppers, the store owner can leave it open to search. In that case, the developer sets the canonical to /shoes/red/. For sorting the same products, the canonical can point to /shoes/. Don’t apply the second rule to every filter: separate collections need their own decision.
Decisions for the category, sorting, and filter
| URL | What the shopper sees | How to use it in search | What URL the canonical points to |
|---|---|---|---|
| Category /shoes/ | All sneakers | Primary category | This URL itself |
| Sorting ?sort=price | The same products in a different order | Technical variant | Category canonical |
| Filter /shoes/red/ | Red styles only | Useful standalone collection | This URL itself |
| Filter with no products | An empty set | Decide separately | Don’t blindly copy the rule |
Where to check the canonical
In the browser console, find all link[rel="canonical"] tags, not just the first one. Record the URL in the href in the server’s original HTML, then select another color and compare the HTML after scripts run—the DOM. If the app changes the product list without full navigation, find out which URL loads when opened directly and when the page is refreshed. An unchanged canonical isn’t always an error: sorting may intentionally remain a variant of the category. If the red collection should appear in search separately, its canonical shouldn’t point to the entire catalog. If a canonical is set through a Link in the HTTP headers—the server response metadata—ask the developer to check that URL too.
Open the page you need and run this in the browser console:
[...document.querySelectorAll('link[rel="canonical"]')].map(el => ({
записано: el.getAttribute('href'), адрес: el.href
}));For a standalone red collection, you should see one line with the URL /shoes/red/. For sorting the same assortment, it should be the category URL. An empty array means there is no tag; two lines may appear if the theme and SEO plugin are both adding one. Use “View page source” to compare the original HTML with the result after scripts run. Canonical doesn’t redirect visitors.
What to do with the filter’s second page
Check pagination within the selected filter. /shoes/red/?page=2 shows a different part of the red assortment. Set the canonical to this second page, not the first: this is what Google recommends for pagination. Open both parts directly, compare the products and the next/previous links. Make sure page=2 doesn’t clear the color selection and that the canonical doesn’t point to the general catalog. For an assortment that changes, choose test products whose page placement is known. After testing, save the exact set and date, since changes in availability can move product cards between pages.
What to change in links and the sitemap
Check the three URL generators: the filter interface URL, the canonical in the template, and the sitemap entries. If different plugins handle them, changing one setting may leave two conflicting URLs. Add links to useful standalone collections in the catalog so shoppers and search engines can find them without manually entering the URL. There’s no need to multiply utility sorting URLs in the sitemap. When moving an old query URL to a clean path, first confirm that the state matches, then check the redirect. The check should include opening the old URL, the new URL, and selecting the filter through the interface.
Check four URLs after the change
Open the category, the sorted page, the red filter, and its second page directly. The right products and selected color should remain after a refresh. For a standalone filter, the canonical points to that page; sorting the same set of products can point to the category.
Also read: Canonical, sitemap, hreflang, and redirect conflicts and URL parameters and SEO: filters, UTM tags, and duplicates—how to avoid harming indexing. Site checks are available on the reChecker technical audit page.