VerisAI crawler identity declaration

Generic technical requests use this exact HTTP User-Agent:

VerisAI-IndexScanner/1.0 (+https://verisai.eu/crawler; AI visibility index scan; support@verisai.eu)

This identity is used for the public homepage, HTTP-to-HTTPS redirect check, robots.txt, sitemap, llms.txt, llms-full.txt, and the small set of public AI-discovery files.

• Only publicly reachable website resources are assessed.
• The scanner does not authenticate, submit forms, use credentials, or bypass logins and paywalls.
• It collects technical response data and derived AI-readiness signals. Public-response-derived assessment results may be retained for VerisAI index and monitoring operations.
• Source IP addresses may vary during local operation; they are not a stable public allow-list or identity proof.
• This is a transparency declaration on VerisAI's HTTPS domain, not a CA-issued, TLS-client, or cryptographic certificate.

One part of the assessment measures how a website treats selected real AI bot identities, such as GPTBot, OAI-SearchBot, Google-Extended, ClaudeBot, PerplexityBot and GrokBot. Those requests retain each bot's official User-Agent so the measurement remains valid.

Blocking one of those bot identities is recorded as that bot being inaccessible. It can also affect the real bot, so it should not be used solely to suppress the VerisAI measurement.

To block VerisAI's generic technical requests, create a WAF or firewall rule that matches the exact User-Agent shown above. This blocks the generic technical portion of the assessment.

For questions, retention requests, or a request to suppress future VerisAI assessments for a domain, email support@verisai.eu with the domain and relevant log timestamp.