> 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/steep-dropoffs.md).

# Steep Dropoffs

This report is designed to surface URLs that have lost a lot, but not all, of their traffic.  In contrast to the [Possibly Wounded URLs report](/home/osiris/triage/possibly-wounded-urls.md), it's unlikely the URL is, say, unpublished, if it's still earning at least some traffic.  

The way this report works is that we compute traffic in the last 7 days, and compare it to the weekly average for the 4 weeks prior to the 7 day window, looking for more than a 50% drop.  Put (over) simply, we're looking for URLs that have lost at least 50% of their normal traffic for more than just a few days.

This doesn't necessarily mean there is anything wrong with the URL, per se.  It could be temporary, or it could be normal flucuations.  But a drop like this might mean that the URL has lost rank for a particularly important keyword or set of keywords, and that can be good to know.


---

# 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/steep-dropoffs.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.