World is now on Opti ID! Learn more

Jonas Bergqvist
Mar 13, 2023
  51
(0 votes)

Making facets work as they should

"Faceted navigation" is a powerful way of enabling structured search functionality in our applications. Many search services forces you to make multiple queries to get content result and "correct" facets result. We have now fixed this in Content Graph, so you only have to make one simple query to get both item result and "correct" facet result.

Facet filters

Facet filters is a new functionality in Content Graph, which filter content items and the facet filters in the "correct way". The easiest way to explain how it works is by an example.

Below is a query for "location items" on "Foundation CMS" site, which has one facet for "continents", and one facet for "countries". Each of the facets have a parameter of type [String!], where values will filter the item result and other facets.

The result on our example application for Foundation CMS will look like this when not selecting any continents or countries:

Adding "Europe" and "Asia" for facet filtering of Continents will filter items to only get european and asian cities.

The countries will also be filtered to only show countries in europa and asia. The continents facet will still contain all values, to make it possible for user to see how many other continents that exist.

The example of selecting "Europe" and "Asia" looks like this in the example application:

We will finally add filtering for countries as will, which will filtering items based on combination of countries and continents.

The facets will now return the matching items based on values for the other facet.

The result looks like the following in the example application:

Mar 13, 2023

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |