Integrate search facets with the Relevanssi search plugin. Relevanssi greatly improves the quality and relevancy of search results by maintaining its own search index in the database.


Because of the way Relevanssi plugs itself into WordPress core search, the Relevanssi add-on integration must be installed when you use FacetWP together with Relevanssi. Without the add-on, Search facets and the site-wide search results page will not work correctly.

How to select the Relevanssi search engine the Search facet settings.
How to select the Relevanssi search engine the Search facet settings.

When the Relevanssi add-on is activated, each Search facet will show a new “Relevanssi” option within its “Search engine” setting. This new “Relevanssi” engine must be selected, otherwise the facet will return no results. If you have reasons to want to use the “WP Default” engine instead, the only way to make this work is to disable Relevanssi on the page where the Search facet is placed.

If your site-wide search results page (the page with /?s=searchterm in the URL) has facets, the above is all you need to do. But if it does not have facets, the search result page will not show results. To fix this, you need to disable FacetWP on the search results page.

Turn off results snippets

Some users have reported issues with Relevanssi’s “Create custom search result snippets” feature.

If your results don’t show, try disabling that setting, as demonstrated below:

Disable Relevanssi's Create custom search result snippets setting.
Disable Relevanssi’s “Create custom search result snippets” setting.

Relevanssi limits

Be aware that using Relevanssi may require large amounts (hundreds of MBs) of database space (for a reasonable estimate, multiply the size of your wp_posts database table by three). If your hosting setup has a limited amount of space for database tables, using Relevanssi may cause problems. The following information is from the Relevanssi site:

“The upper limit of how big a site Relevanssi can support depends on your hardware. On shared hosting accounts with limited resources, tens of thousands of posts can be too much. If your hardware is solid, especially your database, there’s probably no upper boundary. The biggest site we’ve heard run Relevanssi without problems had two million posts, using a dedicated database server with SSD drives.”

Fix “no results” on the search results page

If you have the FacetWP Relevanssi integration add-on installed, and your search results page (the page with /?s=searchterm in the URL) does not have facets, the search will not work properly and show no results.

This is caused by FacetWP’s integration having to intercept the search query before it can know if facets are being used on the page. To fix this issue, you have to disable FacetWP for the search results page only, by adding the following code to your (child) theme’s functions.php:

add_filter( 'facetwp_is_main_query', function( $is_main_query, $query ) {
  if ( $query->is_search() && $query->is_main_query() ) {
    $is_main_query = false;
  return $is_main_query;
}, 5, 2 );

Using Relevanssi with WooCommerce

If you are using Relevanssi together with WooCommerce, some things will not work immediately.

This article in the Relevanssi documentation gives a good overview of common compatibility issues and their fixes.

Fix search results for WooCommerce product SKUs

If you are using Relevanssi with WooCommerce, with product variations enabled, you may run into issues when searching variation product SKUs with the Search facet.

Relevanssi can index product and product variation SKUs for WooCommerce products: just add _sku to the list of custom fields to index. But Relevanssi will index SKUs for the variations only, so the parent product will not be found when searching for the variation SKU.

The following code (source) uses the relevanssi_content_to_index filter hook to index the product variation SKUs for the main product, so you will be able to find the parent product when searching for the variation SKU.

Add this code to your (child) theme’s functions.php, rebuild the Relevanssi index and re-index FacetWP:

add_filter( 'relevanssi_content_to_index', 'rlv_index_variation_skus', 10, 2 );

function rlv_index_variation_skus( $content, $post ) {
  if ( 'product' === $post->post_type ) {
    $args       = array(
      'post_parent'    => $post->ID,
      'post_type'      => 'product_variation',
      'posts_per_page' => -1
    $variations = get_posts( $args );
    if ( ! empty( $variations ) ) {
      foreach ( $variations as $variation ) {
        $sku      = get_post_meta( $variation->ID, '_sku', true );
        $content .= " $sku";
  return $content;

How to disable Relevanssi on certain pages

If you need to disable Relevanssi on specific pages or templates, all you need to do is unhook two Relevanssi filters. To do so, add the following code to your (child) theme’s functions.php. If you want to apply this code only to specific pages or templates, use a Conditional Tag. In this example the code is only applied to a page with ID 4814.

With this code in place, it is also possible to use the “WP Default” Search engine setting in Search facets when you have Relevanssi installed, which normally does not work.

add_action( 'wp_head', function() {
  if ( is_page( 4814 ) ) { // Optionally limit this code to a specific page or template, with a Conditional Tag.
    // Disable Relevanssi entirely
    remove_filter( 'posts_request', 'relevanssi_prevent_default_request' );
    remove_filter( 'posts_pre_query', 'relevanssi_query', 99 );
} );



  • New added `facetwp_relevanssi_do_query` hook
  • Improved respect Relevanssi's "Throttle searches" setting for limiting results
  • Fixed use `post_types` query argument instead of `post_type` (for better Relevanssi compatibility)


  • Fixed WP's get_search_query() wasn't rendering correctly


  • Improved additional refactoring to support custom sorting (e.g. the FacetWP sort box)
  • Improved search facets now scan only posts within the current listing (performance tweak)


  • New complete rewrite for better performance and compatibility
  • New support for Relevanssi Free 4.10.2+ and Relevanssi Premium 2.12.2+
  • New highlighting and "Custom search results snippets" work now


  • Fixed support "order" and "orderby" URL variables


  • Fixed check against $query->get( 's' ) instead of $query->is_search (Event Calendar fix)


  • Important this add-on now requires FacetWP 3.6 and above!
  • Improved refactored code to support FacetWP 3.6+ query detection changes

See also