One thing with any query parameter API like this is that there's no guaranteed signal when the API has breaking changes.
I'm going to assume that there are hundreds or thousands of products, tools, hobby projects, ect, that direct to Google searches; none of which have any mechanism to know and break gracefully when the API changes. Furthermore, Google is under no obligation to coordinate with anyone who just arbitrarily send queries their way. (I've had a few hobby projects use Google Queries.)
Seems like the most we could really ask is to put some kind of version stamp into the query parameter; and Google could optionally support old parameters or simply return an error. Otherwise, we have to accept that sending browsers to other pages via query parameters is inherently fragile and has a high probability of breaking at any time.
I'm going to assume that there are hundreds or thousands of products, tools, hobby projects, ect, that direct to Google searches; none of which have any mechanism to know and break gracefully when the API changes. Furthermore, Google is under no obligation to coordinate with anyone who just arbitrarily send queries their way. (I've had a few hobby projects use Google Queries.)
Seems like the most we could really ask is to put some kind of version stamp into the query parameter; and Google could optionally support old parameters or simply return an error. Otherwise, we have to accept that sending browsers to other pages via query parameters is inherently fragile and has a high probability of breaking at any time.