Andibot user agent
Operated by Andi
Andibot is the crawler reported for Andi, an AI search assistant that summarizes web results.
The Andibot bot at a glance
- Andibot is operated by Andi and indexes web pages so an AI search product can show and cite them in answers.
- The robots.txt token for Andibot is Andibot.
- Blocking an AI search crawler has no effect on Google or Bing rankings.
- Andibot robots.txt support: Not documented.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is Andibot?
Andibot reads pages to produce Andi’s AI summaries.
Andi has not documented its robots.txt behaviour.
Should you block Andibot?
Blocking Andibot is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an AI search crawler has no effect on Google or Bing rankings. |
|---|---|
| Effect on AI visibility | Blocking removes your pages from that AI search index, so its answers can no longer cite or link to your website. |
| Follows robots.txt | Not documented |
| Recommendation | Your choice |
How to block or allow Andibot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token Andibot is matched case-insensitively. robots.txt alone may not stop Andibot, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block Andibot
User-agent: Andibot
Disallow: /robots.txt: allow
# Allow Andibot
User-agent: Andibot
Allow: /robots.txt: partial
# Keep Andibot out of private areas only
User-agent: Andibot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to Andibot
if ($http_user_agent ~* "(Andibot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to Andibot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (Andibot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "Andibot")How to verify real Andibot traffic
Andi publishes no IP list or reverse DNS pattern for Andibot, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find Andibot in your server logs
Search the web server access log for the token. The command below counts Andibot requests per URL on Nginx or Apache.
grep -i "Andibot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
Andibot FAQ
Andibot uses the robots.txt token "Andibot". Andi does not publish a full user-agent string, so match the token inside the User-Agent header.
Andi has not documented how Andibot treats robots.txt. Add a robots.txt rule and back it with a server rule if the traffic matters to you.
Blocking an AI search crawler has no effect on Google or Bing rankings. Blocking removes your pages from that AI search index, so its answers can no longer cite or link to your website.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: Andibot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Andi publishes no IP list or reverse DNS pattern for Andibot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "Andibot", for example with: grep -i "Andibot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
