Let the back button keep your place
A search results page should preserve your place while you inspect an item. A list can preserve the query and still lose the scroll position, the selected filters, or the keyboard focus. Each missing piece adds work when someone needs to inspect several results.
Imagine a catalogue of replacement parts. You filter by size and availability, scroll down to a promising item, and open its details. The dimensions are wrong. Back takes you to the catalogue with the filters intact, but at the top of the first page. After several attempts, opening everything in separate tabs starts to look like a necessary feature of the catalogue.
For this interface, I would put the query, filters, and sort order in the URL. That lets someone copy the search or reload it without reconstructing those choices. The browser history entry can hold the more temporary details: which result was opened and where it appeared in the viewport. Those details help with returning to a particular visit, but need not be part of a link sent to a colleague.
Restoring a pixel offset alone can land on the wrong item if the list changes. I would remember the result's stable ID and its offset within the viewport, then restore that position once the list has rendered. Keeping the previous results available while refreshing them can avoid a jump through an empty loading screen. If the item has disappeared, show the nearest surviving part of the list rather than pretending the old position is exact.
Keyboard users need a way to continue from the same result too. Returning focus to the link that opened the details lets the next Tab move onward. The page should avoid a second scroll caused by restoring focus after it has already restored the viewport. If the original result is gone, focus needs a sensible fallback within the results region.
Try the complete trip with a result several screens down. Open it, go back, and open the next one using the keyboard. Repeat after changing the browser width and after removing the original result from the catalogue. The useful outcome is being able to continue comparing parts without remembering which page, row, or scroll position you had reached.