> 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/6-month-organic-decline.md).

# 6-Month Organic Decline

This report shows the URLs on your site that have been in a declining state of organic traffic over the last 6 months.  We map their trajectory via a linear regression of daily traffic, essentially drawing a best fit line over the daily traffic graph.

We then compute the "lost traffic" by comparing the traffic they would have earned with a "flat line" to the traffic they earned with their declining line.  The reason for this is that it effectively combines the steepness of the decline with the magnitude of the decline to approprimate the "biggest losers" and heat maps accordingly.

This view is a simple heatmap chart with the following fields:

* **URL**: the URL in question
* **Lastmod**: the last intervention date with the URL, for reference.
* **Keyword**: the keyword targeted by the URL, if known/applicable.
* **Views**: the number of organic views it has received in the last 6 months.
* **Estimated Loss**: this is the heatmap field, and it's our estimate of the lost traffic compared to a flat traffic graph.  The redder the field, the more the loss.

This is a simpler way to reason about refresh candidates and triage traffic loss.  It fails to take traffic expectations and potential into account, but it's an accurate view of where organic declines are coming from and which URLs are declining.

Here is what it looks like:

<figure><img src="/files/konqkje0UML8sbxDza4H" 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/triage/6-month-organic-decline.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.