Before You Start
Which Google search type do I need?
Which Google search type do I need?
Fast SERP supports multiple Google verticals. For news results, you should target
google.com/search?tbm=nws — not news.google.com. The two endpoints return different response structures; this page covers google.com/search?tbm=nws only.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 News Search Request
Fast SERP for Google News 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
Response Format
A successful response returns a JSON object with the following top-level fields.news array
The primary array of individual news results.
| Field | Type | Description |
|---|---|---|
link | string | URL of the news article |
title | string | Headline of the article |
source | string | Name of the news publisher |
source_logo | string | URL of the publisher’s logo image |
date | string | Publication date/time of the article |
image | string | URL of the article’s thumbnail image |
global_rank | integer | Rank position of the result on the page |
article_sets array
Grouped article clusters organized by topic, each containing a heading label and an items array of articles.
article_sets is not guaranteed to appear in every response. Your implementation should handle its absence gracefully.