Выделение поисковых запросов


Highlights search terms within WordPress generated search results, both on the search results page and on each linked post page itself.

This plugin is light weight and has no options. It started as very simple fusion between How to Highlight Search Terms with jQuery — theme hack by Thaya Kareeson and Search Hilite by Ryan Boren. It has since evolved with many optimizations, HTML5 and bbPress support.

Начиная с версии 1.6 он больше не зависит от библиотеки jQuery.


  • Выделение по щелчку: выделение не только на странице результатов поиска WP, но и на один клик глубже на любой из найденных страниц.
  • Character and case insensitive (lenient) highlighting
  • Совместимость с BuddyPress / bbPress: выделение при поиске по форуму
  • Совместимость с кэшированием (WP Super Cache)
  • Search terms wrapped in double quotes now considered as single term

Что оно делает?

This low impact plugin finds all search terms on a search results page inside each post and highlights them with a <mark class="hilite term-N"> ... </mark> tag.
Note that N is a number starting with 0 for the first term used in the search phrase increasing 1 for each additional term used. Any part of a search phrase wrapped in quotes is considered as a single term.

Что НЕ делает?

There are no CSS style rules set for highlighting. You are free to use any styling you wish but to make the highlights visible in browsers that do not support HTML5 like Internet Explorer 8 or older you absolutely need to define at least one rule.
Modern HTML5 browsers will use their own highlighting style by default, which usually is a yellow marker style background.

Итак, что мне нужно сделать?

В большинстве случаев он должен просто работать. Но вы можете сделать две вещи, чтобы обеспечить обратную совместимость с браузером и темой:

  1. Define CSS rules: There are no configuration options and there is no predefined highlight styling. You are completely free to define any CSS styling rules in your themes main stylesheet (style.css) or the Custom CSS tab if the WordPress theme customizer.
    You can find basic instructions and CSS examples in the FAQ’s.

  2. Check your theme: In most up to date themes (including WP’s own default theme) post and page content is shown inside a div with class hentry. This means search terms found in post and page content will be highlighted but not similar terms that accidentally show in the page header, sidebar or footer.
    If your current theme does not use the hentry class (yet), this plugin will look for IDs content, main and finally wrapper but if none of those are found, it will not work for you out of the box. See the last of the FAQ’s for ways to make it work.

Доступные хуки и фильтры

  1. hlst_query_vars — Массив переменных запроса WordPress, которые плагин идентифицирует как поисковый запрос. Должен возвращать массив. Дефолт: ['search_terms','bbp_search'] (WordPress и bbPress поиск)

  2. hlst_input_get_args — An array of GET variables that the plugin will identify as a search query. Must return an array. Default: ['hilite'] (for click-through highlighting)

  3. hlst_selectors — The array of possible HTML DOM element identifiers that the script will try. The first viable identifier it finds elements of will be scanned for search terms to mark, the rest is ignored. So the order is important here! Start with the element closest to, but still containing all the post/page title, excerpt or content.

  4. hlst_events — The array of DOM event listeners that the inline script will watch for. Default: ['DOMContentLoaded','post-load'] (on Document Ready and for Jetpack Infinite Scroll and others).

  5. hlst_inline_script — The inline script that will be added to the plugin script file. Can be used to add to or alter the inline script. Must return a string.

Известные проблемы & разработка

  1. If your theme does not wrap the main content section of your pages in a div with class «hentry» or HTML5 article tags, this plugin might not work well for you out of the box. However, you can make it work. See the last of the FAQ’s for an explanation.

  2. Josh pointed out a conflict with the ShareThis buttons plugin. Since then, that plugin has been completely rewriten so please let me know if the problem still exists. Thanks!

Пожалуйста, отправляйте отчеты об ошибках и вклады в код в виде запросов на вытягивание на GitHub.


  • Example of search term highlighting with the default MARK tag.

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

Инструкция по установке

To make it work, you will need to take up to three steps, depending on your wishes and WordPress theme. (I) A normal installation and activation procedure; (II) Make sure your theme uses any of the recognized classes or ID’s for the post content div so that the script knows where and where not to look for search terms;
and (III) optionally add CSS styling rules to get highlighting for older browsers that do not support HTML5 like Internet Explorer 8 and below.

I. Install now or use the slick search and install feature (Plugins > Add New and search for «highlight search terms») in your WP2.7+ admin section or follow these basic steps.

  1. Скачать архив и распаковать.
  2. Загрузите (и перезапишите) папку /highlight-search-terms/ и ее содержимое в папку /plugins/.
  3. Активируйте плагин на странице Плагины

II. In most up to date themes (including WP’s own Default theme) post and page content is shown inside an ARTICLE element or DIV with class hentry.
This is recognized by the hilite script, which means search terms found in post and page content will be highlighted but not similar terms that coincidentally reside in the page header, menu, sidebar or footer.

If your current theme does not use these common designations (yet), this plugin will look for some other possible tags like #content, MAIN, #wrapper (which might include the header, sidebar and footer areas) and finally the BODY.

If this causes issues on your theme, see the last of the FAQ’s for ways to make it work.

