fix: fetch Google SERP mutliple pages #2244
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updated our documentation to include information about how to fetch multiple pages from Google in 1 request
Note
Low Risk
Documentation-only change with no runtime or behavioral impact to the proxy/service.
Overview
Updates
google_serp_proxy.mdto clarify pagination behavior for Google SERP requests.Documents that Google’s
numquery parameter is deprecated/ignored, and introduces a supportednumPagesparameter (1–10) that fetches multiple result pages in one request, including pricing implications and an alternative using Google’sstartparameter.Written by Cursor Bugbot for commit 41ac9ee. Configure here.