Console

1. In the Google Cloud console, go to theAI Applications page.

   AI Applications

2. Select the app for which you want to create the boost control.

3. On your app's overview page, make sure you are on theSystem overview tab.

4. In theSignalstage, click theBoost/Bury tile.

5. ClickCreate control.

6. In theCreate control pane, do the following:

   1. ForName Your Control, enter a name for your boost/bury control and clickContinue.

   2. ForSet Rule Scope & Impact, define the actions that you want to trigger with this control:

      1. Select a data store from the list. If you want the action to beapplied to multiple data stores, create a control for each datastore.

      2. ForFilter, add a filter.

         This is a string specifying requirements that must bemet by the document. Only if the document matches all therequirements, the boost condition is applied. Otherwise there is nochange. If you don't specify a filters, then the boost is applied toall documents in the data store.

         To understand how to write filter expressions, seeFilter expression syntax andExamples of filter expressions.

      3. ForBoost/bury value, select a boost/bury value in the range [-1, 1] using the slider.The slider moves in steps of 0.01.

      4. ClickContinue.

   3. ForOptional: When This Rule Activates, set the following conditions that trigger the control. If no conditions are configured, the control is always in effect:

      1. AddPartial match query terms. The control takes effect when thesequery terms match partially.

      2. AddExact match query terms. The control takes effect when these queryterms match exactly.

      3. To add an active time range, clickAdd time range and setStart time 1 andEnd time 1. This defines the window when thecondition is active. You can add a maximum of 10 time ranges.

      4. ClickContinue.

   4. If you want to apply this control as soon as it's created, forAdditional settings, turn onPublish this control immediately and clickContinue.

7. ClickSubmit.

REST

A boost serving control is defined as a control with aboostAction.

Use the following instructions to create a boost serving control.

For field details, see theengines.controls API reference and theengines.controls.create API reference.

1. Find your app ID. If you already have your app ID, skip to the next step.

   1. In the Google Cloud console, go to theAI Applications page.

      Go to Apps

   2. On theApps page, find the name of your app and get the app's ID fromtheID column.

2. Run the following curl commands to create your controls.

   curl-XPOST\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/controls?controlId=CONTROL_ID"\-d'{"displayName": "DISPLAY_NAME","solutionType": "SOLUTION_TYPE_SEARCH","useCases": [  "USE_CASE"],"conditions": { "queryTerms": [   {     "value": "VALUE",     "fullMatch":FULL_MATCH   } ], "activeTimeRange": [   {     "startTime": "START_TIMESTAMP",     "endTime": "END_TIMESTAMP"   } ]},"boostAction": {  "boost":BOOST_VALUE,  "filter": "FILTER",  "dataStore": "DATA_STORE_RESOURCE_PATH" }}'

   Replace the following:

   • PROJECT_ID: the number or ID of your Google Cloud project.
   • APP_ID: the ID of the Vertex AI Search app.
   • CONTROL_ID: a unique identifier for the control.The ID can contain [1-63] characters that can be letters, digits, hyphens,and underscores.
   • DISPLAY_NAME: the human-readable name for the control.Google recommends that this name provide an indication of when or why touse the control. Must be a UTF-8 encoded string with length [1,128].
   • USE_CASE: must be eitherSEARCH_USE_CASE_SEARCH orSEARCH_USE_CASE_BROWSE. IfSEARCH_USE_CASE_BROWSE is specified,thenCondition.queryTerms can't be used in the condition.
   • CONDITION: an optional field that defines when thecontrol should be applied. Contains the following fields:
     • VALUE: the specific query value to matchagainst. It's a lowercase UTF-8 string with length[1, 5000]. IfFULL_MATCH_1 istrue, this field can have atmost three space-separated terms.
     • FULL_MATCH: a boolean that indicates whetherthe search query needs to exactly match the query term. When set totrue, it requiresSearchRequest.query to completely match thequeryTerm.value. When set tofalse, it requiresSearchRequest.query to containqueryTerm.value as a substring.
     • START_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the start of a time range.
     • END_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the end of a time range.
   • BOOST_VALUE: a floating point number in the range [-1,1]. When the value isnegative, results are demoted (they appear lower down in theresults). When the value is positive, results are promoted(they appear higher up in the results). For more information, seeboostAction.
   • FILTER: a string specifying requirements that mustbe met by the document. If the document matches all the requirements, theboost is applied. Otherwise there is no change. If this field is empty, thenthe boost is applied to all documents in the data store. For the filteringsyntax, seeFilter expression syntax.Note: The document fieldtitle can't be filtered.
   • DATA_STORE_RESOURCE_PATH: the full resource path ofthe data store whose documents should be boosted by this control. Theformat of the full resource path isprojects/PROJECT_NUMBER/locations/LOCATION_ID/collections/default_collection/dataStores/DATA_STORE_ID.This data store must be attached to the engine specified in the request.