III. Optionally add at least one new rule to your themes stylesheet or the Custom CSS editor to style highlightable text.

For example use .hilite { background:#D3E18A; } to get a moss green background on search terms found in the content section (not header, sidebar or footer; assuming your Theme uses a div with class «hentry»).

Please find more examples in the FAQ’s below.

Я не вижу никакой подсветки!

This plugin has no configuration options page and there is no predefined highlight styling. For any highlighting to become visible in browsers that do not support HTML5 like Internet Explorer 8 or older, you have to complete step III of the installation process.
Edit your themes stylesheet (style.css) or the WordPress theme customizer Custom CSS tab to contain a rule that will give you exactly the styling that fits your theme.

If that’s not the issue, then you might be experiencing a bug or plugin/theme conflict. Time to get some Support 🙂

Я хочу настроить подсветку, но понятия не имею, что добавить в свою таблицу стилей. Можете ли вы привести несколько примеров?

Перейдите в раздел администратора WP на Внешний вид > Настроить > Пользовательский CSS и добавьте один из приведенных ниже примеров, чтобы начать работу.

For a moss green background highlighting:

.hilite {
    background-color: #D3E18A;

Подсветка желтым фоном:

.hilite {
    background-color: yellow;

Светло-голубой фон с жирным шрифтом:

.hilite {
    background-color: #9CD4FF;
    font-weight: bold;

Оранжевый фон с черным шрифтом:

.hilite {
    color: #000000;

Please give me more advanced CSS examples

If you want to give different terms used in a search phrase a different styling, use the class «term-N» where N is a number starting with 0, increasing 1 with each additional search term, to define your CSS rules.
The below example will make every instance of any term used in the query show up in bold text and a yellow background except for any instance of a second, third and fourth term which will have respectively a light green, light blue and orange background.

/* Default highlighting, but bold text. */
.hilite {
    background-color: yellow;
    font-weight: bold;
/* Moss green highlighting for second search term only. */
.term-1 {
    background-color: #D3E18A;
/* Light blue highlighting for third search term only. */
.term-2 {
    background-color: #9CD4FF;
/* Orange highlighting for fourth search term only. */
.term-3 {

Keep in mind that for the first search term the additional class «term-0» is used, not «term-1»!

Terms outside my post/page content get highlighted too

The script will search through your page source code for viable sections that usually contain page or post content, most commonly used in WordPress themes. Like ARTICLE or a DIV with class «hentry». If that is not available, the script will look for other commonly used divs like #content, #main, #wrapper. However, in your particular theme, none of these divs might be available…

Let’s suppose your theme’s index.php or single.php has no <div <?php post_class() ?> ... > but wraps the post/page content in a <div id="someid" class="someclass"> ... </div>. This will not be recognized by the script as a post/page content container and the script will default to highlighting starting with the BODY element.

Это приведет к выделению терминов в заголовке, меню, боковой панели и нижнем колонтитуле.

Вы можете сделать одну из трех вещей, чтобы решить эту проблему:

A. Change your theme templates like single.php, page.pho and search.php so the post/page content div has a class «hentry» (you can append it to existing classes with a space like class="someclass hentry").

B. Добавьте фильтр в файл functions.php вашей темы (или отдельный файл плагина) следующим образом:

    function( $selectors ) {
        // custom theme selectors (change and append as needed)
        $my_selectors = array(
        return $my_selectors + (array) $selectors;

C. Переключитесь на тему, которая соответствует текущим соглашениям WordPress 🙂


I added the «Prevent highlighting when clicking through to result» option, all works well! Thanks you
Nice! A plugin that works «out of the box.» Note: If after installing this plugin you experience any issues, most likely, they are due to a conflict with another plugin (usually a Cache or Performance plugin). The developers of these other plugins should be able to help solve your issues. Cheers 🙂
29.08.2023 1 ответ
Very good. It didn’t work right away. But overall very helpful. Although I immediately found a small mistake. For some reason, «by» does not work, but «by» = «by» — I checked! 1.cbm.ua/?p=5504
Посмотреть все 40 отзывов

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

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


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

Перевести «Выделение поисковых запросов» на ваш язык.

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

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

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


* Update to WP coding standards
* WP 6.5 compatibility tested


Date 2022-03-01

  • Fix T_TRY error


Date 2022-01-31

  • Fix possible missing is_plugin_active error


Date 2022-01-30

  • NEW: Woocommerce compatibility
  • NEW: Search Filter Pro compatibility


Дата 2021-12-04

  • Switch to mark.js, https://markjs.io/
  • Include HTML5 main tag
  • Dropped futile search engine support
  • FIX: Possible double inline script
  • FIX: wptexturized search results not highlighted
  • NEW: filter hlst_events


Дата 2021-08-18

  • FIX: NinjaFirewall incompatibility, thanks @danielrufde


Дата 2021-06-22

  • NEW: Vanilla Javascript, no more jQuery dependency!
  • NEW: Arabic character normalization map. Thanks @khakan
  • NEW: Jetpack Infinite Scroll support


Date 2021-06-20

  • NEW: filters hlst_query_vars, hlst_inline_script and hlst_input_get_args


Date 2021-06-10

  • FIX: broken comment pagination links, thanks @tooni


Дата 2021-01-13

  • ИСПРАВЛЕНИЕ: несовместимость jQuery 3


Дата 2020-04-07

  • ИСПРАВЛЕНИЕ: повторное рассмотрение уязвимости XSS


Дата 2020-04-02

  • Предотвратить выделение при поиске по клику из пунктов меню или виджетов


Дата 2019-12-20

  • Улучшение совместимости сторонних поисковых плагинов


Дата 2019-03-07

  • ИСПРАВЛЕНИЕ: результаты с учетом кириллического регистра, спасибо @dimmez
  • Сжатие скрипта


Дата 2018-03-10

  • Перейти к wp_add_inline_script


Дата 2017-12-22

  • Исправлена возможная уязвимость в append_search_query()
  • Подготовить текстовый домен перевода


Дата 2017-11-23

  • ИСПРАВЛЕНИЕ: Предотвращение bbp_is_search() для администратора, запускаемого Gravity Forms, о чем сообщает @dicoeenvoud.


Дата 2017-02-24

  • ИСПРАВЛЕНИЕ: уязвимость XSS, о которой сообщил Бен Биднер @ Automattic


Дата 2017-01-31
Время разработки: 3 часа

  • ИСПРАВЛЕНИЕ ОШИБКИ: оператор [] не поддерживается для строк в PHP 7, спасибо @seppsoft
  • Drop pre WP 3.7 support
  • Улучшенная поддержка bbPress


Дата 2016-10-04
Время разработки: 3 часа

  • BUGFIX: use filtered search terms for click through highlighting


Дата 20.07.2016
Время разработки: 2 часа

  • BUGFIX: incompatibility with Relevanssi and other search plugins


Date 2016-04-10
Dev time: 6h

  • Лучшие результаты поиска
  • Improved bbPress compatibility
  • Renamed Minified js

Date 2015-10-13
Dev time: 1h

  • FIX: Missing terms not wrapped in P tag (reported by zmokin)


Date 2014-09-04
Dev time: 5h

  • Совместимость с поиском WordPress 3.8, позволяющая менее нечеткий поиск с кавычками
  • ?sentence=1 query parameter compat
  • FIX: XSS vulnerability found by Rodolfo Godalle, Jr.


Date 2013-09-02
Dev time: 2h

  • BuddyPress and bbPress highlighting within forum searches
  • Исправлено: jQuery 1.10 совместимость


Date 2013-07-28
Dev time: 1h

  • FIX: Combine-JS compatibility (Thanks to Joshua Hoke)
  • More possible classes and ids to look for


Date 2012-12-16
Dev time: 1h

  • BUGFIX: non-western languages in URL not decoded


Date 2012-12-06
Dev time: 1h

  • BUGFIX: javascript infinite loop


Date 2012-10-11
Dev time: 6h

  • Search terms wrapped in double quotes now considered as single term
  • Caching compatible
  • Second click highlighting: not only on the search results page but also inside any of the found pages
  • Speed improvement
  • More search engines supported
  • BUGFIX: Undefined variable: cache_compat


Date 2012-07-27
Dev time: 1h

  • BUGFIX: non HTML5 browser (IE8 and older) support failing


Date 2012-07-25
Dev time: 8h

  • NEW: Caching (WP Super Cache) compatibility
  • NEW: Highlights not only on WP search results page but also one click deeper inside any of the found pages
  • NEW: Search terms wrapped in double quotes now considered as single term
  • support many more search engines: AOL, Dogpile, Search.com, Goodsearch.com, Mywebsearch.com, Webcrawler.com, Info.com
  • rebuilt as Class
  • plugin speed improvements


Date 2012-04-18
Dev time: 2h

  • HTML5 mark tag support
  • No more word boundary limit for non-latin based languages compatibility


Date: 2011-01-03
Dev time: 1h

  • BUGFIX: conflict with Cufon script


Date: 2010-09-06
Dev time: 2h

  • limit highlighted search terms to word boundary
  • added Bing, Ask, Baidu and Youdao search engines
  • now automatically check for and highlights in multiple theme div areas
  • BUGFIX: cloning first result excerpt to all excerpts


Date: 2010-08-07
Dev time: 2h

  • using jQuery in no-conflict mode and $hlst instead of $ to avoid conflict with prototype
  • split variables and moved js extension in compacted form to static file
  • moved jQuery and extention to footer + only when actually needed for faster page load


Date: 2010-04-07
Dev time: 1h

  • fixed Regular Expression to allow parts of words to be highlighted
  • search term wrapping limited to .hentry divs


Дата: 2009-04-16
Время разработки: 1 час

  • Bugfix for Firefox 2+ (forcefully highlights now limited to div#content)


Дата: 2009-04-15
Время разработки: 1 час

  • Разрешение нескольких стилей поискового запроса
  • Исправление для IE7 / IE8, спасибо Jason


Дата: 2009-04-14
Время разработки: 3 часа

  • Basic plugin aimed at low impact / low resource demand on your WP installation using client side javascript.