> For the complete documentation index, see [llms.txt](https://hitsubscribe.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hitsubscribe.gitbook.io/home/osiris/actionables/refresh-candidates.md).

# Refresh Candidates

This report algorithmically curates URLs that you might want to refresh.  I say *might* because there are various possible countervailing concerns that wouldn't show up in the data (URL isn't relevant to your current positioning, you've actually just updated the URL but not updated the backing data, etc).  So you'll always want to confirm before blindly updating, but the data suggests that you may want to refresh.

Here is what the table shows:

* **URL**: the URL in question.
* **Primary keyword**: the main keyword targeted by the URL.
* **Rank**: the most recent rank of this URL for this keyword, measured within the last week.
* **Last Changed**: the last time you logged an intervention of some kind for this URL.
* **Projected**: the rank our model projects that you should have for this URL.
* **Peak Monthly**: the most traffic logged for this URL in a given month.
* **Last Month**: the amount of traffic the URL has logged in the last 30 days.
* **Potential Gain**: how much traffic we calculate you could gain, based on either the difference between last month and peak or between last month and the traffic our model believes you could earn.
* **Go!**:  (tier-dependent) request a refresh manifest.
* **Status**: (tier dependent) status of your manifest request.

There is also a slider at the top, where you can control which URLs to filter out, depending on how recently they've been edited.  We default this to 6 months, with the idea that if you've intervened with a URL more recently than that (especially newly published), then you might want to give it time to settle into its eventual position before throwing good labor money after changing it.  But you can always throttle that to 0 and see everything.

This screen is sorted and heat-mapped by potential gain.  Meaning, we'll list the URLs in the order of how much traffic potential the refresh has, according to the models and our data.

<figure><img src="/files/t4lwdyztYsGTaKn0VMLc" alt=""><figcaption></figcaption></figure>


---

# 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://hitsubscribe.gitbook.io/home/osiris/actionables/refresh-candidates.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.