Commit fad13e7
fix: fetch Google SERP multiple pages (#2244)
This PR updated our documentation to include information about how to
fetch multiple pages from Google in 1 request
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Documentation-only change with no runtime or behavioral impact to the
proxy/service.
>
> **Overview**
> Updates `google_serp_proxy.md` to clarify pagination behavior for
Google SERP requests.
>
> Documents that Google’s `num` query parameter is deprecated/ignored,
and introduces a supported `numPages` parameter (1–10) that fetches
multiple result pages in one request, including pricing implications and
an alternative using Google’s `start` parameter.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
41ac9ee. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>1 parent ab7ed2e commit fad13e7
1 file changed
Lines changed: 32 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
59 | 59 | | |
60 | 60 | | |
61 | 61 | | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
62 | 94 | | |
63 | 95 | | |
64 | 96 | | |
| |||
0 commit comments