Keenable Search

Keenable Search in context

Keenable Search is a retrieval crawler that feeds AI search answers operated by Keenable. In plain terms, it builds a search or answer index. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 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 Search rests on what you want from Keenable, not on its behaviour. How we rate safety and impact.

How site owners treat Keenable Search

Our robots.txt study of the Tranco top 10,000 did not track KeenableBot 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 Search's operator says it follows robots.txt, so a correctly written Keenable Search group is enough to control it.

Keenable crawlers and close alternatives

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

• KeenableBot: this crawler (Tier 2)
• Keenable-User: Keenable user fetch, fetches a page when a person asks an assistant or app to open it (Tier 3)

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

Other AI and LLM crawlers that do the same job (builds a search or answer index) include AddSearchBot from AddSearch, AIWebIndex from Lyrenth, atlassian-bot from Atlassian, AzureAI-SearchBot from Microsoft, Cloudflare-AI-Search from Cloudflare, Cloudflare-AutoRAG from Cloudflare. Deciding about Keenable Search is usually a decision about the whole group, so check how your file treats these too.

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

Which rule Keenable Search actually follows

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

User-agent: *
Disallow: /private/

User-agent: KeenableBot
Disallow: /drafts/

1. Find the group. Keenable Search looks for a group naming KeenableBot. 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 Search, 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 Search? Decide by situation

Check Keenable Search on your own site

1. Open /robots.txt on your domain and search for KeenableBot. If it is not named, it follows User-agent: *.
2. List the Disallow lines in the group Keenable Search 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 Search even when robots.txt allows it, and that never shows in the file.
4. Run our website crawlability test to see how Keenable Search and every other crawler we track are treated in one pass, including firewall refusals.