Installs: 16 399

Dependents: 0

Suggesters: 0

Security: 0

Stars: 34

Watchers: 16

Forks: 3

Open Issues: 33


2.0.5 2023-02-15 11:13 UTC

This package is auto-updated.

Last update: 2023-03-02 22:01:39 UTC


A WordPress plugin that provides a blazing fast search engine and WP Query performance enhancements.

RediPress utilizes popular in-memory key-value database Redis as well as its RediSearch module, which provides a very performant full text search engine and secondary index on top of Redis.

The plugin hooks to various WordPress APIs, hooks and filters to create a replica of WordPress' posts database table in RediSearch and to keep it up-to-date. It also hooks into WP_Query and diverts all suitable queries into RediSearch instead of MySQL, which makes the queries a lot faster, in many cases almost instant.

RediPress also provides advanced searching features that are lacking from the original WordPress search, like weighted search terms and fuzzy search.

RediPress is also built with extensive amount of hooks and filters to customize its functionalities to suit the needs of the developer. In addition to just optimizing the queries, RediPress also brings some completely new features to the table with the ability to include non-WordPress-posts in the search results or adding and querying location data within the index.

Table of Contents


  • Redis + RediSearch module. At least version 2.2.1 of RediSearch is required. The plugin is tested up to version 2.6.8.
  • WordPress version 5.9.0 or later. The plugin could work with earlier versions as well, but it has not been tested.

Installation and initialization

  1. Install Redis with RediSearch and ensure it can be connected from the WordPress installation.
  2. Install and activate the RediPress plugin. For now the only available installation method is through Composer.
  3. Define the connection parameters either in the admin panel or as constants in your code (recommended).
  4. If you are planning to include custom posts or additional fields in the search index, it should be done now.
  5. Create the index schema to RediSearch. It can be done either in the admin panel or through WP-CLI with command wp redipress create posts.
  6. Run the actual indexing. It can as well be done either in the admin panel or through WP-CLI. Running the command wp redipress index posts is a recommended way to run the initial indexing. If the indexing stops you can continue indexing by running the command wp redipress index posts missing.

Indexing multisite installations

You can use the same commands with multisite: wp redipress create posts and wp redipress index posts. For multisite you have to specify site url with the --url parameter in order for RediPress to function properly. Example wp redipress index --url=subsite.domain.test.


The basic usage of RediPress goes through the WP_Query class. You can use the class and functions that depend on it (such as get_posts()) like you normally would, and RediPress hooks into the queries and runs them against the RediSearch database instead of the normal MySQL resulting in much lower latencies and query times.

Unlike some other similar query-speeding plugins, you don't need to add any parameters to the queries as RediPress knows what it is capable of doing and handles all queries automatically. If there is a query it can't handle, it automatically falls back to MySQL.

Extra parameters

There are some extra parameters that can be used alongside the regular parameters.


If you have defined geolocation fields for your index, you can query them easily with WP_Query. The query should be placed on the root level of the WP_Query arguments array, and look like this:

