> 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/insights/onsite.md). # Onsite Review how your pages perform and how AI systems interact with your site. Onsite is the Insights area for owned content. It brings together page performance, AI crawler activity, and content publishing history so you can decide which pages need attention. ## Onsite views ### Pages Review traditional search and AI search performance for each page, then filter and select pages for follow-up work. [View Pages documentation](/insights/onsite/pages.md) ### Agent Analytics See which AI engines crawl your site, why they access your content, and when AI assistants send visitors to a page. [View Agent Analytics documentation](/insights/onsite/traffic.md) ### Content Updates Track pages published or refreshed through Workflows, Grids, the API, and MCP. [View Content Updates documentation](/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/insights/onsite.md?ask=&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.