> 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/triage/possibly-wounded-urls.md).

# Possibly Wounded URLs

This report shows you URLs that have had steady traffic over a 2 month baseline, but then dropped to 0 over a configurable number of days (5, by default).  The idea of this to identify URLs that might be blockd, unpublished or generally in bad technical shape somehow.  It's not normal for a URL to go from "regularly earning traffic" straight to 0.

This is a surprisingly difficult universal query to write, simply because some sites have way more day-to-day variance than others, and some URLs even more than the sites.  In other words, there may be perfectly healthy URLs that stop getting organic traffic for 4 days, and then it simply picks up again normally.  

So what you're looking at here you should think of as "a list of URLs you might want to quickly check on" rather than URLs for which something is definitely wrong.


---

# 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/triage/possibly-wounded-urls.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.