3. Attach the control to the app's serving config using theengines.servingConfigs.patch method.

   curl-XPATCH\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1alpha/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search?update_mask=boost_control_ids"\-d'{ "boostControlIds": ["BOOST_ID_1", "BOOST_ID_2"]}'

   ReplaceBOOST_ID_N with the control IDs that youcreated in the previous step.

Console

1. In the Google Cloud console, go to theAI Applications page.

   AI Applications

2. Select the app for which you want to create the filter control.

3. On your app's overview page, make sure you are on theSystem overview tab.

4. In theSignalstage, click theFilter tile.

5. ClickCreate control.

6. In theCreate control pane, do the following:

   1. ForName Your Control, enter a name for your filter control and clickContinue.

   2. ForRule Scope & Impact, set the following:

      1. Select a data store from the list that you want to attach this filter control to. If you want the action to be applied to multiple data stores, create a control for each data store.

      2. ForFilter, tell the rule which specific items to look for. You can combine search terms usingAND,OR,NOT, and group terms with(). For exact phrases, use quotes"". An example:category: "electronics" AND price < 500, status: "open" AND priority:"P1".

         To understand how to write filter expressions, seeFilter expression syntax andExamples of filter expressions.

      3. ClickContinue.

   3. ForOptional: When This Rule Activates, define the actions that you want to trigger with this control. If no conditions are configured, the control is always in effect:

      1. AddPartial match query terms. The control takes effect when thesequery terms match partially.

      2. AddExact match query terms. The control takes effect when these queryterms match exactly.

      3. To add an active time range, clickAdd time range and setStart time 1 andEnd time 1. This defines the window when thecondition is active. You can add a maximum of 10 time ranges.

      4. ClickContinue.

   4. If you want to apply this control as soon as it's created, forAdditional settings, turn onPublish this control immediately and clickContinue

7. ClickSubmit.

REST

1. Find your app ID. If you already have your app ID, skip to the next step.

   1. In the Google Cloud console, go to theAI Applications page.

      Go to Apps

   2. On theApps page, find the name of your app and get the app's ID fromtheID column.

2. Run the following curl commands to create your controls.

   curl-XPOST\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/controls?controlId=CONTROL_ID"\-d'{"displayName": "DISPLAY_NAME","solutionType": "SOLUTION_TYPE_SEARCH","useCases": ["USE_CASE"],"conditions": {  "queryTerms": [    {      "value": "VALUE",      "fullMatch":FULL_MATCH    }  ],  "activeTimeRange": [    {      "startTime": "START_TIMESTAMP",      "endTime": "END_TIMESTAMP"    }  ]},"filterAction": {  "filter": "FILTER" }}'

   Replace the following:

   • PROJECT_ID: the number or ID of your Google Cloud project.
   • APP_ID: the ID of the Vertex AI Search app.
   • CONTROL_ID: a unique identifier for the control.The ID can contain [1-63] characters that can be letters, digits, hyphens,and underscores.
   • DISPLAY_NAME: the human-readable name for the control.Google recommends that this name provide an indication of when or why touse the control. Must be a UTF-8 encoded string with length [1,128].
   • USE_CASE: must be eitherSEARCH_USE_CASE_SEARCH orSEARCH_USE_CASE_BROWSE. IfSEARCH_USE_CASE_BROWSE is specified,thenCondition.queryTerms can't be used in the condition.
   • CONDITION: an optional field that defines when thecontrol should be applied. Contains the following fields:
     • VALUE: the specific query value to matchagainst. It's a lowercase UTF-8 string with length[1, 5000]. IfFULL_MATCH_1 istrue, this field can have atmost three space-separated terms.
     • FULL_MATCH: a boolean that indicates whetherthe search query needs to exactly match the query term. When set totrue, it requiresSearchRequest.query to completely match thequeryTerm.value. When set tofalse, it requiresSearchRequest.query to containqueryTerm.value as a substring.
     • START_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the start of a time range.
     • END_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the end of a time range.

   • FILTER: a string specifying requirements that mustbe met by the document. If the document matches all the requirements, thedocument is returned in the results. Otherwise the document is not in theresults.

     For the filtering syntax, seeFilter expression syntax.For more information, seefilterAction.Note: The document fieldtitle can't be filtered.

3. Attach the control to the app's serving config using theengines.servingConfigs.patch method.

   curl-XPATCH\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1alpha/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search?update_mask=filter_control_ids"\-d'{  "filterControlIds": ["FILTER_ID_1", "FILTER_ID_2"]}'

   ReplaceFILTER_ID_N with the control IDs that youcreated in the previous step.

Console

1. In the Google Cloud console, go to theAI Applications page.

   AI Applications

2. Select the app for which you want to create the synonyms control.

3. On your app's overview page, make sure you are on theSystem overview tab.

4. In thePreparestage, click theSynonyms tile.

5. ClickCreate control.

6. In theCreate control pane, do the following:

   1. ForName Your Control, enter a name for your synonyms control and clickContinue.

   2. ForRule Scope & Impact:

      1. Enter the synonyms you want to have considered in the control. Forexample, entercats followed by a return (not comma), thenfeline.

      2. When you are finished entering synonyms, clickContinue.

   3. ForOptional: When This Rule Activates, define the actions that you want to trigger with this control. If no conditions are configured, the control is always in effect:

      1. To add an active time range, clickAdd time range and setStart time 1 andEnd time 1. This defines the window when thecondition is active. You can add a maximum of 10 time ranges.

      2. ClickContinue.

   4. If you want to apply this control as soon as it's created, forAdditional settings, turn onPublish this control immediately and clickContinue

7. ClickSubmit.

REST

1. Run the following curl commands to create your controls.

   curl-XPOST\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/controls?controlId=CONTROL_ID"\-d'{"displayName": "DISPLAY_NAME","solutionType": "SOLUTION_TYPE_SEARCH","useCases": ["USE_CASE"],"conditions": {  "queryTerms": [    {      "value": "VALUE",      "fullMatch":FULL_MATCH    }  ],  "activeTimeRange": [    {      "startTime": "START_TIMESTAMP",      "endTime": "END_TIMESTAMP"    }  ]},"synonymsAction": {  "synonyms": ["SYNONYMS_1","SYNONYMS_2"] }}'

   Replace the following:

   • PROJECT_ID: the number or ID of your Google Cloud project.
   • APP_ID: the ID of the Vertex AI Search app.
   • CONTROL_ID: a unique identifier for the control.The ID can contain [1-63] characters that can be letters, digits, hyphens,and underscores.
   • DISPLAY_NAME: the human-readable name for the control.Google recommends that this name provide an indication of when or why touse the control. Must be a UTF-8 encoded string with length [1,128].
   • USE_CASE: must be eitherSEARCH_USE_CASE_SEARCH orSEARCH_USE_CASE_BROWSE. IfSEARCH_USE_CASE_BROWSE is specified,thenCondition.queryTerms can't be used in the condition.
   • CONDITION: an optional field that defines when thecontrol should be applied. Contains the following fields:
     • VALUE: the specific query value to matchagainst. It's a lowercase UTF-8 string with length[1, 5000]. IfFULL_MATCH_1 istrue, this field can have atmost three space-separated terms.
     • FULL_MATCH: a boolean that indicates whetherthe search query needs to exactly match the query term. When set totrue, it requiresSearchRequest.query to completely match thequeryTerm.value. When set tofalse, it requiresSearchRequest.query to containqueryTerm.value as a substring.
     • START_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the start of a time range.
     • END_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the end of a time range.
   • SYNONYMS_N: a list of strings that are associatedwith each other, making it more likely for each to show similar results.While it's more likely that you get similar results, when yousearch for each of the synonym entries, you might not receive all therelevant results for all the associated synonyms.You must specify at least two synonyms and you can specify up to 100synonyms. Each synonym must be UTF-8 encoded and in lowercase. No duplicatestrings are allowed. For example, you can add "pixel", "android phone", and"google phone" as synonyms.For more information, seesynonymsAction.

2. Attach the control to the app's serving config using theengines.servingConfigs.patch method.

   curl-XPATCH\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1alpha/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search?update_mask=synonyms_control_ids"\-d'{  "synonymsControlIds": ["SYNONYMS_ID_1", "SYNONYMS_ID_2"]}'

   ReplaceSYNONYMS_ID_N with the control IDs that youcreated in the previous step.

Console

1. In the Google Cloud console, go to theAI Applications page.

   AI Applications

2. Select the app for which you want to create the filter control.

3. On your app's overview page, make sure you are on theSystem overview tab.

4. In theSignalstage, click thePromote tile.

5. ClickCreate control.

