Botscope
Botscope on your stack
What the integration looks like where you work, including what it cannot do on platforms that do not allow it.
- 2,114
- bots and agents catalogued
- 865
- named operators
- 14
- categories
Platforms
-
Botscope for WordPress
Classify every bot and AI agent reaching your WordPress site from the origin, with no DNS change and no dependence on a script running in the visitor’s browser.
Read → -
Botscope for Cloudflare
Two ways to run Botscope on a Cloudflare site: a Worker in your own zone with no DNS change, or the edge with Cloudflare kept for DNS. What each one sees.
Read → -
Botscope for Shopify
Our Shopify app shows bots and AI agents on your store. Blocking them takes the store domain on Cloudflare with our Worker in front. What each path covers.
Read → -
Botscope for Laravel
Classify requests in middleware, before your routes run. Every decision carries a reason code you can log, test against, and explain to somebody later.
Read →
Roles
-
Botscope for SEO teams
See which crawlers read which pages, how often, and what came back. Per-page crawl and referral figures, without a tag that automated clients never execute.
Read → -
Botscope for publishers
Separate the AI agents that send readers back from the ones that only collect, then set a policy per operator and enforce the same rule you publish.
Read →