Programmable Search API pagination and result set consistency

The Google Programmable Search API allows for the retrieval of search results across multiple pages, typically limited to 10 results per request and a maximum of 100 results per query. When implementing deep pagination to capture the full available set, there is a need to ensure that the data remains stable across sequential requests.

Because the underlying web index is dynamic, the total result count and the specific ordering of items may shift between the initial request and subsequent paginated calls. This introduces uncertainty regarding whether a client can reliably map a complete, non-overlapping set of results for a single query execution.

• Does the API provide a mechanism to lock the result set for a specific query to prevent shifts during pagination?
• What is the documented behavior for handling result set drift when the total count changes between page requests?