Keenable user fetch

Keenable user fetch in context

Keenable user fetch is a user-triggered agent operated by Keenable. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under AI and LLM crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 15 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about Keenable user fetch rests on what you want from Keenable, not on its behaviour. How we rate safety and impact.

How site owners treat Keenable user fetch

Our robots.txt study of the Tranco top 10,000 did not track Keenable-User as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Keenable user fetch's operator says it follows robots.txt, so a correctly written Keenable user fetch group is enough to control it.

Keenable crawlers and close alternatives

Keenable user fetch is one of 2 Keenable crawlers in our database. A User-agent: Keenable-User group controls Keenable user fetch only; the other Keenable tokens below need their own lines.

• Keenable-User: this crawler (Tier 3)
• KeenableBot: Keenable Search, builds a search or answer index (Tier 2)

To give Keenable user fetch the same answer as its siblings, stack User-agent: Keenable-User with their lines above one set of rules; to treat Keenable user fetch differently, give it its own group.

Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about Keenable user fetch is usually a decision about the whole group, so check how your file treats these too.

We first recorded Keenable-User on October 19, 2026. Keenable documents it on app.keenable.ai, and we recheck that page before each release.

Which rule Keenable user fetch actually follows

Keenable user fetch reads exactly one group in robots.txt, the most specific one that names Keenable-User, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Keenable-User
Disallow: /drafts/

1. Find the group. Keenable user fetch looks for a group naming Keenable-User. One exists, so it ignores User-agent: * completely.
2. Apply only that group. It is refused /drafts/ and nothing else.
3. The surprise. /private/ is open to Keenable user fetch, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Should you allow Keenable user fetch? Decide by situation

Check Keenable user fetch on your own site

1. Open /robots.txt on your domain and search for Keenable-User. If it is not named, it follows User-agent: *.
2. List the Disallow lines in the group Keenable user fetch follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
3. Look beyond the file. A firewall or bot manager can refuse Keenable user fetch even when robots.txt allows it, and that never shows in the file.
4. Run our crawler access checker to see how Keenable user fetch and every other crawler we track are treated in one pass, including firewall refusals.