Often users would like to get a free trial of Relevanssi Premium, but we always say no. Why is that? The answer is simple: we offer our customers such liberties that providing a temporary trial use is difficult. Relevanssi customers have liberties We don’t believe in spying our customers or restricting their use of the…
Sometimes you want to get a specific post as the first result for a certain search, but Relevanssi doesn’t return the right post as the first result by itself for some reason. Relevanssi Premium has a tool for these situations: pinning. Pinning lets you specify keywords for each post and whenever that keyword is used…
Query Monitor is by far the best thing for a WordPress developer. It’s billed as the “Developer Tools panel for WordPress”, and that’s a good way to put it. If you’ve ever used the browser developer tools, you know what to expect. Query Monitor is a good way to figure out problems in Relevanssi searches,…
After the Summer break, Relevanssi is back with new versions, both to Premium and free. These are mostly small improvements, but when testing the new version, I discovered a bug in the comment indexing that has made Relevanssi not index comments when they are added. I’m not sure why this hasn’t come up in tests…
Is is possible to set Relevanssi in a way that it would return only perfect matches for queries up to 3 characters, but any words that starts with the queried term if it has 4 characters or more? – Originally asked here Yes, but it requires a bit of coding. With the latest version (free…
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?…
By default Relevanssi tends to prefer longer posts. The default TF × IDF weights Relevanssi uses simply count the term frequency, ie. how many times a word appears in the post. That prefers longer posts as they usually have the search term appear more often. However, a 500-word post with 15 search term appearances might…