Use case / Publishers
Publishers & content
Publishers need discovery and pay attention to scraping. Volance separates the crawlers you want from the ones you do not, with evidence behind each call.
The problem
Publishing traffic mixes real readers, search and social crawlers you want, AI and archival crawlers you may not, and scrapers copying content or bypassing paywalls. Blocking by user-agent alone is trivially spoofed, and blanket measures break discovery.
How Volance helps
Score on-site sessions for behavioural signals and combine them with disclosure evidence where a crawler identifies itself. Verified agents can be allowed by name, unknown automation can be flagged or blocked by your policy, and real readers are unlikely to be disturbed because there is no visible challenge.
What you see
- Reader-versus-crawler splits by section and path.
- Sessions where a signed agent verified, so legitimate crawlers are visible and allowed.
- Named signals behind each flag, ready for legal or platform discussions.
Volance scores a session on human-likeness and returns the evidence. It is not a CAPTCHA and does not prove a human is present; enforcement stays on your server.
Frequently asked
Will Volance block Googlebot and hurt SEO?
No. Verified crawlers can be allowed by policy, and Volance is not a gateway. Search and social crawlers you choose to trust keep working.
Can it help with AI crawlers?
It can distinguish signed agents from unknown automation, so you can allow the crawlers you want and flag or block the ones you do not. The policy is yours.
MAKE THE NEXT REQUEST MAKE SENSE.
Start where
it matters.
One script on your site.
One API call from your server.
Every signal behind the verdict, in your own portal.