01 · Operator
Who operates Keenable-User
- Company
- Keenable.ai, Inc.
- Type
- AI assistant fetcher
- Official docs
- app.keenable.ai
02 · Behavior
What Keenable-User does
Keenable-User handles user-initiated requests, such as fetching one page someone asked for. It does not crawl the web automatically. Keenable publishes it so site owners can spot these requests in logs. It has its own robots.txt token, separate from KeenableBot.
03 · Impact
Why Keenable-User matters for your site
If you allow it
- Requests are triggered by real users or their agents
- It follows robots.txt rules for its own token
If you block it
- Keenable publishes no IP ranges for verification
- You may not want AI agents to fetch your pages
04 · Allow
How to allow Keenable-User
robots.txt
User-agent: Keenable-User
Allow: /Cloudflare
# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "Keenable-User")
Action: Skip › All Super Bot Fight Mode rules
# Also check Security › Bots: "Block AI bots" can block it regardless of robots.txt.WordPress
# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: Keenable-User
Allow: /nginx
# nginx serves every user agent by default.
# Make sure no rule like this blocks it:
# if ($http_user_agent ~* "Keenable\-User") { return 403; }Apache
# Apache serves every user agent by default.
# Make sure .htaccess has no rule like this:
# RewriteCond %{HTTP_USER_AGENT} Keenable\-User [NC]
# RewriteRule .* - [F,L]05 · Block
How to block Keenable-User
Keenable-User follows robots.txt, so one rule is enough. Use a server or CDN rule only to stop spoofed copies.
robots.txt
User-agent: Keenable-User
Disallow: /Cloudflare
# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "Keenable-User")
Action: BlockWordPress
# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: Keenable-User
Disallow: /nginx
# In your server { } block:
if ($http_user_agent ~* "Keenable\-User") {
return 403;
}Apache
# .htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Keenable\-User [NC]
RewriteRule .* - [F,L]
</IfModule>06 · User agents
User agents we see for Keenable-User
| User agent | Share | Last seen | Status |
|---|---|---|---|
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Keenable-User/1.0; +https://keenable.ai/bot) |
100% | Unverified |
07 · Verification
Is it really Keenable-User?
Keenable-User’s operator publishes no IP ranges or hostnames, so requests cannot be verified. Treat the user agent as a claim, and watch your logs for unusual request rates.
FAQ
Questions about Keenable-User
What is Keenable-User?
Keenable-User is Keenable.ai's user agent for requests made by a person or an agent on their behalf. It does not crawl automatically.
How do I block Keenable-User?
Add User-agent: Keenable-User with Disallow: / to robots.txt. It is controlled separately from KeenableBot.
What is the difference between Keenable-User and KeenableBot?
KeenableBot crawls pages for Keenable's search index. Keenable-User only fetches specific pages that a user or agent requested.
Last reviewed Oct 8, 2026