Keenable-User is described on keenable.ai/bot as fetching a single page in real time when a user, or an agent acting for one, asks for it. It is not an automatic crawler. The index crawler is KeenableBot.
Cloudflare lists the user-agent pattern Keenable-User and records no robots.txt commitment or signature scheme, so verify behavior in your logs.
Yes. Keenable-User reads a page in real time when a user or an agent acting for one asks for it.
Keenable-User fetches a single page on request and is not an automatic crawler. Blocking it stops agents using Keenable from reading that page live, though the separate KeenableBot index crawler is unaffected.
Most sites keep Keenable-User allowed because each request maps to a person's task. To opt out:
User-agent: Keenable-User
Disallow: /
Since robots.txt behavior is not confirmed, add edge rules if you need a firm block.
Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.
No. It fetches one page when a user or agent asks for it. The crawler is `KeenableBot`.
Keenable's crawler for public pages in its search index, which answers queries from AI agents with linked sources.
Exa's on-demand fetcher that retrieves a page live when a user or an app built on the Exa API asks for it.
Parallel's user-initiated fetcher that retrieves pages on behalf of users of its web APIs.
Handles user-initiated requests in ChatGPT, accessing external content to provide real-time information; not used for automated crawling or AI training.
Claude-User supports Claude AI users. When individuals ask questions to Claude, it may access websites using a Claude-User agent.
Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.
