For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Media SecurityMalvertising DefenseAPI Reference
Media SecurityMalvertising DefenseAPI Reference
  • Media Security Overview
    • MediaGuard Overview
    • FraudSensor Overview
    • Closing the Loop - MediaGuard and FraudSensor
    • IVT Taxonomy
    • Click Defense Overview
    • Metrics (Media Security)
    • Brand Safety Web Crawler
  • HUMAN Dashboard
    • Understand the HUMAN Dashboard
  • Analysis and Reporting
    • Explore Dashboard (Legacy)
    • Create Custom Data Views
    • Schedule Reports and Alerts
    • Access Transaction Level TLX Reports
  • Integrations
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Identification in your logs (the User-Agent string)
  • What to do if you see GlancelotBot traffic
  • Contact us
Media Security Overview

Brand Safety Web Crawler

Was this page helpful?
Previous

Understand the HUMAN Dashboard

A comprehensive overview of your traffic data.
Next
Built with

GlancelotBot is a specialized content retrieval system developed and operated by HUMAN. It serves as a vital component in our mission to protect digital advertising spend and maintain a clean, secure ecosystem.

  • Purpose: The primary function of GlancelotBot is to safely and efficiently retrieve and process the content of web pages. This data is critical for providing Brand Safety, Suitability, and Contextual Verification signals to ensure that advertising campaigns are placed only within appropriate and secure environments.
  • Does not cause IVT: GlancelotBot does not cause invalid traffic (IVT) for ads. It does not cause ads to be served.

Identification in your logs (the User-Agent string)

You are seeing this specific traffic because GlancelotBot utilizes a transparent and self-identifying User-Agent string: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36 GlancelotBot/0.8.0 (+https://docs.humansecurity.com/advertising/brand-safety-web-crawler)

The exact string may vary over time. For example, the version number after GlancelotBot/ will increase. To reliably locate GlancelotBot activity, search for the substring "GlancelotBot/" in the user agent and base any allow or blocking rules on it.

What to do if you see GlancelotBot traffic

GlancelotBot is programmed to be respectful and efficient, crawling at measured rates to minimize impact on your server performance. However, if you wish to exclude GlancelotBot from accessing certain parts of or your entire website, you may use the standard robots.txt protocol. Please refer to the bot by its specific name:

User-agent: GlancelotBot
Disallow: /

Contact us

If you have any questions regarding GlancelotBot’s traffic or its behavior, or require technical assistance, contact our technical team at support@humansecurity.com.