> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/analytics.md). # Measure and improve - [Site analytics](https://gitbook.com/docs/analytics/insights.md): View analytics related to your published documentation’s traffic and usage - [Traffic](https://gitbook.com/docs/analytics/insights/traffic.md): See how many people read your site, which pages they land on, what they search for, and what they think of your content - [AI Assistant](https://gitbook.com/docs/analytics/insights/ai-insights.md): See what your visitors ask GitBook Assistant, how well your content answers them, and where your docs fall short - [Agents & MCP](https://gitbook.com/docs/analytics/insights/agents-and-mcp.md): Track how LLMs, coding agents, and crawlers read your documentation - [Broken links](https://gitbook.com/docs/analytics/broken-links.md): Find the URLs on your published site that return a 404 and fix them with suggested redirects - [Content gaps](https://gitbook.com/docs/analytics/content-gaps.md): Find the questions your docs don’t answer, ranked by severity, and fill them with GitBook Agent - [Guides](https://gitbook.com/docs/analytics/guides.md): Explore guides for measuring and improving your documentation with analytics --- # 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://gitbook.com/docs/analytics.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.