Before You Start
Which Google search type do I need?
Which Google search type do I need?
Fast SERP supports multiple Google verticals — web search, news, shopping, images, and more. This page covers standard web search (
google.com/search). If you need a different vertical, see the relevant page for that search type.What QPS (queries per second) do I need?
What QPS (queries per second) do I need?
Consider both your POC/testing volume and your expected production volume before getting started. This helps ensure your zone is configured correctly for your workload. If you’re unsure, start with an estimate — your account manager can adjust your rate allocation as your usage grows.
Do I need to control or throttle traffic on my end?
Do I need to control or throttle traffic on my end?
If your system has internal rate-limiting or load control mechanisms, share those details with your account manager. This helps align your zone’s capacity with your infrastructure’s behavior and avoids unnecessary errors.
Should I use the native proxy interface or the REST API?
Should I use the native proxy interface or the REST API?
Fast SERP works best with the native proxy interface — it is slightly faster than the REST API. A REST API interface can be provided if required by your architecture.
Which geographic region will my scrapers run from?
Which geographic region will my scrapers run from?
Fast SERP supports multiple deployment regions: US East, US West, EU, and APAC. Knowing your scraper region(s) in advance helps optimize routing and latency. If your production traffic is distributed across multiple regions, let your account manager know.
Fast SERP Request
Fast SERP works best with the native proxy interface. If you need a REST API interface for your architecture, one can be provided.For Fast SERP, both the
x-unblock-data-format: parsed_lightrequest header and the brd_json=1 URL parameter are required. Omitting either will result in an unexpected response format.Native proxy request
Organic results
Use header valuex-unblock-data-format: parsed_fast — this request header will return organic results.
Organic results with with Google’s “Top Stories”
Use header valuex-unblock-data-format: parsed_light — this request header will return Google’s “Top Stories” in the response alongside organic results.
Response Format
organic array
The primary array of web search results, present in both parsed_light and parsed_fast responses.
| Field | Type | Description |
|---|---|---|
link | string | URL of the result page |
title | string | Title of the result |
description | string | Snippet/summary shown in the search result |
global_rank | integer | Rank position of the result on the page |
extensions | array | Optional list of site links associated with the result (see below) |
extensions items
| Field | Type | Description |
|---|---|---|
type | string | Type of extension, e.g. site_link |
link | string | URL of the site link |
text | string | Anchor text of the site link |
top_stories array
Returned only when using x-unblock-data-format: parsed_light. Contains Google’s “Top Stories” news carousel results.
| Field | Type | Description |
|---|---|---|
link | string | URL of the news article |
title | string | Headline of the article |
source | string | Name of the news publisher |
date | string | Publication date/time of the article |
image | string | URL of the article’s thumbnail image |