> For the complete documentation index, see [llms.txt](https://nextsearch.gitbook.io/next-proposal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nextsearch.gitbook.io/next-proposal/whats-wrong-with-web-search/poor-searcher-productivity.md). # Poor Searcher Productivity Search engines lack a number of simple and intuitive tools that could significantly improve a searcher's productivity. Some examples include: * Relatively limited qualifier options for refining queries (and the limited options are usually not in a form most users will utilize, e.g. hidden on an invisible advanced search form or using operators). * Inability to filter out or prioritize certain results for specific queries without knowing in advance what should/should not exist. * Inability to share easily one's own research on a topic with others. The depths of this problem become more evident whenever someone is performing research or seeking information regarding a topic that is not part of popular culture or some significant niche. --- # 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://nextsearch.gitbook.io/next-proposal/whats-wrong-with-web-search/poor-searcher-productivity.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.