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

# Pages

The Pages section reports all pages that were seen by the scanner during is crawl process.

## Use Cases

* **Verify crawling coverage.** You can use this section to make sure the crawler can discover key parts of your website.

## Detection

From the base URL of the website, the crawler attempts to find links and traverse them up to a depth of 100 directories (or 10,000 total pages). Any pages that are discovered will be listed in this section.

## Risk

No risk is associated with Pages.

## Reports

* [Overview](https://app.halosecurity.com/user/security/website/sitemap/): Shows response size, speed, and response code for sitemap elements.
* [Summary](https://app.halosecurity.com/user/security/website/sitemap/summary): Displays the number of pages found per target with the ability to view them.
* [List](https://app.halosecurity.com/user/security/website/sitemap/list): List of all page elements per target.


---

# 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://docs.halosecurity.com/docs/platform/websites/pages.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.