[Assigned] Search results are terrible

[Author]

Posts

[charlesR-4]

I am using a View with a search filter on this page: hidden link I also have Relevanssi installed on our site. I've checked all of the Relevanssi settings and everything looks good, I have given a lot of weight to the title of the post vs content, and I have rebuilt the index.

The problem is that the search results are terrible. I can search for a word and the top 10-20 results don't even contain that word. However, when I go to Dashboard > Admin Search the results are perfect. How can I get the View search results closer to what I see on the Admin Search?

[Minesh]

Hello. Thank you for contacting the Toolset support.

The thing is that you set to search within the post title and content. If content has word mother then and then it will be show as search result.

For instance, this is the post where mother word is availalbe and that is your first post with the search result:
- hidden link

Either you can search within post title. I set your view to search only in post title:
- hidden link

And I can see only three result as you can see with the above link.

[charlesR-4]

I have weighted the title so much higher than the content in Relevanssi's search setting that this doesn't make sense. Are these settings not applied to the Toolset search?

[Minesh]

Well - you will require to check this with Relevanssi support as when you use Relevanssi integration Toolset's role is just passing the whole query to Relevanssi and Relevanssi handles further.

I also noticed the all posts are not indexed. It get stuck after:

Indexed 316 posts (total 624), processed 624 / 1287.

Please get in touch with Relevanssi support and share what is your expected output and they will help you to adjust the relevanssi query accordingly.

[charlesR-4]

I asked the makers of Relevanssi about this first, and they said they didn't know anything about Toolset or how it handles the query or results, which is why I came here. Can you please tell me in a more specific and technical way how Toolset interacts with Relevanssi so I can tell them, and then ask them what might be the problem?

[Minesh]

Well - when you try to build the index the content/posts using Relevanssi:
=> hidden link

It stops somehow after: Indexed 316 posts (total 624), processed 624 / 1287.
- It does not finish the job to index the 1287 posts.

This is a relevenssi feature not Toolset.

Here is the Doc that shows information how Relevanssi integration works:
- https://toolset.com/course-lesson/searching-texts-in-custom-fields-with-toolset-and-relevanssi/

when you use the Relevanssi integration the search query will be passed over to Relevanssi, having said that relevenssi will the reponsible to handle, build and run the query.

I see there are number of hooks available as per their doc:

- add_filter( 'relevanssi_orderby', function( $orderby ) { return 'post_title'; } );
add_filter( 'relevanssi_order', function( $order ) { return 'asc'; } );

More info:
- hidden link
- https://wordpress.org/support/topic/relevanssi_orderby-relevanssi_order/

Maybe you want to add weight to the post title using the following hook:
- hidden link

It commond query for relevenssi and I hope they will have solution for this.

[charlesR-4]

I see the indexing issue on the staging site, I can't explain that, but on the live production site there is no indexing issue. It has indexed all pages, posts, and the 'film' custom post type.

Relevanssi support has walked me through a few different searches of the site. The problem is that the site results outside of Toolset are all working as expected. In fact, admin search and basic site search of a word in the 'film' post type get the same excellent results. The results in the Toolset View are almost a complete inversion of the admin search results-- those posts that appear at the top of the admin search are at the very bottom of the View search. It's not a complete 1:1 inversion, but very close.

The only ordering options in Relevanssi are to order by relevance or post date, and I have it set to 'relevance' (the default). There is no "inverse relevance" option, but that appears to be what the View is doing with the results it is getting from Relevanssi.