Keenable.ai, Inc. crawlers: what each bot does
Keenable.ai, Inc. runs 2 bots that we document: KeenableBot, Keenable-User. They have different jobs (AI search crawler, AI user-triggered fetcher), so a robots.txt rule for one does not apply to the others.
| Bot | Category | robots.txt token | Honors robots.txt? | What blocking does |
|---|---|---|---|---|
| KeenableBot | AI search crawler | KeenableBot | Yes, per Keenable | Per Keenable, disallowing KeenableBot removes your site from those answers. Keenable-User is a separate token for user-initiated requests and needs its own rule. |
| Keenable-User | AI user-triggered fetcher | Keenable-User | Yes, per Keenable | Keenable controls this token separately from KeenableBot: a rule for Keenable-User applies to those user-initiated requests only and does not remove you from the search index. |
Is a request really from Keenable.ai, Inc.?
A user-agent string is only a claim. These are the checks Keenable.ai, Inc. publishes for its bots; where there is none, the user agent alone cannot prove a request is genuine.
- KeenableBot: compare the requesting address with the published IP ranges.
- Keenable-User: compare the requesting address with the published IP ranges.
Paste an address into the crawler IP checker to test it against the lists we can read.
What Keenable.ai, Inc. says about robots.txt
KeenableBot
Keenable says it follows RFC 9309, that a group naming one of its tokens takes precedence over a User-agent: * group, and that each token is controlled separately. It also honors noindex, nofollow and none in the robots meta tag and the X-Robots-Tag header; directives addressed to keenablebot apply to it specifically.
Keenable-User
Keenable says it follows RFC 9309, that a group naming Keenable-User takes precedence over a User-agent: * group and that each token is controlled separately; changes apply after Keenable next fetches your robots.txt.
508 requests from Keenable.ai, Inc. bots on this site in the last 30 days. Bot traffic data