'geolocation'    => [
    'field'    => 'location',
    'compare'  => '<',
    'lat'      => 59.6,
    'lng'      => 16.5,
    'distance' => 100000,
  • field is the name of the field you have defined in the index.
  • compare is either < or > depending on whether you want to have results closer to or farther away from your reference point.
  • lat and lng are the coordinates of the reference point to which the distance is calculated.
  • distance is the distance in meters from the reference point to which the values are compared.

If you want to sort the WP_Query results by a distance to certain coordinates, you can do so by defining the WP_Query orderby parameter like this:

'orderby' => [
        'orderby' => 'location',
        'order'   => 'ASC',
        'compare' => [
            'lat' => 59.6,
            'lng' => 16.5,

This will sort the query results by the distance to the given coordinates.


If no ordering parameters are set with a search query or if orderby is set to relevance, RediPress uses RediSearch's default relevance calculations for ordering the results. By default it weighs post_title field with score 5.0, post_excerpt with 2.0 and other fields with 1.0. These can all by changed by filters.

There is also a possibility to give custom weights to certain values when doing the query.

Post types

Custom weights can be given to different post types either in the admin panel or in code. In code it is done by adding a custom weight parameter to the WP_Query parameters with post_type as a key and another array as its value containing the post types and their weights as key-value pairs.

new WP_Query([
    'post_type' => 'any',
    'orderby'   => 'relevance',
    'weight'    => [
        'post_type' => [
            'post'             => 1.5,
            'page'             => 3.0,
            'custom_post_type' => 7.0,

You can also weigh different post authors differently. So far there is no admin functionality for this and it must be done in code.

new WP_Query([
    'post_type' => 'any',
    'orderby'   => 'relevance',
    'weight'    => [
        'author' => [
            'admin'      => 1.5,
            'jane_doe'   => 2.0,
            'john_smith' => 5.0,
Taxonomy terms

It is also possible to weigh posts with certain taxonomy terms higher than others. In this case the first level inside the taxonomy parameter is the taxonomy name with another associative array as its value with terms and their weights as key-value pairs.

new WP_Query([
    'post_type' => 'any',
    'orderby'   => 'relevance',
    'weight'    => [
        'taxonomy' => [
            'category' => [
                'news'          => 3.0,
                'announcements' => 5.0,
            'post_tag' => [
                'some_tag'    => 4.25,
                'another_tag' => 6.0,
Meta values

Weights can also be defined for meta values. Obviously the meta keys should be added to the RediPress index and also set to be queryable. In this case the first level inside the meta is the meta key with another associative array as its value with values and their weights as key-value pairs.

new WP_Query([
    'post_type' => 'any',
    'orderby'   => 'relevance',
    'weight'    => [
        'meta' => [
            'meta_key1' => [
                'foo' => 2.0,
                'bar' => 3.0,
            'another_key' => [
                'fizz' => 1.25,
                'buzz' => 3.0,

Fuzzy matching

RediPress supports fuzzy matching of search terms with the s parameter. The setting for the Levenshtein distance can be either 1, 2 or 3. This can also be set in the admin panel.

new WP_Query([
    's'         => 'foobar',
    'post_type' => 'any',
    'fuzzy'     => 2,

Multisite search

RediPress supports searching from multiple sites with one query by using special blog query parameter. Set site IDs in an array to specify which sites should be targeted. You can use string 'all' to search all sites, or omit the value to search only current site (default).

new WP_Query([
    's'         => 'foobar',
    'post_type' => 'any',
    'blog'      => [ get_main_site_id(), 2, 3 ],

By default RediPress does not include the blog ID within the result objects, but you can add it by using redipress/return_fields filter.

    function ( $return_fields ) {
        $return_fields[] = 'blog_id';

        return $return_fields;

After that you can use the blog_id f. ex. in redipress/formatted_search_results filter.

    function ( $results, $raw_results ) {

        // Format the raw results into associative array.
        $formatted_raw_results = array_map( function ( $result ) {
            return \Geniem\RediPress\Utility::format( $result );
        }, $raw_results );

        foreach ( $results as $key => $result ) {
            $raw             = $formatted_raw_results[ $key ] ?? [];
            $result->blog_id = (int) $raw['blog_id'] ?? 0;

        return $results;


Query parts

To customize the RediSearch query, you can filter individual query parts with the following filters:

  • redipress/sortby
  • redipress/applies
  • redipress/filters
  • redipress/groupby
  • redipress/reduce_functions
  • redipress/load


RediPress is built to be as developer-friendly as possible. Nearly everything can be filtered and there are a lot of actions to work with.

Adding custom fields

To add custom fields into the RediPress index, two things must be done: register a new field into the table schema, and add a filter which provides the data for the field during the indexing and on post save.

Adding a new schema field works with the redipress/index/posts/schema_fields filter. (And similarly with the redipress/index/users/schema_fields filter) It filters an array of objects that extend Geniem\RediPress\Entity\SchemaField. For now the options are a numeric field, a text field a and tag field. The differences on these can be read from the official RediSearch documentation.

add_filter( 'redipress/index/posts/schema_fields', function( $fields ) {
    $fields[] = new \Geniem\RediPress\Entity\TextField([
        'name'     => 'my_field_name',
        'weight'   => 1.5,
        'sortable' => true,

    return $fields;
}, 10, 1 );

Notice The index needs to be re-created if new fields are created. This happens with the wp redipress drop posts command, which - unlike the 1.x versions - does not empty the index but rather drops only the schema which can then be re-created using the create command.

When the custom field is created and in the schema, the next is step to provide a function that populates the data for the field. This is done via the redipress/additional_field/{field_name} filter. The filter gets called every time the post is indexed, regardless of whether it is done on save post action, on a complete re-index or for example via WP-CLI command.

add_filter( 'redipress/additional_field/my_field_name', function( $data, $post_id, $post ) {
    return get_post_meta( $post_id, 'my_field_name', true );
}, 10, 1 );

Modifying the post object

RediPress stores the post object serialized in its index. It can be modified before saving which allows the developer to store additional data for the post to be used after it's retrieved from the database.

This happens with the redipress/post_object filter. In the example below, all ACF fields of the post are included in the object.

add_filter( 'redipress/post_object', function( $post ) {
    $post->fields = \get_fields( $post->ID );

    return $post;
}, 10, 1 );

Third party plugins

Advanced Custom Fields

There is a lot of functionality in ACF Codifier for working with RediPress. Without Codifier, ACF fields should be included in the index via filters.


RediPress supports Polylang out of the box. Other multi-language plugins may require some coding to work.


If you run into problems you can try dropping all indexes by running wp redipress drop posts. You can also delete all posts adding --delete-data flag for the command. After this re-index.


command: wp redipress delete

description: Delete posts from the index by the arguments. arguments:

  • document field: Any field from the document that should match the given value.
  • limit: If not defined the default value is 100.

example usage:

wp redipress delete --blog_id=1 --post_type=article --limit=500