Closed schaferyan closed 3 months ago
I think this is the expected JSON as the HTML returned by Google does contain not that many results. Probably because it's mobile and the new infinite scrolling.
@hartator do you think there might be a way to avoid this behavior from Google? So far it only seems to affect a handful of queries, and retrying with no_cache=true
should be fine as a workaround. But if this becomes more common it will be very inconvenient for some of our customers.
These 2 look valid; it's just Google having more rich results than the usual.
Google is slowly phasing out num
parameter in favor of infinite scrolling otherwise.
A user provided a few examples of searches that only return a few results, though they should return more.
While it's normal to return a varying number of
organic_results
(i.e 8 or 9 instead of 10), especially on the first page, these searches only provide 1 or 2 results.The examples used
num=100
anddevice=mobile
. However, other searches may be affected as well. I was unable to replicate it on my side, even retrying the user's searches many times withno_cache=true
.Intercom | Playground | Search Inspector 1 | Search Inspector 2