What is Timpibot? How to allow or block Timpi's crawler

Timpibot is Timpi's agent for AI search and live answers. Crawler for Timpi's decentralized search index.

Timpi publishes limited crawler documentation; compliance reports are sparse. If blocking matters, verify behavior in your logs and back the block with a firewall rule.

Add "User-agent: Timpibot" followed by "Disallow: /" to your robots.txt file. Because this bot's robots.txt compliance is not reliable, enforce the block with firewall or CDN rules (for example a Cloudflare WAF rule matching the user agent) if it matters to you.

No. Timpibot is separate from Googlebot, which handles Google Search indexing. Blocking Timpibot has no effect on your traditional search rankings, but it does remove your pages from the AI answers Timpi's assistant serves to its users.

Search your server access logs for the string "Timpibot" — for example: grep -i "Timpibot" /var/log/nginx/access.log | wc -l. Our free AI Bot Log Analyzer does this in your browser: paste a log file and it counts hits per AI crawler, including Timpibot, with per-path breakdowns.

You don't — Timpibot isn't a tool you run. It's Timpi's own crawler, operated by Timpi, that visits your site from their infrastructure. The only control you have over it is whether you allow or block it, via robots.txt or a server rule. If you're looking to crawl other sites yourself, you'd write your own crawler or use a crawling library; sending "Timpibot" as your user agent would be impersonating Timpi.

Almost certainly not. Crawl-delay was never part of the original robots.txt specification — Google has publicly said it ignores the directive, and the AI crawlers that model their parsers on Google's do the same. Timpi publishes no position on crawl-delay for Timpibot, so treat it as unsupported. If Timpibot is hitting your site harder than you want, rate-limit it at the server or CDN instead: a Cloudflare rate-limiting rule or an nginx limit_req zone matched on the user agent will actually be enforced, whereas a crawl-delay line is only a request that this agent likely never reads.

Timpi makes no enforceable commitment that Timpibot honors robots.txt, so the plain answer may be that it simply does not. Before assuming that, rule out the ordinary causes: a cached copy of robots.txt from before your change, a user-agent line that does not actually match, or a block placed in a group this agent does not read. If the hits continue after those are excluded, robots.txt is not going to stop this agent and you need a firewall or CDN rule that returns 403.

Treat it as no unless Timpi says otherwise. Rendering JavaScript costs an order of magnitude more than fetching HTML, and most AI crawlers — unlike Googlebot, which runs a full headless Chrome — read the raw HTML response and stop there. The practical consequence: anything your page loads client-side after the initial response is likely invisible to Timpibot. If your main content is client-rendered, server-render it or pre-render it so the text exists in the first response.

Timpi publishes no IP-range file for Timpibot, which means there is no way to verify a request really came from them. Any traffic claiming this user agent should be treated as unverified. If you need certainty, block on the user agent and accept that you may be blocking impostors rather than the real crawler — and note that the absence of published ranges is itself a signal about how seriously the operator treats crawler transparency.

There is no fixed schedule. Timpibot serves live answers, so its crawl rate tracks demand — pages that come up in Timpi conversations get fetched more often, and a site nobody asks about may see it rarely or never. Frequency also rises with how often your pages change and how many links point at them. The only way to know for your own site is to measure it: grep your access log for the user agent, or paste the log into our AI Bot Log Analyzer, which breaks hits down by date and path in your browser.

Timpi publishes no official documentation for Timpibot. That absence is itself worth noting: an undocumented crawler gives you no stated policy to hold it to, and no published IP ranges to verify it against.