> For the complete documentation index, see [llms.txt](https://docs.presearch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.presearch.io/keyword-staking/keywords/why-doesnt-my-ad-show-when-someone-searches-a-longer-phrase-that-includes-my-staked-keyword.md). # Why doesn’t my ad show when someone searches a longer phrase that includes my staked keyword? If you were to stake the phrase "actually private", your ad will only appear if a user searches those exact two words in that exact order and at the beginning of their search. So, if someone searches "a search engine that is actually private", your ad won’t show because "actually private" is in the middle, not the start. Presearch only triggers ads when the first word of the search matches your staked keyword or phrase. To reach more searches, try also staking related short-tail words like "private", "search engine", or the full long-tail phrase users are more likely to type. --- # 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://docs.presearch.io/keyword-staking/keywords/why-doesnt-my-ad-show-when-someone-searches-a-longer-phrase-that-includes-my-staked-keyword.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.