Would be awesome if searching for a term followed by a language (e.G. "ice cream spanish") already gave you a translation widget for that term like Google and Bing do it since the user is fairly possible looking for a translation of mentioned term.
While this "only" saves you 9 characters, it makes the translation widget easier to find (in fact I had to search this forum for a couple of minutes to figure out there was a search widget, no other major search engine requires a keyword for it to appear).
For queries where the user searches for the term followed by a languages non-english version e.g. "pfannkuchen niederländisch" ("niederländisch" is the German way of saying "dutch"):
The users native languages could be deducted from the Accept-Language, header as most browsers include all system languages enabled in the Accept-Language header (e.g having German set as a secondary and UK English as a primary language or keyboard in the OS creates something like Accept-Language: de, en-gb;q=0.8, en;q=0.7) and it is likely that the language the user is using to describe the desired language is of their native languages.
When receiving above given header, we could query the search term for the names of all languages localized in the languages the client gave us (-> the search term would be tested for containing the word "dutch" and "niederländisch" among all other languages localized versions and if one of these pops up, a translation widget appears).
Note that this might not work on "hardened" browsers that omit fallback languages for fingerprinting protection. I think for these just using their Kagi interface language as a default would be fine tho as these browsers already warn their users to expect such drawbacks when using them in "hardened"/incognito mode.
Google and Bing for example already implement something like this, only without something like the Accept-Language trick it appears(?)
Google:
Bing:
