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.How to get organic results
Use header valuex-unblock-data-format: parsed_fast, this request header will return organic results.
Organic results: response format
organic array
The primary array of web search results, present in both parsed_light and parsed_fast responses.
extensions items
Example response, parsed_fast (organic results)
Organic results with “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.
general object
Returned in every parsed_light response. Reports the query you sent and the query Google actually ran, which lets you detect when Google truncates a search.
If
detected_query differs from query, check for a spelling section in the response. If spelling is present, the difference is due to automatic spelling correction and the response is valid. If spelling is absent, the query was cloaked and results were returned for a truncated version of the original query.spelling object
Returned in a parsed_light response only when Google applies or suggests a spelling correction. All fields are nullable and appear only when Google provides that variant.
top_stories array
Returned only when using x-unblock-data-format: parsed_light. Contains Google’s “Top Stories” news carousel results.
Example response, parsed_light (with Top Stories)
Query truncation detection and the
query_rejected blocked-query behavior apply to the whole SERP API, not just Fast SERP. See How to detect query truncation and What happens when a query is blocked on the SERP API debugging page.