Hacker News new | past | comments | ask | show | jobs | submit login
Show HN: I built an API for Google autocomplete (keywordquill.com)
41 points by mjhcodes 8 months ago | hide | past | favorite | 23 comments



That certainly helps with not having to deal with the undocumented (?) Google API yourself. The following is what chrome would use to perform autocomplete searches:

curl 'https://google.com/complete/search?client=chrome&hl=en&gl=en...'


I built a little game based on a similar idea, where you enter a search query and then try and guess what the autocompletes will be. It's still very beta but feel free to try it out. Feedback welcome.

https://autocomplete-guess.blaise.gg/

I was able to get completions by just querying this endpoint:

https://www.google.com/complete/search?q=$QUERY_GOES_HERE&cl...


Love it for it's simplicity.


Nice work, but I am surprised that you would charge people money to use this, and I imagine that it will be promptly shut down by Google.


Yes, this. Also, why pay when you can do what they did and get the autocompletions for free?


SEOs and digital marketing departments needs this kind of services, especially for a huge number of this queries. Getting this kind of data for “free” is not so straightforward when Google detects that.


Isn't Google more likely to detect that this service is consuming their API and then blocking them?


That's the entire value of the API. They deal with the proxies and reverse engineering for you.


I built https://wwwww.today/ as a vanity project last year. It's in the same space but is almost completely pointless.

Pro tip: clicking through to individual results is probably the most interesting thing you can do. At some point I'll look at the aggregated data collected over the whole period. I'm curious to see which were the most fleeting autocomplete results.


Aren't these suggestions based on the user and their location? If so, how does this project account for that?


What's it for? Also it doesn't give the same results as using google.com in the browser.


Awesome, many things this could be useful for. How often does it update?


Undoubtedly useful, but I'd be shocked if this wasn't violating Google's ToS and I can't imagine building something important using this.


i had the same reaction, but i looked to see what google's tos was for things like this and i found https://serpapi.com/ , which apparently has been around for 5 years and also offers paid services for scraping google search. if their homepage is to be believed, there are large companies using their service. i'm very surprised that google hasn't taken steps to block them.


Note that part of SerpApi's product seems to be indemnification from liability. On their pricing page, the Developer plan specifies "No Legal US Shield" and the Production plan specifies "Legal US Shield".

From their FAQ:

> What are scraper legal protections?

> SerpApi, LLC assumes scraping and parsing liabilities for both domestic and foreign companies unless your usage is otherwise illegal.


if i were evaluating serpapi, my concern wouldn't be my own legal liability. i'd be worried about serpapi getting blocked one day and my own application suffering as a result


There's many services like this that want/need access to Google search results. Another is ahrefs which is geared towards SEO.


Interesting. I haven't heard of SerpApi but that is indeed surprising.


I was also serprised


You can use Google without agreeing to their ToS, so technically it shouldn't matter, but practically, if their lawyers come knocking, that's a different story.


I'm not sure what the connection is here. I wouldn't be so worried about violating the ToS myself if I was using the service. I'd be worried about Keyword Quill violating the ToS, getting shut down, and a service I was depending on disappearing.


I wouldn’t be surprised if actually it’s just a ChatGPT prompt “What google search autocomplete would return for this query:”

seems easier than reverse engineering/scraping google search autocomplete


Definitely easier but will be not be factually correct.

Will be ok if you just want some ideas but not if you’re tracking keywords performance in Google




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: