> For the complete documentation index, see [llms.txt](https://whitepaper.werate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.werate.io/the-broken-review-economy/broken-incentives-and-user-experience/terrible-search-experience.md). # Terrible search experience ### 🤔 Imagine this You’ve just landed in a new city. You’re tired, hungry, and want something good for dinner.\ You open Yelp. Then TripAdvisor. Then Google Maps. Maybe even Apple Maps. Suddenly, you’re comparing reviews across four apps with different star ratings, filters and UX.\ Everything is inconsistent, outdated or irrelevant. Some reviews are fake. Some are five years old.\ Some just say: “meh.” ### 🧩 The process of finding a great place is still painful * You juggle **multiple platforms** with no shared logic * Each one has **different rating systems** and filtering tools * You’re forced to interpret **unclear, incomplete or biased** reviews * It’s slow, manual and frustrating — especially on mobile > It takes more time to pick the restaurant than to eat the meal. *** ### 🎯 No sense of personal relevance Traditional search cannot understand * Your taste * Your habits * Your past visits * Your social circle Everyone receives the same results, even though everyone experiences places differently. *** ### 🔒 No trust in results Even when you find a place, you still wonder * Are the reviews real * Are the photos recent * Is the rating inflated * Does the experience match my taste Search without trust is not discovery.\ It is hesitation. *** There is still no unified engine for **fast, trustworthy, real world recommendations** tailored to your behaviour and grounded in authenticity. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://whitepaper.werate.io/the-broken-review-economy/broken-incentives-and-user-experience/terrible-search-experience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.