> 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/es/insights/onsite.md).

# En el sitio

Revisa cómo rinden tus páginas y cómo interactúan los sistemas de IA con tu sitio.

Onsite es el área de Insights para contenido propio. Reúne el rendimiento de las páginas, la actividad de rastreo de IA y el historial de publicación de contenido para que puedas decidir qué páginas necesitan atención.

## Vistas de Onsite

### tabla de

Revisa el rendimiento de la búsqueda tradicional y de la búsqueda con IA para cada página, luego filtra y selecciona páginas para el trabajo de seguimiento.

[Ver la documentación de Pages](/docs/es/insights/onsite/pages.md)

### Agent Analytics

Consulta qué motores de IA rastrean tu sitio, por qué acceden a tu contenido y cuándo los asistentes de IA envían visitantes a una página.

[Ver la documentación de Agent Analytics](/docs/es/insights/onsite/traffic.md)

### Actualizaciones de contenido

Haz seguimiento de las páginas publicadas o actualizadas a través de Workflows, Grids, la API y MCP.

[Ver la documentación de Content Updates](/docs/es/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/es/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.