search

serpapi / public-roadmap

Public Roadmap for SerpApi, LLC (https://serpapi.com)
55 stars 5 forks source link

Add `ved_type` and `ved_type_decoded` key to the JSON response #668

Open ilyazub opened 1 year ago

ilyazub commented 1 year ago

@zyc9012 have created and introduced ved_decoder in a fix for https://github.com/serpapi/public-roadmap/issues/666. (Thank you!)

Currently, ved_decoder is used only internally in SerpApi. @dsottimano has mentioned on Twitter about the need of transparency on the current parsing schema.

SerpApi can add ved_type and ved_type_decoded keys for all parsed elements. It'll be simpler for our users to double-check if SERP features are detected correctly by SerpApi.

dsottimano commented 1 year ago

Exceptionally well done, congrats to the team. I already see more ads,and specialties like buying guides and 'immersive products' source query: /search.json?engine=google&q=best+laptops&location=Austin%2C+Texas%2C+United+States&google_domain=google.com&gl=us&hl=en&num=100&device=mobile&no_cache=true&google_domain=google.com

dsojevic commented 5 days ago

The demand for the ved key (and associated decoded key) doesn't appear to be there; have moved this to freezer.

I would also argue that we may want to consider this a wontfix as the decoded parameter largely gives data we provide via other keys and, as such, is unlikely to be of much value to an overwhelming majority of consumers.