The people_also_search_for field returns a string value
complete
Mikhail Kavaliou
Hitting API with the parameters:
"search_parameters": {
"engine": "google",
"q": "Panoz Esperante",
"location_requested": "united states",
"location_used": "United States",
"google_domain": "google.com",
"device": "mobile"
}
It returns a string for the people_also_search_for field in the knowledge_graph section, whereas json objects are expected by docs:
Ajay Ramachandran
Now, the links links for this type of
people_also_search_for
are accessible via the
people_also_search_for_links
object.This post was marked as
complete
Ajay Ramachandran
in progress
Illia Zub
Mikhail Kavaliou, In this example, the
People also search for
is displayed as a regular field on the Knowledge Graph. Like knowledge_graph.founders
, knowledge_graph.subsidiaries
, etc.On mobile
, the People also search for
widget is displayed separately from the Knowledge Graph and we extract it to the top-level field inline_people_also_search_for
.Was the
inline_people_also_search_for
existed in the searches like 610799cf1071f48d5476d3df
?Mikhail Kavaliou
Illia Zub: Nope, there is no the field
inline_people_also_search_for
presented in the 610799cf1071f48d5476d3df response.From my observations the
inline_people_also_search_for
field is exposed for tablets, but not for mobile.Justin O'Hara
under review
Ali
Hello Mikhail,
With the same search parameters, I couldn't reproduce this bug:
If you share the search ID of this specific search, that would be a great help.
Mikhail Kavaliou
Ali: Yes, I have the id: "610799cf1071f48d5476d3df". Thank you.
Justin O'Hara
Mikhail Kavaliou: Thanks for the search
id
I have reported this internally. The search I just conducted much like Ali did not provide me with this incorrect data field:Regardless, our engineers are going to take a look at this.