fix: fetch Google SERP multiple pages by danpoletaev · Pull Request #2244 · apify/apify-docs

danpoletaev · 2026-02-12T12:42:01Z

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.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.

^{Written by Cursor Bugbot for commit 41ac9ee. Configure here.}

apify-service-account · 2026-02-12T12:44:49Z

Preview for this PR was built for commit 41ac9ee and is ready at https://pr-2244.preview.docs.apify.com!

apify-service-account · 2026-02-12T12:52:00Z

Preview for this PR was built for commit 5fe1a3c and is ready at https://pr-2244.preview.docs.apify.com!

apify-service-account · 2026-02-12T13:02:28Z

Preview for this PR was built for commit f38cb7a1 and is ready at https://pr-2244.preview.docs.apify.com!

bliuchak · 2026-02-12T15:52:11Z

@danpoletaev just out of curiosity, could you run that copy-skill for this docs, that was introduced at our last all-hands by docs team? :)

apify-service-account · 2026-02-13T08:59:45Z

Preview for this PR was built for commit c54a9d67 and is ready at https://pr-2244.preview.docs.apify.com!

TC-MO · 2026-02-13T10:20:35Z

I noticed yesterday that we had slightly wrong folder structure for skills to be available for Claude Code, I merged master cause we've pushed a fix for that

apify-service-account · 2026-02-13T10:24:00Z

Preview for this PR was built for commit babbe661 and is ready at https://pr-2244.preview.docs.apify.com!

marcel-rbro · 2026-02-13T11:16:12Z

I'm not sure of the review skill checks this, but there's a typo in the PR title: mutliple -> multiple

danpoletaev · 2026-02-13T12:01:53Z

I'm not sure of the review skill checks this, but there's a typo in the PR title: mutliple -> multiple

Fixed

bliuchak

Nice!

TC-MO · 2026-02-16T00:12:52Z

sources/platform/proxy/google_serp_proxy.md


+## Fetch more than one page of results
+
+By default, Google returns up to _10 search results per page_. To retrieve additional results beyond the first page, use the `numPages` query parameter. This allows you to fetch multiple pages of search results in a single request.


This sentence feels like filler, we already convey that you can fetch more in previous one

Suggested change

By default, Google returns up to _10 search results per page_. To retrieve additional results beyond the first page, use the `numPages` query parameter. This allows you to fetch multiple pages of search results in a single request.

By default, Google returns up to _10 search results per page_. To retrieve additional results beyond the first page, use the `numPages` query parameter.

TC-MO

Some changes requested

I've simplified the language a bit
got rid of double admonition
removed filler words/phrases

TC-MO · 2026-02-16T00:13:20Z

sources/platform/proxy/google_serp_proxy.md

+:::
+
+:::info Manual pagination with the `start` parameter
+You can also use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).


Suggested change

You can also use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).

Use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).

TC-MO · 2026-02-16T00:14:37Z

sources/platform/proxy/google_serp_proxy.md

+Google has deprecated the `num` query parameter, which previously controlled the number of results displayed per page.
+
+:::caution Ignored parameter
+If you include the `num` parameter in your requests, it will be completely ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.


Suggested change

If you include the `num` parameter in your requests, it will be completely ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.

If you include the `num` parameter in your requests, it will be ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.

TC-MO · 2026-02-16T00:17:18Z

sources/platform/proxy/google_serp_proxy.md

+:::caution Pricing for multi-page requests
+Each page counts as a separate request. A request with `numPages=10` is priced as 10 requests.
+:::
+
+:::info Manual pagination with the `start` parameter
+You can also use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).
+:::


Double admonition is really bad practice. I recommend we keep :::caution admonition and remove :::info by remaking it into general prose

Suggested change

:::caution Pricing for multi-page requests

Each page counts as a separate request. A request with `numPages=10` is priced as 10 requests.

:::

:::info Manual pagination with the `start` parameter

You can also use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).

:::

:::caution Pricing for multi-page requests

Each page counts as a separate request. A request with `numPages=10` is priced as 10 requests.

:::

Use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).

TC-MO · 2026-02-16T00:18:23Z

