> 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/traffic-analytics/ai-percentage-over-time.md).

# AI Percentage Over Time

In this report you can see the percentage of your site's traffic that is coming from AI sources, where AI sources are known, established answer engine sites.  Specifically, this is a week over week look at the amount of traffic coming from these sources divided by the site's total traffic in that week.

For most Osiris clients, there's a bit of noise to this graph, but it tends to be on a somewhat polynomial growth path over the last couple of years. &#x20;

You can only filter this report by date range.

<figure><img src="/files/5WFkvLumADM8S82HspwF" 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/traffic-analytics/ai-percentage-over-time.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.
