Search is one of those features that looks simple from the outside and gets messy fast on the inside. You have a search provider, you have your own database, and you have a front end that just wants results.
On one project the search logic had grown into something that was hard to trust. So I moved it behind a single typed procedure. The front end calls one function, hands it what the user typed, and gets back results in a shape it can count on. All the provider specific detail lives in one place on the server, out of sight.
The win is not only tidiness. When the whole path from the browser to the server is typed, a change on one side shows up as an error on the other before it ever reaches a user. The compiler catches the mismatch instead of your customer catching it.
I like boring, predictable seams like this. One clear entry point, strong types across it, and the awkward complexity tucked behind it. It makes the feature easier to change six months later, which is usually when it actually matters.