6. In theCreate control pane, do the following:

   1. ForName Your Control, enter a name for your filter control and clickContinue.

   2. ForRule Scope & Impact, set the following:

      1. Select a data store from the list that you want to attach this filter control to. If you want the action to be applied to multiple data stores, create a control for each data store.

      2. Enter thePromote title, such asView latest video.

      3. Enter thePromote URL, such as the location of the video.

      4. Enter thePromote image URL, such as a thumbnail or screenshot.

      5. Enter a briefPromote description, such as what the video is about. The maximum is 250 characters.

   3. ForOptional: When This Rule Activates, define the actions that you want to trigger with this control. If no conditions are configured, the control is always in effect:

      1. AddExact match query terms. The control takes effect when these queryterms match exactly.

      2. To add an active time range, clickAdd time range and setStart time 1 andEnd time 1. This defines the window when thecondition is active. You can add a maximum of 10 time ranges.

      3. ClickContinue.

7. ClickSubmit.

REST

1. Run the following curl commands to create your controls.

   curl-XPOST\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/controls?controlId=CONTROL_ID"\-d'{"displayName": "DISPLAY_NAME","solutionType": "SOLUTION_TYPE_SEARCH","useCases": ["USE_CASE"],"conditions": {  "queryTerms": [    {      "value": "VALUE",      "fullMatch": true    }  ],  "activeTimeRange": [    {      "startTime": "START_TIMESTAMP",      "endTime": "END_TIMESTAMP"    }  ],  "queryRegex": "VALUE_REGEX"},"promoteAction": {  "dataStore": "DATA_STORE_RESOURCE_PATH",  "searchLinkPromotion": {     "document": "DOCUMENT_RESOURCE_PATH",     "title": "TITLE",     "uri": "URI",     "description": "DESCRIPTION",     "enabled":ENABLED_TRUE|FALSE,  } }}'

   Replace the following:

   • PROJECT_ID: the number or ID of your Google Cloud project.
   • APP_ID: the ID of the Vertex AI Search app.
   • CONTROL_ID: a unique identifier for the control.The ID can contain [1-63] characters that can be letters, digits, hyphens,and underscores.
   • DISPLAY_NAME: the human-readable name for the control.Google recommends that this name provide an indication of when or why touse the control. Must be a UTF-8 encoded string with length [1,128].
   • USE_CASE: must be eitherSEARCH_USE_CASE_SEARCH orSEARCH_USE_CASE_BROWSE. IfSEARCH_USE_CASE_BROWSE is specified,thenCondition.queryTerms can't be used in the condition.
   • Condition: an optional object that defines when thecontrol should be applied. Contains the following fields:
     • queryTerms: It can't be used with thequeryRegex field.
       • VALUE: the specific query value to matchagainst. It's a lowercase UTF-8 string with length[1, 5000].
     • activeTimeRange:
       • START_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the start of a time range.
       • END_TIMESTAMP: a timestamp in RFC 3339 UTC"Zulu" format to indicate the end of a time range.
     • queryRegex: only available for data stores withbasic website search. This field can't be used with thequeryTermsfield.
       • VALUE_REGEX: a regular expression to matchthe query against.
   • DATA_STORE_RESOURCE_PATH: the full resource path ofthe data store whose search results contain the promoted URL. Theformat of the full resource path isprojects/PROJECT_NUMBER/locations/LOCATION_ID/collections/default_collection/dataStores/DATA_STORE_ID.This data store must be attached to the engine specified in the request.
   • DOCUMENT_RESOURCE_PATH: a field to specify the document resource path ofthe document to be promoted:
     • For search data stores with structured and unstructured data, you mustprovide either the document resource path in theDOCUMENT_RESOURCE_PATH field, the URI in theURI field, or both. The format of the fullresource path isprojects/PROJECT_NUMBER/locations/LOCATION_ID/collections/default_collection/dataStores/DATA_STORE_ID/branches/0/documents/DOCUMENT_ID.
     • For website data stores, this field must be unset and set the URI fieldinstead.
   • TITLE: a required field to specify the titleof the document or the web page to be promoted. This title is displayed inthe search result.
   • URI: a required field to specify the URI link wherethe search result leads the user. This URI need not be included in thedata store.
     • For search data stores with structured and unstructured data, you mustprovide either the document resource path in theDOCUMENT_RESOURCE_PATH field, the URI in theURI field, or both.
     • For website data stores, this is a requiredfield and you must set it.
   • DESCRIPTION: an optional field to describe thedocument or web page to be promoted, which is displayed in the searchresult.
   • ENABLED_TRUE|FALSE: an optional boolean field toindicate whether the promote control is turned on and attached to the app.This field is applicable to website data stores withbasic website search only.When you set this field tofalse, the promote serving control is turnedoff and for the control to take effect, you must update the control byenabling it, as explained in the next step.For more information, seepromoteAction.

   Response

   You should receive a JSON response similar to the following:

   { "name": "projects/PROJECT_NUMBER/locations/global/collections/default_collection/engines/APP_ID/controls/PROMOTE_CONTROL_ID", "displayName": "PROMOTE_CONTROL_NAME", "solutionType": "SOLUTION_TYPE_SEARCH", "conditions": [   {     "queryTerms": [       {         "value": "VALUE",         "fullMatch": true       }     ]   } ], "useCases": [   "SEARCH_USE_CASE_SEARCH" ], "promoteAction": {   "dataStore": "projects/PROJECT_NUMBER/locations/global/collections/default_collection/dataStores/DATA_STORE_ID",   "searchLinkPromotion": {     "title": "URI_TITLE",     "uri": "URI",     "description": "URI_DESCRIPTION",     "enabled":ENABLED_TRUE|FALSE  } }}

