JetSmartFilters

Quick take

JetSmartFilters is Crocoblock’s advanced filtering plugin for WordPress sites built with Elementor, Gutenberg, Bricks, Divi, WooCommerce, and related JetPlugins. It provides visual filter widgets for custom post types, products, taxonomies, custom fields, ratings, ranges, dates, search, sorting, pagination, and active selections.

Best fit: Crocoblock, Elementor, Gutenberg, Bricks, and WooCommerce projects that want visual AJAX filtering integrated with the same builder ecosystem used to create listings and templates.

Filter types and data sources

JetSmartFilters includes a broad set of filter controls such as checkboxes, radio buttons, selects, search, date ranges, numeric ranges, ratings, visual swatches, alphabetical filters, sorting, pagination, and active-filter displays. Filters can target WooCommerce products or other post types and can use taxonomy terms, custom fields, product attributes, ratings, and query data.

The product is especially useful when the result layout is already built with JetEngine or a supported builder. In that context, the filter widgets and listing queries share the same ecosystem, reducing the amount of custom glue code needed between content modeling and front-end discovery.

AJAX filtering and query behavior

Filters can update results dynamically without full reloads. Crocoblock also provides options for hierarchical filtering, search within results, sorting, and pagination. The exact behavior depends on the provider and query being filtered, so complex pages should be tested with the actual loop rather than only with a demo grid.

For WooCommerce, current documentation covers prices, ratings, categories, attributes, variations, sale status, and other product criteria. This makes JetSmartFilters relevant to stores as well as directory or catalog projects.

Builder and ecosystem integration

JetSmartFilters is positioned for Elementor, Gutenberg, Bricks, and Divi, with extensive documentation around JetEngine and JetWooBuilder. That ecosystem integration is its main strategic advantage: a site using Crocoblock for dynamic content can build fields, listings, queries, and filters with products designed to work together.

The same dependency can also be a limitation. A site that is not using Crocoblock or a supported builder may gain less from the product than it would from a more builder-neutral solution such as FacetWP or Filter Everything.

Pricing and licensing

JetSmartFilters is currently listed at $75 per year for one site. Crocoblock also sells unlimited-site licensing and broader All-Inclusive plans that bundle JetSmartFilters with the rest of the JetPlugins suite. The All-Inclusive Plus plan is currently $249 per year for one site, while a lifetime bundle is available at a higher one-time price.

The right license depends on how much of the Crocoblock stack a project actually uses. Buying an all-plugin bundle only for filtering may not be economical, while teams already using JetEngine, JetWooBuilder, and related plugins may benefit from unified licensing.

SEO and filtered URLs

AJAX filtering improves interaction speed, but SEO strategy still needs deliberate configuration. Decide which filtered states should be crawlable, how canonical URLs behave, and whether parameter combinations should be indexed. Do not assume every useful visitor filter should become a search landing page.

When replacing another filter plugin, compare the old URL pattern with JetSmartFilters’ generated states and preserve important indexed landing pages through redirects or equivalent server-rendered archives.

Migration and testing

Document every filter’s data source, provider, query ID, field key, range, sorting rule, and default value before rebuilding. Test empty states, product variations, mobile drawers, multilingual labels, and pages containing more than one loop. If the site relies on custom query logic, validate every integration after plugin updates.

Where JetSmartFilters may not fit

A developer building highly custom queries may prefer FacetWP’s hook-oriented approach. Search & Filter Pro can feel simpler for form-centric projects, Filter Everything offers stronger SEO controls for filter landing pages, and WP Grid Builder may be better when the project also needs a dedicated card and grid builder.

Query-provider discipline matters

JetSmartFilters can work across several builders and Crocoblock providers, but each filter still needs to target the correct query. On pages with multiple listing grids, archive loops, or WooCommerce sections, document provider IDs and query relationships before launch so one filter does not update the wrong result set.

Teams should also test plugin updates on staging when JetEngine, JetWooBuilder, or a builder controls the same query. The strongest JetSmartFilters implementations usually have a clear ownership model for the data query, the result template, and the filter interface rather than letting several plugins modify the same loop independently.

JetSmartFilters 3.8.5 and current filter architecture

JetSmartFilters 3.8.5 is the latest documented 2026 release line from Crocoblock. The 3.8 generation expands Listing Builder support for JetEngine queries, adds dynamic range recalculation, filter duplication, clickable listing items, improved URL handling, and tighter support for Elementor, Gutenberg, Bricks, WooCommerce archives, user queries, and JetEngine data sources.

Security and query handling also changed materially during 2026. Crocoblock patched SQL-handling issues in the 3.8 series and continued hardening indexed filtering. That makes version hygiene important on sites exposing complex filters publicly. After updates, re-test indexed counts, range filters, pagination, WPML translations, WooCommerce attributes, and any filters connected to custom queries or Custom Content Types.

For migrations, document the provider connected to each filter, the query ID, apply type, AJAX behavior, URL format, default values, hierarchy, and whether JetEngine indexing or custom storage is involved. A visually identical filter can return different results if it is connected to a different provider or query context. JetSmartFilters is especially strong inside the broader Crocoblock stack, but that also means migrations away from JetEngine or Elementor/Bricks should be planned as architecture changes rather than simple widget swaps.

JetSmartFilters FAQs