What is Parsing?
Parsing for SERP API is the process of transforming a raw HTML response into a structured JSON with fields and values of data. This advanced parsing functionality is supported specifically for Google & Bing. When parsing is activated, data from SERP HTMLs are further structured into usable fields and values (such as,rank, link, title, description, rating, and dozens more fields) enabling you to monitor competitor SERP rankings, analyze keyword trends, and gather valuable market insights.
Send a Basic Parsed Request
The following is the simplest GET parsed request with SERP API using eitherbrd_json=1 OR  brd_json=html:
Parsing is supported for both Google and Bing search engines
The above request is a synchronous request (the response is received in real-time). If you are looking to send an asynchronous parsed request see here.
Basic Request - Breakdown
| brd.superproxy.io | Address of our load balancer that will find the fastest Super Proxy for your request | 
| Infrastructure port of our Super Proxies that is used to receive your requests | |
| -user brd-customer-<customer_id> -zone-<zone_name> | Username authentication. In its most basic form, it defines your username and what zone you will use for your request. | 
| ZONE_PASSWORD | Zone password. All zones have passwords that are used for authentication ` | 
| brd_json=1 | Returns parsed JSON instead of raw HTML | 
| brd_json=html | Returns parsed JSON + full nested HTML | 
Expected Parsed Output when using brd_json=1
The following is the exact JSON response received when sending the request above:
JSON Response
JSON Response
A Comprehensive Guide to Parsed Google SERP JSON Data
At the top of the JSON response, you can find thegeneral field, which contains details about the search you ran and also includes the “results count” from the response.

general field
| general.search_engine | the search engine used for the search | 
| general.query | the keywords used for the search | 
| general.results_cnt | the results count Google doesn’t display results count for Mobile, so this field is supported only with desktop search results. | 
| general.search_time | the response time to get the results page | 
| general.language | the language that was set for the search, Default: hl=en | 
| general.location | the location that was targeted with the search,(based on the localizationandgeo-locationparameters) | 
| general.mobile | the device the search was performed with (desktop/mobile) | 
| general.basic_view | deprecated | 
| general.search _type | the type of search that was set to the request | 
| general.Page_title | results page title | 
| general.Code_version | Bright data parser version | 
| general.Timestamp | the time when the search executed | 
| Input.original_url | the url used for the search, this url includes all parameters applied for the search.applied for the search. | 
Starter fields to know
| JSON field | Description | 
| type | The field type (site_link, text, rating, etc.) | 
| title | The text header, mostly the link text. | 
| description | The description under the link | 
| referral_link | Redirection link | 
| image | This field can contain the image base64 string or the Image url | 
| image_alt | Image alternative name | 
Explanation of other fields
rank
rank
| rank | indicates the position of the element in accordance with the other elements within that component | 
| global_rank | indicates the position of the element in accordance with all the elements in the SERP | 

spelling
spelling
When your search terms are inaccurate, Google suggests other search terms, which will show under the 

spelling field.Subfields:| Original_text | the text that was searched | 
| Original_empty | true, means that no results were found. | 
| Auto_corrected_link | link to suggested result | 
| auto_corrected_text | the suggested link text | 
- HTML
- JSON

rating & reviews
rating & reviews
Some of the components within a SERPs can include the 
reviews and rating fields- HTML
- JSON

extensions
extensions
Some SERP results could include site sub-links (AKA site links) that are displayed as a vertical or horizontal list

 Vertical - marked with extended:true
- HTML
- JSON

 Horizontal - not marked with `extended:true`
- HTML
- JSON

display_link
display_link
These are breadcrumbs from the URL in the result:
- HTML
- JSON

organic
organic
Main search results are called organic results and are located in the organic json node.
- HTML
- JSON

ads
ads
There are four different locations for ads within a SERP and each are parsed separately:




| top_ads | Ads that are located at the top of the SERP | 
| top_pla | Ads that are located within a special carousel at the top of a SERP | 
| jackpot_pla | Ads that are located within the right side panel in shopping ads. It usually appears when a particular product matches your search perfectly. | 
| bottom_ads | Ads that are located at the bottom of the SERP | 
By default, SERP API displays “organic” adds (based on IP location and cookies, etc). If you wish SERP API to display ads in different ways (incognito, adtest) you can change this in your SERP API zone on the control panel.
top_ads
top_ads
- HTML
- JSON

top_pla
top_pla

jackpot_pla
jackpot_pla

bottom_ads
bottom_ads

people_also_ask
people_also_ask
The 
In a SERP,  the PAA box questions are connected to answers that users can click to read. This can help people better understand their initial question without clicking on other results. Each question here has its answer under the “answers” element.
people_also_ask section includes questions Google automatically generates based on queries it believes are related to your question.answers
In a SERP,  the PAA box questions are connected to answers that users can click to read. This can help people better understand their initial question without clicking on other results. Each question here has its answer under the “answers” element.- HTML
- JSON

videos
videos
- HTML
- JSON

twitter
- HTML
- JSON

top_stories
top_stories
- HTML
- JSON

knowledge
knowledge
Provides a brief overview of the searched topic in a knowledge panel (desktop- on the right side, mobile - at the top)
- HTML
- JSON

widgets
| knowledge.widgets.social_media_presence | includes profiles | 
| knowledge.widgets.sideways_refinements | people also ask | 
recipes
recipes
When searching for food items the SERP might contain also recipes

snack_pack_map & snack_pack
snack_pack_map & snack_pack
Relates to the Google maps displayed in a SERP.
This map part is displayed in the JSON and includes the coordinates of the map location.
If the map includes pins of specific locations, the JSON will include a 
snack_pack_map
This map part is displayed in the JSON and includes the coordinates of the map location.- HTML
- JSON

snack_pack
If the map includes pins of specific locations, the JSON will include a snack_pack field for each location with additional details like open hours, contact details, tags etc.- HTML
- JSON

related
related
flights
flights
- HTML
- JSON

hotels
hotels
Bright Data’s SERP API makes it easy to collect hotel data, like prices, availability, reviews, and more.Here’s how to collect the data from the hotel knowledge graph using Google Search and how to get even more details from the hotel page on Google Travel.When you search for a hotel using Google Search, its details and reviews appear in the resulting knowledge graph on the right.



pagination
pagination
- HTML
- JSON

| current_page | the requested page location within the search | 
| first_page_link | Link of the first page | 
| prev_page_linknext_page_link | referring to requested page | 
| prev_page_startnext_page_start | first searched results number in previous and next pages | 
| prev_pagenext_page | number of pages for previous and next pages | 
| page | page number | 
| link | link to page | 
| start | first result in the page | 
AI Overview
AI Overview
ai_overview
Google’s Generative AI Overviews are shown on various SERPs when the query aligns with topics Google considers suitable for generative answers.
AI Overviews Response Example Schema
Light Parser for Google
Add thex-unblock-data-format: parsed_light header to your HTTP requests.
- Focus on Top 10 results: Extracts only the top 10 organic search results from Google.
- Optimized speed: Approximately 50% faster latency compared to standard parsing.