2. For all search apps except for basic website search, attach the controlto the app's serving config using theengines.servingConfigs.patch method. The order in which thepromoteControlIds are attached in the following request is the order inwhich the promoted results are returned.

   curl-XPATCH\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1alpha/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search?update_mask=promote_control_ids"\-d'{  "promoteControlIds": ["PROMOTE_ID_1", "PROMOTE_ID_2"]}'

   ReplacePROMOTE_ID_N with the control IDs that youcreated in the previous step.

3. Optional: For basic website search, you need not attach the control to theapp's serving config. However, for basic website search you can turn apromote control on or off after the control is created,call theengines.control.patch method.

   curl-XPATCH\-H"Authorization: Bearer$(gcloudauthprint-access-token)"\-H"Content-Type: application/json"\-H"X-Goog-User-Project:PROJECT_ID"\"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/controls/CONTROL_ID?updateMask=promoteAction.searchLinkPromotion.enabled"\-d'{"promoteAction": {  "searchLinkPromotion": {     "enabled":ENABLED_TRUE|FALSE,  }}}'

Example

When you send a search request to the app with a query that matches the queryor query regular expression specified for the promote control, the promoted link appears inthe response.

For example, suppose that you create a promote control with the followingconfiguration in a data store with basic website search:

{ "conditions": [   {     "queryTerms": [       {         "value": "artificial intelligence",         "fullMatch": true       }     ]   } ]" ... promoteAction": {  "dataStore": "https://discoveryengine.googleapis.com/v1alpha/projects/123456/locations/us/collections/default_collection/dataStores/basic-website-data-store" \  "searchLinkPromotion": {    "title": "What is AI?",    "uri": "https://cloud.google.com/learn/what-is-artificial-intelligence",    "description": "Explain what is AI"    "enabled": true  } }}

Then, you send the followingsearch request:

curl -X POST -H "Authorization: Bearer $(gcloud auth print-access-token)" \  -H "Content-Type: application/json" \  "https://discoveryengine.googleapis.com/v1alpha/projects/123456/locations/us/collections/default_collection/engines/basic-website-app/servingConfigs/default_search:search" \  -d '{"query": "artificial intelligence"}'

You should receive a JSON response similar to the following truncated response.The response contains thesearchLinkPromotions field that contains thepromoted link.

{ "results": [...],  "totalSize": 3,  "attributionToken": "_gHw_QoMCMSbhboGELuI1qwCEiQ2NzQwYmYzYi0wMDAwLTJmYTctYTk1OC0yNDA1ODg4MzZmYjgiB0dFTkVSSUMqvAGrxIotzua1L5neqC_n7YgtxPzLMIOymiK0kq4wxPi8MPn2sy3LmrQw6d3EMNSynRWc1rctnN3YMOuCsS3ogrEto4CXIsLwnhX89rMtkKS0MJbeqC-jibMtkPeyMMTGsTCZ3dgw5O2ILa7Eii2NpLQw5t3EMN6PmiKOvp0VwfzLMICymiKq-LMt0ea1L634sy3Fy_MXtreMLbeSrjDHxrEwzpq0MMH4vDCgibMtn9a3LZSSxTCOkckw24-aIjAB",  "guidedSearchResult": {},  "summary": {},  "searchLinkPromotions": [    {      "title": "What is AI?",      "uri": "https://cloud.google.com/learn/what-is-artificial-intelligence",      "description": "Explain what is AI"    }  ]}