WP Grid Builder

Quick take

WP Grid Builder combines faceted filtering with a responsive grid, card, and carousel presentation system. It can query posts, terms, and users, then filter them through indexed facets while giving site builders a drag-and-drop card designer for the results themselves. Facets can also be used independently with third-party content when the built-in grid is not required.

Best fit: WordPress sites that need both faceted search and a dedicated visual system for displaying filtered cards, grids, product lists, portfolios, or directory content.

Facets and query model

WP Grid Builder facets can filter taxonomies, post fields, and custom fields. The plugin includes more than 20 facet types covering checkboxes, radios, selects, sliders, ratings, pagination, sorting, reset controls, load-more actions, and other interactions. Each facet is attached to one grid, template, or supported third-party query.

An index table stores filter values to speed up filtering. Facets are refreshed when content changes and can also be manually re-indexed. This is useful on larger data sets where raw metadata queries would otherwise make every interaction expensive.

Grid and card presentation

The visual layer is a major difference from filter-only plugins. WP Grid Builder includes a card builder plus Masonry, Justified, and Metro grid layouts, carousels, responsive column controls, lazy loading, reveal animations, media lightboxes, and prebuilt cards. Custom fields can be displayed inside cards, and WooCommerce or Easy Digital Downloads data can be included in ecommerce layouts.

This reduces the need to pair a separate loop builder with a filtering plugin. It can also create more lock-in if the site’s presentation becomes deeply tied to WP Grid Builder cards, so long-term template ownership should be considered before a full redesign.

Integrations and custom data

The vendor lists integrations with WooCommerce, Easy Digital Downloads, SearchWP, Relevanssi, ACF, Meta Box, Pods, WPML, Polylang, Elementor, Beaver Builder, Oxygen, LearnDash, Bricks, and other common tools. Facets can be displayed with blocks, shortcodes, widgets, or dedicated builder integrations.

Developers can use facets without the plugin’s grids and extend behavior through actions, filters, and functions. That makes the product more flexible than a purely visual grid builder despite its strong design layer.

Pricing and licensing

The Basic plan is currently $49 per year for one site. Premium costs $99 per year for three sites, and Ultimate is $249 per year for unlimited sites. All current plans include official add-ons, one year of updates, and one year of support. The vendor offers a 14-day money-back guarantee.

Because all add-ons are included, the main licensing decision is site count rather than feature tier. Agencies should compare the unlimited license with FacetWP’s larger-site plans and other filter products before standardizing across client builds.

Migration and maintenance

A move to WP Grid Builder can involve two migrations: filters and presentation. Map every old filter field and URL, but also decide whether the current cards, archive templates, and query loops should remain or be rebuilt in WP Grid Builder. Replacing both layers at once increases regression risk.

On staging, re-index facets, compare result counts, test card output on multiple devices, validate WooCommerce stock and price filters, and confirm that history states, pagination, caching, and multilingual content behave correctly.

Where WP Grid Builder may not fit

If the site already has a carefully built result layout and only needs faceting, FacetWP or Search & Filter Pro may introduce less presentation overhead. JetSmartFilters can be more natural inside Crocoblock, while Filter Everything is stronger when SEO-managed filtered URLs are a central requirement.

Separate the filtering decision from the design decision

WP Grid Builder can replace both the result layout and the filtering layer, but those are two separate architectural choices. A project may keep its existing archive or builder loop and use only facets, or it may move presentation into the card and grid builder. Deciding this early makes migration easier to scope and roll back.

When the visual layer is rebuilt, compare card markup, schema, internal links, image loading, and responsive behavior with the previous templates. When only facets are adopted, test the integration against the existing query after every major builder or theme update because the result loop remains owned by another system.

WP Grid Builder 2.3.6 security and deployment notes

WP Grid Builder 2.3.6 is the current release as of September 21, 2026. The 2.3.x line is especially important because version 2.3.4 fixed multiple security issues in filtering and metadata handling, while later releases added WordPress 7.1 compatibility and hardened the async filter endpoint. Sites running older builds should treat the update as more than a cosmetic maintenance release.

WP Grid Builder combines two responsibilities: rendering grids/cards and providing faceted filtering. That is convenient, but it also means migrations need to account for card templates, grid queries, responsive layouts, facet indexes, URL behavior, and third-party integrations together. A replacement filter plugin can reproduce facets while still leaving the site without an equivalent card/grid rendering system.

After imports or bulk content changes, verify that facet indexing has completed and that translated terms, numeric taxonomy slugs, ranges, and pagination return the correct results. For WooCommerce or multilingual sites, test empty-result states, archive pagination, and any custom-field data sources after updates. Keep staging copies of exported settings before major template or index changes.

WP Grid Builder FAQs