SleekPixel for FacetWP filtered archive pages
FacetWP turns archive pages into rich filterable interfaces. SleekPixel reads the active facet values from the request and renders a card showing exactly what is being filtered: city, price range, bedrooms, result count, sort order, all on a shareable PNG.
♾️ Lifetime License available
Every filtered URL has a unique story to share
FacetWP indexes posts into the wp_facetwp_index table and rebuilds the archive query based on the facets in the request. Two visitors looking at "properties in Lisbon under 600k" and "properties in Porto under 400k" are looking at the same archive template, but at very different content. The default OG image, however, is identical: the archive page's static OG image or the theme logo.
SleekPixel hooks into the FacetWP query lifecycle to read the active facets, their selected values, and the resulting count from the indexer. It then renders a card on the fly that shows the filter values as badges, the result count as a headline number, and the sort order as a footer label. The card is generated for unique facet combinations and cached so repeated shares of the same filtered URL serve a static PNG.
The card refreshes when the underlying index changes. Adding ten new listings under the same filters bumps the count on the card on the next regenerate. Changing the template, say to add a new accent color or a new badge style, refreshes every cached facet card from the admin.
Workflow
From facet selection to per-filter card
Hook into the FacetWP request
Pull result count from the index
wp_facetwp_index, SleekPixel reads the resulting post count and stores it alongside the active facet values.
Render and cache the card
Serve as the archive OG image
og:image tag points at the cached PNG for this exact filter combination. Repeat shares of the same URL serve the same static file.
Output
Sample FacetWP filtered archive card
Rendered from a real FacetWP query with active facets read from the request and the result count pulled from the FacetWP indexer.
Comparison
Static archive OG vs SleekPixel for FacetWP
Same archive image for every facet combo
- Every filtered URL shares the same generic archive OG image
- FacetWP active filters and result counts are invisible to social platforms
- Listing-archive shares feel identical regardless of what was filtered
- Sort order and pagination are not represented in the preview
- Marketing has no way to share a specific filtered view in a recognizable card
SleekPixel
- Reads active facets via the FacetWP request lifecycle on each archive load
-
Result count pulled from the
wp_facetwp_indexindexer - Selected facet values render as badges on the card
- Cached PNG per unique facet combination for fast share previews
- Bulk regenerate every cached facet card when the template changes
Features
What SleekPixel gives you for FacetWP
Active facet badges
Every selected facet renders as a badge on the card with its current value. City equals Lisbon, price under 600k, bedrooms two-plus, each shows as its own pill so the card mirrors the filter UI.
Result-count headline
The number of matching results from the FacetWP indexer renders as the main number on the card. The same archive with 38 matches and with 2 matches produce different cards.
Cached per combination
Unique facet combinations are cached as PNG files. Repeat visits to the same filtered URL serve a static image. Cache invalidates when the index changes or the template is edited.
Use cases
Where FacetWP archives benefit most from per-filter cards
Real estate archives
Property archives with city, price, and bedroom facets share a card that says exactly what is being filtered. Brokers can send a Lisbon-under-600k link with a matching preview.
Catalog archives
WooCommerce or custom catalog archives filtered by category and price ship cards showing the specific selection. "Shoes under 200 EUR" looks different from "Bags over 500 EUR" in feeds.
Event listings
Event archives filtered by month, city, or topic produce cards reflecting the filter. "Workshops in Berlin in May" looks like its own page in shares, not the generic events index.
The bigger picture
Filtered archives are content too, not just navigation
FacetWP exists because users want to slice a catalog. Properties under 600k in Lisbon. Workshops in Berlin in May.
Shoes under 200 EUR in size 42. Those slices are the most-shared URLs on filterable sites, because they are how somebody describes what they are looking at. The same site usually has one OG image for the entire archive, designed as a fallback.
Every filtered share looks identical to every other filtered share. SleekPixel changes that by reading the actual facet state when the archive renders and producing a card that mirrors it. The filter badges on the card match the filter badges in the UI.
The result count on the card matches the result count in the listing. The sort order on the card matches the sort order in the URL. When somebody shares the Lisbon-under-600k URL, the link preview says "Properties in Lisbon under 600k EUR, 38 matching listings." That is the language they would use to describe what they sent.
Filtered archives stop being silent and start being self-describing, without any manual screenshotting for each filter.
Questions
Common questions about SleekPixel for FacetWP
Yes. SleekPixel hooks into the FacetWP request lifecycle and reads the active facet names and their selected values before the archive index is queried. Those values are then used as variables in the template.
FacetWP rebuilds the archive query against its own wp_facetwp_index table. After the query runs, SleekPixel reads the resulting post count and exposes it as a template variable that typically renders as the headline number on the card.
Yes. SleekPixel hashes the active facet combination and stores a cached PNG per unique combination. Repeat visits to the same filtered URL serve the static file. The cache invalidates when the FacetWP index rebuilds or the template is edited.
Pagination is treated as part of the facet state, so page two of a filtered archive can render a slightly different footer label such as "Page 2 of 4." In most setups, however, the card stays consistent across pages to avoid fragmenting the cache.
Yes. The sort facet value renders as the footer label on the card by default, and the pager facet's current page is available as a variable. Both can be hidden in the template if you only want filter values represented.
Cached cards for that archive are invalidated and regenerated on the next request. This ensures that adding or removing posts that affect a filter combination updates the card's result count without manual intervention.
Yes. The SleekPixel admin offers a regenerate action that walks every cached facet combination for a chosen archive and refreshes its card. A WP-CLI command does the same for headless deploys.
Yes. SleekPixel runs at the request level, not in the template, so it works regardless of whether the archive layout is built with FacetWP Listing Builder, classic PHP archive templates, or block-based theme templates.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout