WooCommerce Filter Redirects to Shop Page From Category Page: Fix
You filter on a product category page and the result looks like the WooCommerce shop: the heading says Shop, the category description and breadcrumbs are gone, the theme's category header disappears and the browser tab shows the shop's SEO title. It feels as if the WooCommerce filter redirects to the shop page from the category page, but look at the address bar: in most cases it still shows the category URL. The page has not moved; WordPress has stopped treating it as a category. Below is why HUSKY does this by default, the two settings that keep the category page intact, and what to do about breadcrumbs, descriptions, theme templates and real redirects.
Why a filtered category page turns into the shop
When a filter is applied, the URL gets the search parameter (swoof=1 by default) plus the selected values, for example /product-category/shoes/?swoof=1&pa_color=red&really_curr_tax=15-product_cat. By default the plugin then converts the main WordPress query into a product archive: it sets the query's post type to products, marks it as a post type archive and switches off its taxonomy flags. This guarantees that the filter searches products wherever the form sits. The side effect is that, for this request, the page is no longer a category archive for anyone who asks:
| What you see | What decides it | Result after filtering |
|---|---|---|
| Page heading | WooCommerce prints the term name only on a taxonomy archive | The title of the Shop page |
| Text above the products | Category description on taxonomy archives, Shop page content on the product archive | The Shop page content instead of the category description |
| Breadcrumbs | WooCommerce checks "is this a product category?" before "is this the shop?" | Home / Shop |
| SEO title and meta description | Yoast SEO, Rank Math and others read the current archive | The shop's |
| Theme blocks, header images, Elementor or Divi archive templates, Widget Logic conditions | Conditions such as is_product_category() and is_tax() | Category-only elements disappear; the template for the shop may be used |
The products themselves stay right: the category still comes from the URL, and the really_curr_tax parameter tells the filter which category the visitor started from. Only what surrounds the products comes from the wrong place. The same happens on tag, brand and custom taxonomy archives. In AJAX mode you may notice it only after a reload or when you open a shared filtered link, because an AJAX update replaces the products, not the heading.
The fix: Disable swoof influence
- Go to WooCommerce → Settings → Products Filter → Advanced → Options.
- Set Disable swoof influence to Yes and save.
- Purge the page cache and test in a private window: filter on a category, then reload the page.
With Yes the plugin leaves the page type alone. A filtered category page stays a category archive, so WooCommerce, the theme, the page builder and the SEO plugin show the category's own title, description, template and meta data. Filtering keeps working, because the selected values are applied to the product query itself, not through the page type. You do not need the SEO URL request extension for this.
The setting is global. After switching it on, test filtering on the shop page, a category, a tag or brand archive, the product search results and any page that uses [woof_products]. Pages built with [woof_products] are not affected, because the plugin never turns a WordPress page into the product archive. If a theme stops showing products or breaks its layout on filtered archives with Yes, that theme relies on the shop template during a search: set the option back to No and use the targeted fixes further down.
If the filter forgets the category: Additional check of the category page
On a category archive the filter remembers the category the visitor is in. It uses it to list only the subcategories in the category block, to count only the products of that category and to add really_curr_tax to filter links. When the plugin fails to detect it, you see this after the first filtering: the category block jumps back to the top-level categories of the whole shop, the counts no longer match the category, and a choice in that block leads out of it. That is the other half of "it goes to the shop page".
Set Additional check of the category page (Advanced → Options, right below Disable swoof influence) to Yes. The plugin then reads the current category from WordPress at the moment it builds the filter, instead of relying on the value it saved earlier. Block themes get this check automatically; classic themes and builders that assemble archives in their own way, Avada for example, may need it switched on together with Disable swoof influence. What the category block shows on each kind of page is explained in why the category filter shows only subcategories.
Breadcrumbs still hidden: the plugin's own CSS
While a filter is active, the plugin adds the class woof_search_is_going to the <body> tag, and its stylesheet hides the WooCommerce breadcrumb (nav.woocommerce-breadcrumb) and a h1.page-title placed directly after it. With the default setting that breadcrumb would read Home / Shop on a category page, so hiding it was the lesser evil. With Disable swoof influence = Yes the breadcrumb is correct, and you can show it again:
/*
* HUSKY: keep the WooCommerce breadcrumb (and a title right after it)
* visible on filtered pages.
* Products Filter → Advanced → Code → Custom CSS code, or Appearance → Customize → Additional CSS.
*/
body.woof_search_is_going nav.woocommerce-breadcrumb,
body.woof_search_is_going nav.woocommerce-breadcrumb + h1.page-title {
display: block;
}
If your theme lays out the breadcrumb with flexbox, use display: flex; instead of block. Breadcrumbs printed by Yoast SEO, Rank Math or the theme's own function are not hidden by the plugin; they simply follow the page type, so they show the category once the setting is Yes.
If you have to keep the default setting
When your theme needs Disable swoof influence = No, restore the missing parts one by one:
- Category description. The FAQ category description not showing on a filtered page has a ready snippet that reads the category from
really_curr_taxand prints its description above the products. - Breadcrumbs. The CSS above shows them, but they will read Home / Shop.
- Conditions in widgets, theme hooks and custom code.
is_product_category()returnsfalseduring filtering. Use a helper that also reads the category from the filter link:
/**
* True on a product category archive, also while HUSKY filters it
* with "Disable swoof influence" = No.
* Usage: my_is_product_cat() or my_is_product_cat( 'shoes' ), e.g. in Widget Logic.
* Child theme functions.php or a code snippets plugin.
*/
function my_is_product_cat( $slug = '' ) {
if ( is_product_category( $slug ) ) {
return true;
}
if ( empty( $_GET['really_curr_tax'] ) ) {
return false;
}
// Format: "15-product_cat" (term ID, dash, taxonomy)
$parts = explode( '-', sanitize_text_field( wp_unslash( $_GET['really_curr_tax'] ) ), 2 );
if ( count( $parts ) !== 2 || 'product_cat' !== $parts[1] ) {
return false;
}
$term = get_term( (int) $parts[0], 'product_cat' );
if ( ! $term instanceof WP_Term ) {
return false;
}
return '' === $slug || $term->slug === $slug;
}
To check only whether a filter is active, the plugin has a global function, is_woof_search_going(). Header images and other theme elements that exist only on real archives come back only with Yes.
When the URL really changes to the shop page
If the address bar shows the shop URL after filtering, this is a real redirect, and it has a different cause. On a page that is not a product archive, for example a WordPress page designed as a category landing page, the filter looks for a product list it can refresh. When it finds none, it sends the visitor to the shop. Three ways out:
- Use the real category archive (
/product-category/...) and design it with your theme's or builder's archive template, then apply the settings above. - Keep the page and show its products with
[woof_products]limited to the category, as described in the product filter on a custom page. - If a builder grid on the page already reacts to the filter but uses its own markup, tell the script to stay on the page with
woof_not_redirect; the snippet is in the filter URL changes but the products do not.
One more case is not a redirect at all. Choosing a category in the filter on the shop page narrows the shop; it does not open that category's archive. The URL stays the shop URL, and archive-only elements such as a category header image do not appear. If visitors should land on the category itself, give them category links in a menu or a navigation block and keep the filter for narrowing.
Checklist
- After filtering, the address bar still shows
/product-category/...: it is the page type, not a redirect. - Disable swoof influence = Yes, page cache purged, tested in a private window and after a reload.
- The category block or the counts jump to the whole shop: Additional check of the category page = Yes.
- Breadcrumbs: the CSS above added.
- Shop page, tag or brand archives, search results and
[woof_products]pages still filter correctly.
If the category page still loses its title or template after these steps, open a topic on the HUSKY support forum with the category link, the filtered link and the name of your theme or page builder, and we will look at it.