Gravatar for wvuong@captechconsulting.com

Question by wvuong, May 10, 2016 10:23 AM

Coveo for Sitecore 4 Cloud Edition Maximum Returned Results

We are in the process of upgrading Coveo for Sitecore 3 to 4/Cloud Edition. Currently in 3 we had to update our Maximum Returned Results value in the CES Admin tool 5000 from 1000. Does this initial limit of 1000 exist in the Coveo Cloud edition and if so where do we update this?

2 Replies
Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, May 11, 2016 10:27 AM

Hi William,

This setting is currently not available in Coveo Cloud.

Can you explain to me why did you have to increase this value with Coveo for Sitecore 3.0 please? It will help me finding an alternative approach for you.

Thank you,

Jeff

Gravatar for wvuong@captechconsulting.com

Comment by wvuong, May 11, 2016 10:28 AM

We have a search page with 2000+ results and (at least in 3.0) when we got to the page corresponding to the 999th item, going to the next page would start back at item 1.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 11, 2016 10:49 AM

Are you using the Coveo JavaScript Search Framework for your user interface or you coded it using LINQ?

Gravatar for wvuong@captechconsulting.com

Comment by wvuong, May 11, 2016 11:46 AM

Search Framework

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 11, 2016 1:07 PM

With the Coveo JavaScript Search Framework V1.0 included with Coveo for Sitecore 4.0, the Pager component now have a maxNumberfPages attribute set to 100 by defaut to avoid displaying more than 1000 results as you experienced with the Coveo JavaScript Search Framework V0.9 included with Coveo for Sitecore 3.0.

Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, May 11, 2016 1:26 PM

The Pager component problem you experienced with the Coveo JavaScript Search Framework V0.9 included with Coveo for Sitecore 3.0 was fixed.

With the Coveo JavaScript Search Framework V1.0 included with Coveo for Sitecore 4.0, the Pager component now have a maxNumberfPages attribute set to 100 by default to avoid displaying more than 1000 results. With the default value, the visitors will only be able to display the 1000 first search results for any given query. If you decrease the maxNumberfPages setting value, you will limit the UI to fewer search results.

In most cases, a visitor that is scrolling through all the first 1000 search results is a very bad smell indicating very poor relevance of the search results for his query. This should be solved not by increasing the number of returned results, but by ensuring:

  1. The search results are sorted by relevance by default
  2. Query Ranking Expressions (QRE)/boosting is used to improve default index relevance
  3. The Sitecore items are indexed along with their HTML representation and this body doesn't contain the header/footer/navigation areas (see Indexing Only Relevant Parts of Sitecore Rendered Content)

If displaying more than 1000 results is really a business requirement, it can only be done with a CES7 on-premises index by increasing the maxNumberfPages value and the Maximum Returned Results value in the CES7 administration tool.

If you really want to be able to configure this setting for a Coveo Cloud index, I suggest you to add an idea on our ideas portal: https://coveo.ideas.aha.io/ideas

Thank you,

Jeff

Ask a question