> 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/how-does-keyword-staking-priority-work.md).

# How does keyword staking priority work?

 Only one ad (or no ad) is shown per search, and it goes to whoever has the highest stake on a matching
 keyword or phrase. Whoever stakes the most has their ad shown. If you are the highest staker and did
 not check “Move to Top Subscription,” your ad appears at the bottom of the first page. If you are
 the highest staker and did check the box, your ad appears in the third position of the first page. The
 checkbox is simply moving your ad from the bottom to the third position—it does not affect whether
 your ad wins or not. The largest staker always wins. The fee for “Move to Top Subscription” is
 0.033% of your staked amount per day, which adds up to approximately 1% per month.


---

# 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/how-does-keyword-staking-priority-work.md?ask=<question>&goal=<endgoal>
```

`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.