> 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/meta-tags.md).

# Meta Tags

View meta tags found on your site.

The Meta Tags section displays meta tags and their values that were found on your site.

## Use Cases

* **Monitor tags to ensure they only provide information you wish to be shared.** Meta tags can often contain information about the platform or framework running on the website, email addresses, and off-site accounts.

## Detection

Meta tags are scraped during the crawling process.

## Risk

No risk is associated with Meta Tags.

## Reports

* [Overview](https://app.halosecurity.com/user/security/website/meta/): Displays common meta tags and occurrences where they were found.
* [Summary](https://app.halosecurity.com/user/security/website/meta/summary): Displays meta tags that were found and their number of occurrences and targets
* [List](https://app.halosecurity.com/user/security/website/meta/list): Lists meta tags and their values per target.
* [Missing](https://app.halosecurity.com/user/security/website/meta/missing): Search for missing meta tags or values.
* [Changes](https://app.halosecurity.com/user/security/website/meta/changes): See changes to meta tags between current and previous scans.


---

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