sources/platform/proxy/google_serp_proxy.md

+
+When you specify `numPages`, the proxy makes multiple requests in the background and merges them into a single HTML response.
+
+### Usage


Suggested change

### Usage

### `numPages` parameter

TC-MO · 2026-02-16T00:19:01Z

sources/platform/proxy/google_serp_proxy.md

+If you include the `num` parameter in your requests, it will be completely ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.
+:::
+
+To retrieve more than 10 results, use the `numPages` parameter described above instead.


Please do not use directional language

Suggested change

To retrieve more than 10 results, use the `numPages` parameter described above instead.

To retrieve more than 10 results, use the `numPages` parameter described before instead.

apify-service-account · 2026-02-16T09:35:32Z

Preview for this PR was built for commit aad4da2a and is ready at https://pr-2244.preview.docs.apify.com!

fix: fetch Google SERP mutliple pages

41ac9ee

danpoletaev requested review from bliuchak and marcel-rbro February 12, 2026 12:42

danpoletaev self-assigned this Feb 12, 2026

danpoletaev requested a review from TC-MO as a code owner February 12, 2026 12:42

danpoletaev added the adhoc Ad-hoc unplanned task added during the sprint. label Feb 12, 2026

github-actions bot added this to the 134th sprint - Unblocking team milestone Feb 12, 2026

github-actions bot added the t-unblocking Issues with this label are in the ownership of the unblocking team. label Feb 12, 2026

refactor: clean up

5fe1a3c

refactor: clean up

f38cb7a

refactor: fix by skill

c54a9d6

Merge branch 'master' into fix/google-serp-multiple-pages

babbe66

danpoletaev changed the title ~~fix: fetch Google SERP mutliple pages~~ fix: fetch Google SERP multiple pages Feb 13, 2026

bliuchak approved these changes Feb 13, 2026

View reviewed changes

TC-MO reviewed Feb 16, 2026

View reviewed changes

TC-MO requested changes Feb 16, 2026

View reviewed changes

refactor: clean up

aad4da2

danpoletaev requested a review from TC-MO February 16, 2026 09:36

TC-MO approved these changes Feb 17, 2026

View reviewed changes

danpoletaev merged commit fad13e7 into master Feb 17, 2026
13 checks passed

danpoletaev deleted the fix/google-serp-multiple-pages branch February 17, 2026 12:25

bliuchak added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label Feb 18, 2026


		## Fetch more than one page of results

		By default, Google returns up to _10 search results per page_. To retrieve additional results beyond the first page, use the `numPages` query parameter. This allows you to fetch multiple pages of search results in a single request.

	You can also use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).
	Use Google's `start` parameter to handle pagination manually. The `start` parameter specifies the index of the first result (e.g., `start=10` for page 2, `start=20` for page 3).

	If you include the `num` parameter in your requests, it will be completely ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.
	If you include the `num` parameter in your requests, it will be ignored. Google no longer supports this parameter, and Google SERP proxy does not process it.


		When you specify `numPages`, the proxy makes multiple requests in the background and merges them into a single HTML response.

		### Usage

	To retrieve more than 10 results, use the `numPages` parameter described above instead.
	To retrieve more than 10 results, use the `numPages` parameter described before instead.

Comments

Conversation

danpoletaev commented Feb 12, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

apify-service-account commented Feb 12, 2026

Uh oh!

apify-service-account commented Feb 12, 2026

Uh oh!

apify-service-account commented Feb 12, 2026

Uh oh!

bliuchak commented Feb 12, 2026

Uh oh!

apify-service-account commented Feb 13, 2026

Uh oh!

TC-MO commented Feb 13, 2026

Uh oh!

apify-service-account commented Feb 13, 2026

Uh oh!

marcel-rbro commented Feb 13, 2026

Uh oh!

danpoletaev commented Feb 13, 2026

Uh oh!

bliuchak left a comment

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

TC-MO left a comment

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

TC-MO Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

apify-service-account commented Feb 16, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

danpoletaev commented Feb 12, 2026 •

edited by cursor bot

Loading

TC-MO Feb 16, 2026 •

edited

Loading