Website changes with pagination?

[mavproductions]

Hello!

I'm trying to sort through pages with pagination. Right now I have a site that maxes at 100 results, with currently 80 entries.

I have browser steps to force site from 10 to 100 pagination entries first and foremost. When it hits 101, my results won't be accurate at full scope. I see people do separate watches per page in previous years. Is that still the only option?

Are there currently any other options? Is there a way to take a "grouped snapshots" between browser steps and then combine after fetching is complete into a diff result - or something of the sort?

[krotname]

I would still model this as one watch per page, unless you can make the site expose all pages through one URL/API.

Browser Steps are pre-fetch steps for a single watch: they let changedetection.io log in, click, fill filters, etc., and then the watch stores one final fetched snapshot. The history and diff API are also keyed by one watch UUID (/watch/{uuid}/history and /watch/{uuid}/difference/...), so there is not currently a built-in "take snapshots at each pagination step and combine them into one diff" mode.

Practical options:

• create separate watches for page 1, page 2, page 3, etc.; tags help keep them grouped
• if the site has a JSON/API endpoint, monitor that and use JSONPath/JQ filters to normalize the result
• put a small script/proxy endpoint in front of it that fetches all pages and outputs one stable HTML/JSON document, then monitor that single generated URL

Browser Steps are useful if you need to log in, select a filter, or set a larger page size before the final snapshot. For true pagination aggregation, I would use separate watches or an external aggregator URL.