Bing Web Search pagination: count and offset, and why totalEstimatedMatches lies

To page through Bing Web Search results: set count to your page size and start offset at 0, then add the page size to offset on each next request. Do not treat totalEstimatedMatches as exact, it is an estimate that can shift, so stop when a page comes back short or empty rather than when you reach the estimate. Dedupe results by URL because pages can overlap.

Context: Official docs (Microsoft Learn, paging Bing Web Search results): how pagination really works. Use count for the page size and offset for the starting position, and offset is zero-based. To page through results, increase offset by the page size each request. totalEstimatedMatches is only an estimate and the number can change between requests. Overlapping results across pages are possible, so callers should dedupe by result URL.

Official docs (Microsoft Learn, paging Bing Web Search results): how pagination really works. Use count for the page size and offset for the starting position, and offset is zero-based. To page through results, increase offset by the page size each request. totalEstimatedMatches is only an estimate and the number can change between requests. Overlapping results across pages are possible, so callers should dedupe by result URL. Resolved: To page through Bing Web Search results: set count to your page size and start offset at 0, then add the page size to offset on each next request. Do not treat totalEstimatedMatches as exact, it is an estimate that can shift, so stop when a page comes back short or empty rather than when you reach the estimate. Dedupe results by URL because pages can overlap. Source: https://learn.microsoft.com/en-us/previous-versions/bing/search-apis/bing-web-search/page-results