Testing downweighting

[mearso]

Hi All

First time posting - hoping to finally get to grips with our setup and start using the 'full power of this station' (our funnelback setup).

I've been asked to downweight some results and so followed the instructions at https://community.funnelback.com/knowledge-base/implementation/query-processing/ranking/upweight-or-downweight-sections-of-a-site-in-the-search-results

My question is - what is the good practice way to test configuration changes? Some general pointers would be much appreciated - thanks all

[plevan]

You can pass the cool.X parameters interactively via CGI when you run a query, so this can be a good way to test how different weightings will affect the result set.

Generally speaking tuning the ranking algorithm is the best way to get the best overall improvement in your result set because there is a much more rigourous process involved when determining the optimal ranking settings.

However if you do want to adjust the values manually adding the cool.X parameters will show you immediately how the results are affected.

So for the QIE example - once you have added the qie.cfg and reindexed you can run searches adding cool.4=X to the URL to see the effect of the QIE. e.g. http://mysite/s/search.html?collection=mycollection&query=searchterm&cool.4=0.7

Similarly you can add cool.68, mentioned in one of the other examples to the URL as well once the gscopes are set up in the index.

[mearso]

Thanks for that - I'm struggling to see much change using the cool.X parameters, so perhaps the problem wasn't really much of a problem. I think I'll take your advice and start learning more about the tuning - seems like a more gradual and understandable way to work with our results. Hopefully I can get more people our end involved in that.

[plevan]

Generally speaking - before you look at the ranking algorithm it is well worth looking at a few other factors which can have a far greater impact on ranking.

• If you have control of your content then consider adding noindex (html comment) tags to the template so that you hide headers/footers/navigation from Funnelback. Removing the irrelevant content will have a big impact on what is identified as a relevant result (eg. a search for contact won't potentially return every page because it's in your navigation). https://docs.funnelback.com/15.12/develop/key-programs-and-scripts/padre.html#controlling-indexable-content explains how the noindex tags work. This technique removes irrelevant content (noise) from the index making the results much more focussed.

• Use synonyms in conjunction with your analytics to feedback and improve the search. See: https://www.funnelback.com/blog/5-simple-tips-to-make-the-most-out-of-your-search-analytics This blog post I wrote a couple of years ago covers some of the basic techniques. This technique bridges the gap between user and organisational language by mapping user words to the words you use on your site meaning that the user's search terms match the words in the index.