Q: The hits are always numbered 1..N..is it possible to take the page number into account? 20 hits per page, the first item on page #1 would be “1”, first item on page #2 would be “21" …the current fixed 1..N numbering is counter-intuitive.

👋 We don't number the hits in the API responses. Can you post a snippet or screenshot to show that?

Example: https://github.com/zopyx/zopyx.typesense/blob/master/src/zopyx/typesense/browser/static/app.js

Ah, you mean the numbers always starting with "1" in the UI even when I click on page 2, 3, etc.?

yes

I see the HTML is being rendered using

<li>

-- that explains those 1 to 10 numbering.

using an outer ordered list

You can probably add a CSS

list-style: none

rule to remove that numbering, but @Jason Bosco might have an alternative approach here.

Or use

ul

(unordered list) instead of

ol

(ordered list).

It looks like instantsearch might have a way to manage ordering like what Greg mentioned using __hitIndex. Could you try this out: https://www.algolia.com/doc/api-reference/widgets/hits/js/#widget-param-item

if the numbering is coming from an

<ol>

element there is a

start

attribute that lets you set the number sequence starting point