Hi, not really that I can see in our current code outside of the catch portion of a try/catch block, and this is only for “Use Algolia with the native WordPress search template” search page settings. If you’re using autocomplete/instantsearch, that’s all going to be frontend/javascript libraries.
Best bet is probably going to be analytics and whatnot from your algolia.com dashboard, for analysis.
Okay thanks.
I have 8 post types, each set to 3-5 results and the index included the content so I think this is what was draining the search requests.
I excluded content from indexes and limited results to 2 each. I think it will help. I may have to increase the debounce value slightly as well.
The smaller amount of sources needed for the Autocomplete, the better. If it meets needs, using the “All Posts” option will put all searchable post types into one index, and thus also reduce the amount of indexes to query against. We have filters available to limit which post types get included, without having to adjust their “exclude from search” boolean value.
I’m curious if some of the info at https://www.youtube.com/watch?v=hYldeR2mPTs could help
