Milos Djurdjevic
marked this post as
complete
We have added the support for Google Trends explore page.
You can view the documentation at: https://serpapi.com/google-trends-api
J
Joe Barnett
Here is what would be most helpful to us:
Settings:
- Time range (e.g. Last 4 hours)
- Location (e.g. United States)
- Language (e.g. English - US)
- Keywords (we realize these will likely have to be limited to 5 per request - we want to normalize across a larger number though, but we can do that on our side)
Data:
What is provided in multitimelie.csv (as stated below) is useful for the baseline. Related queries per keyword is also very helpful.
- Time
- Keyword interest (out of 100)
Thanks so much - this would be extremely useful for us.
Illia Zub
marked this post as
planned
We stopped implementing Google Trends API because now we improve the engines we already support. We will re-evaluate this feature request in the future.
J
Jeff Schneider
Illia Zub: clarify please; you killed this?
Illia Zub
Jeff Schneider: We haven't worked on Google Trends API since April. We'll update the status once someone from our engineering team will continue to work on this feature.
J
Jeff Schneider
We're doing some planning on our end and really need a delivery date on this feature.
Illia Zub
Jeff Schneider: What data do you want to be extracted from Google Trends? This information will help us to reduce the scope.
J
Jeff Schneider
Illia Zub: Yes. Use this query as an example: https://trends.google.com/trends/explore?geo=US&q=demandbase,6sense Then, download the .CSV and look at it. The data is a time-series over some duration for one ore more terms. We want the contents of the CSV but as a standard API call (http/json). Our filter criteria will always be: "United States", "Past 12 Months", "All Categories", "Web Search".
Illia Zub
Jeff Schneider: Thank you! So you want only the
multiTimeline.csv
?J
Jeff Schneider
Illia Zub: Yes, just convert the .csv to as a standard api format. That's it.
I
Itai Dagan
Hi Elizabeth Oster :)
there is an ETA on this feature?
thanks!
Elizabeth Oster
Itai Dagan: Not yet, we have a working version of the API at this point so we're in the review process.
Milos Djurdjevic
marked this post as
in progress
J
JS
Hi Elizabeth, any ETA on this feature?
Elizabeth Oster
JS: I've bumped the priority of this in our backlog. We still have other features that we are working on at the moment. But we should begin development on this soon.
J
JS
any idea when will this be implemented?
J
JS
make sure you support all dates: now%201-H, now%204-H, now%201-d, etc in adition to date ranges
related queries: both rising and top
and average for each keyword
it should support up to 5 keywords
Julien Khaleghy
marked this post as
planned
Load More
→