> 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/retirement-candidates.md).
# Retirement Candidates
Retirement candidates is a list of URLs that you could consider retiring, at least from an SEO perspective. (Meaning, if you have other uses for the content, the model can't speak to that, so emphasis on the "candidate.")
This view is a table that has the following columns:
* URL: the URL you might consider retiring.
* Keyword: the target keyword, if any.
* Potential: the organic traffic potential our model calculates based for the primary keyword to your site.
* Backlinks: the number of backlinks we've found to that URL in the wild.
* Total Views: the number of total views in the last number of days you specify withthe slider.
* Last Visit: the last date we have a recorded visit to the URL through any medium.
The slider at the top lets you set the number of days without a visit before we show it in this list.
Retiring URLs isn't the highest priority thing you can do, but it's worth occasionally getting rid of (or at least deindexing) things that aren't doing anything for you, to keep crawl budget low and your site clean. This view is meant to surface the best candidates, and in our experience, it will often show URLs that you didn't know were live or want their, like clientsite.com/home-2
The total visits and number of backlinks, as well as the keyword metrics, are there to help you make a decision. If you have a URL that has earned no views but has hundreds of backlinks, for instance, you might want to leave it alone for the SEO value of those backlinks.
---
# 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/retirement-candidates.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.