> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/fr/insights/onsite.md).

# Sur site

Examinez les performances de vos pages et la manière dont les systèmes d'IA interagissent avec votre site.

Onsite est la section Insights dédiée au contenu propriétaire. Elle rassemble les performances des pages, l’activité des robots d’exploration IA et l’historique de publication du contenu, afin que vous puissiez déterminer quelles pages nécessitent une attention particulière.

## Vues Onsite

### Pages

Examinez les performances de recherche traditionnelle et de recherche IA pour chaque page, puis filtrez et sélectionnez les pages à traiter ensuite.

[Voir la documentation de Pages](/docs/fr/insights/onsite/pages.md)

### Agent Analytics

Découvrez quels moteurs d’IA explorent votre site, pourquoi ils consultent votre contenu et quand les assistants IA envoient des visiteurs vers une page.

[Voir la documentation sur Agent Analytics](/docs/fr/insights/onsite/traffic.md)

### Mises à jour du contenu

Suivez les pages publiées ou actualisées via Workflows, Grids, l’API et MCP.

[Voir la documentation sur les mises à jour de contenu](/docs/fr/insights/onsite/content-updates.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/docs/fr/insights/onsite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.