WordPress search doesn’t search everything, and doesn’t give you enough control over what is searched and how. Relevanssi gives you full access and full control, with plenty of filters and ways to make Relevanssi work the way you want your search to work.
Multisite searches Relevanssi can run searches across many subsites in the same multisite network.
Custom fields Relevanssi will find the content in your custom fields, including things like WooCommerce SKUs, ACF field content or whatever it is you store in custom fields. Read more about custom field search.
User profiles Yes, Relevanssi will find users by their names and profile descriptions.
Taxonomy terms No matter if you prefer categories, tags or custom taxonomies, Relevanssi will return the term archive pages in searches!
Shortcode output Relevanssi can expand shortcodes and find content generated by shortcodes.
Search Relevanssi.com – using Relevanssi, of course!
I’d just like to give a shout out to how awesome this plugin is (Premium version). I have a site with pages, standard posts and a custom post for a document library where a couple gigs of PDFs are stored on AWS S3 using another plugin, and Relevanssi does a full-text index of all of it and returns context-sensitive results in less than a second. Plus good documentation and a responsive developer. This is the stuff of dreams.
Nancy Hildebrandt
I’ve used Relevanssi for several years now, and it is an essential plugin on my bigger sites. Relevanssi is an absolute must-have if you want to offer a better user experience on your WordPress website, because we all know how important a good search function is (and how bad the standard WordPress search is). Mikko keeps adding new features – I love the PDF search and more recently the related posts feature. Support is excellent, even for help with non-standard features. Thanks Mikko!
Dr. John Gøtze
I am two years new to the website business. I have, however, been a graphic designer for nearly 40 years. I purchased Relevanssi after reading so many positive reviews. I had some issues getting Relevanssi installed — not because of product, but because of where I am in the learning curve. I contacted Mikko and he got me all set up, including fixing some other issues I had created in Google, which were sure to cause problems with Relevanssi. I can’t say enough positive things about Mikko. He responded to all my questions immediately, and I mean immediately. He never snarked, was always positive, and never made me feel like I don’t know what I’m doing — which I often don’t! Mikko and his product are top-shelf. The last search plugin I used displayed way, way too many results. I was afraid all the search results would be overwhelming to the user. I like the way Relevanssi displays and allows you to narrow down results as you want.
Relevanssi Premium 2.10.2 introduces new way to search: wildcard matching. Once the wildcard matching is enabled (it is disabled by default), it introduces two new operators: * and ?. Using the wildcard operators The * operator replaces zero or more characters, so searching for w*ess would match “wilderness”, “witness”, “WordPress” and also “wess”. The ?…
Updating WooCommerce to version 4.4 breaks Relevanssi searches. After updating WooCommerce to version 4.4, Relevanssi searches no longer find results. This problem is caused by changes in WooCommerce. Those who are interested in the details can go read the GitHub issue I created. For those interested in solving the problem, next version of Relevanssi will…
Relevanssi is language agnostic in itself. It does not know any language and doesn’t really care about which language the site uses. However, there are few things that need to be considered when using Relevanssi in languages other than English. Characters: use UTF8 As long as your site uses UTF8 characters, Relevanssi can handle just…
I need to add some custom shortcodes to the list of the “removed” ones (so they don’t show in plain text in the results). However, some of them are built like [shortcode_name text=”Need to keep this in results”] and I would like the content in the text parameter to stay in the results. How do I go about this?…