Этот плагин не тестировался с последними 3 основными выпусками WordPress. Скорее всего, он уже не поддерживается и может быть несовместим с текущими версиями WordPress.



Redisearch implements a search engine on top of Redis. It has lots of advanced features, like exact phrase matching and numeric filtering for text queries, that are nearly not possible or inefficient with mysql search queries.


Актуальная версия плагина работает с RediSearch версии 2.0 (или выше),
что потребует использования Redis 6.0 (или выше). Если ваша версия ниже 2.0, то используйте плагин версии 0.2.7.

Here you find a list of RediSearch features included in the plugin:

Search: Instantly find the content you’re looking for. The first time.

Scoring fields differently: Give different score to different fields. For example higher score to product name and number than its description.

Fuzzy Search: Don’t worry about visitors misspelling.

Autosuggest: Adds a suggestion string to an auto-complete suggestion dictionary.

Synonyms: RediSearch supports synonyms, that is searching for synonyms words defined by the synonym data structure.

Existing features

  • WooCommerce: Index and search through most of existing products meta data.
  • Document: Index content of binary files such as pdf, word, excel and powerpoint.
  • Synonym: Adding synonym groups is simple. Just add each comma separated group on a new line in synonym settings and done.
  • Live search (aka autosuggest): Search as you type regardless of misspelling.


  1. First, you will need to properly install and configure Redis and RediSearch.
  2. Activate the plugin in WordPress.
  3. In the RediSearch settings page, input your Redis host and port and do the configuration.
  4. In RediSearch dashboard page, click on Index button.
  5. Let you visitors enjoy.

Optionaly, you can pass settings in your wp-config.php file like following. If you are using Redis Object Cache plugin, these settings may already exist.

define(‘WP_REDIS_HOST’, ‘’);
define(‘WP_REDIS_PORT’, ‘6379’);
define(‘WP_REDIS_PASSWORD’, ‘your-password’);
define(‘WP_REDIS_INDEX_NAME’, ‘indexName’);
define(‘WP_REDIS_SCHEME’, ‘connectionScheme’);

Часто задаваемые вопросы

What is wrong with WordPress native search?

Although mySql is a great database to storing relational data, It acts very poor on search queries and you must forget about some features like fuzzy matching and synonyms.

How Redisearch is compared to ElasticSearch?

Yes, ElasticSearch is a great search engine and it has very good performance compared to mySql. But RediSearch has almost 5 to 10 times better performance and also its way easier to create index, sync your data and send query requests.


I strongly believe Redisearch will one day dominate Elasticsearch. Very promising plugin. Kudos to developer @foadyousefi. Keep up the good work!
10.11.2018 1 ответ
it's a great thing to get this plugin work with my site!
Посмотреть все 3 отзыва

Участники и разработчики

«RediSearch» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:


«RediSearch» переведён на 1 язык. Благодарим переводчиков за их работу.

Перевести «RediSearch» на ваш язык.

Заинтересованы в разработке?

Посмотрите код, проверьте SVN репозиторий, или подпишитесь на журнал разработки по RSS.

Журнал изменений


  • FIXED: Fixed server connection issue caused by last release
  • Added: Option to select default language
  • Added: Added a filter to force RediSearch to replave WP_Query


  • Added: Ability to connect via UNIX sockets


  • FIXED: Fix issue while creating/updating/deleting posts


  • FIXED: Fix an issue with live search


  • Updated: Implemented RediSearch version 2.0


  • FIXED: Fix some bugs.


  • FIXED: Fix a bug preventing saving og feature settings.


  • Added: Get index name option from wp-config
  • Added: Option for disabling stop words
  • Added: Adding a comma separated and user defined list of stop words
  • Fixed: Make search fields parent elements position to ‘relative’ so auto suggestion will appear in correct place


  • Fix: Fix admin js and css files enqueue directory name case issue


  • Added: Added password option.
  • Added: Ability to set redis server configurations in wp-config.php file.


  • Added: Document feature for indexing binary file contents
  • Added: Filter hook ‘wp_redisearch_indexable_post_status’ to manipulate indexable post status
  • Added: Filter hook ‘wp_redisearch_before_admin_wp_query’ Applies to main query args. This is mainly for showing number of indexable posts
  • Added: Filter hook ‘wp_redisearch_after_admin_wp_query’ Applies after main query and recieves args and the $query object. This is mainly for showing number of indexable posts
  • Added: Filter hook ‘wp_redisearch_before_index_wp_query’ Applies to main query args. This hook is for manipulating arguments for indexing process
  • Added: Filter hook ‘wp_redisearch_after_index_wp_query’ Applies after main query and recieves args and the $query object. This hook is for manipulating $query object used for indexing posts


  • Added: WooCommerce support added as Feature
  • Fixed: Return option values if empty string stores in database
  • Fixed: Fix incorrect link to settings page
  • Fixed: Fix harcoded index name in WP-CLI INFO command
  • Added: filter hook ‘wp_redisearch_indexable_temrs’ to manipulate indexable terms list
  • Added: filter hook ‘wp_redisearch_indexable_post_types’ to manipulate indexable post types


  • Added: WP-CLI support
  • Added: Register and activating of Features
  • Added: filter hook ‘wp_redisearch_indexable_meta_keys’ to add extra meta keys to the index
  • Added: filter hook ‘wp_redisearch_indexable_meta_schema’ to manipulate type of post meta fields (default is text)
  • Added: action hook ‘wp_redisearch_after_post_indexed’ fires after posts indexed from the main index command
  • Added: action hook ‘wp_redisearch_after_post_published’ fires after a post have been published
  • Added: action hook ‘wp_redisearch_after_post_deleted’ fires after a post have been deleted
  • Added: action hook ‘wp_redisearch_after_index_created’ fires after main index created
  • Added: action hook ‘wp_redisearch_settings_indexing_fields’ fires after settings fields inside indexing options page
  • Fixed: Fix indexing posts on publish/update


  • Use default value for settings if not set in settings


  • Initial plugin