Pagination without an upper bound, and why page 40 matters
Most search APIs quietly stop somewhere around page ten. The work that needs page forty is the work worth doing.
23 Jul 2026
Our page parameter has no upper bound. Page 40 is a call like any other, at the same price as page 1.
This sounds like a technicality until you try to do one of the three jobs that need it.
Finding where you actually rank
A domain that is not in the top ten is somewhere. "Not ranking" and "ranking at 47" are different diagnoses leading to different work, and you cannot tell them apart with a capped API.
Harvesting a complete result set
Competitive landscape work, corpus building and link prospecting all want the whole list rather than the head of it. A cap turns a complete answer into a sample without telling you.
Measuring the long tail of a query
The interesting question about a crowded query is often not who is first but how deep the crowd goes. That is a page-thirty question.
Two companion flags come with it: has_next_page and has_previous_page, which save you the probe request that most pagination loops waste on discovering they have finished. The endpoint reference.
Run the same measurements yourself
Free tier, no card. Every figure above came from one endpoint on a weekly schedule.