Andi Search
SafeUser-agent: Andibot
Category: AI & LLM Bots
SEO impact if blocked: 2/10
Andi
1 crawler operated by Andi
https://andisearch.com/Who Andi is, for site owners
Andi operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated safe.
Blocking Andi carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Andi: Generally safe to allow; provides legitimate crawling value.
Andi at a glance
| Operator | Andi |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Website | andisearch.com |
Crawler operated by Andi
What Andi's crawlers are for
Andi runs 1 crawler in our database. Grouped by the job each one does:
- a training crawler:
Andibot
The highest-priority token is Tier 2. That puts Andi among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat Andi
How often site owners write rules for Andi's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
Andibot | 67 (1.2%) | Not measured |
A Andi token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.
All counts come from 5,583 valid files fetched October 20, 2026.
Writing one policy for Andi
A robots.txt file cannot say "Andi"; it can only name Andi's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Andi fetches through it
User-agent: Andibot
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the robots.txt AI crawler test after any change to see the result for each Andi token, including firewall refusals.
Test yourself: does User-agent: Andi block all of Andi's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token Andibot.
Test yourself: if you block one Andi token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Andi crawler, explained
A one-paragraph brief for every Andi token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Andi Search (
Andibot, Tier 2): a training crawler that collects pages both for training and for search or answers. Rated safe. Andi Search's operator does not clearly document how it treats robots.txt. Write the Andi Search rule anyway, then confirm in your logs that its requests stop. 1.2% of top-site robots.txt files name it.
Common mistakes with Andi's crawlers
The errors we see most often with Andi's crawlers in the files and firewalls we test:
- Assuming that blocking Andi's crawlers removes you from AI answers. It is a training crawler; AI answers are fed by retrieval and user-triggered crawlers with different tokens.
- Blocking Andi's crawlers with a broad
User-agent: *rule that also catches search engines. NameAndibotin its own group instead. - Expecting a Andi's crawlers block to remove content already collected. robots.txt only affects future visits.
All three hide inside a file that looks correct, so check Andi's crawlers from outside after every change.
What our own data shows about Andi
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Andi's marketing. Andi has one token in our database, so the whole picture fits in one place.
Andibot in our records
We first recorded Andibot on June 18, 2026. We could not find a page where Andi names it, so treat the token as reported rather than documented. Andibot is outside our tracked token set, but 67 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 104 AI and LLM crawlers in our database, Andibot sits 22th by priority (Tier 2), level with AddSearchBot, AI2Bot, AI2Bot-DeepResearchEval, aiHitBot. 81 of the 104 share its safe rating. Other operators with a crawler that collects pages both for training and for search or answers: PerplexityBot (Perplexity AI, Tier 1), Bytespider (ByteDance, Tier 2), cohere-ai (Cohere, Tier 2), DeepSeekBot (DeepSeek, Tier 2), DoubaoBot (ByteDance, Tier 2). A policy for Andibot is usually a policy for these too.
A decision record for Andibot
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the Andibot entry reads:
- Operator and job: Andi; it collects pages both for training and for search or answers.
- Priority and behaviour: Tier 2, rated safe, blocking impact low.
- Suggested starting point: Your licensing call: Disallow to refuse training, Allow to permit it.
- Enforcement: Andibot's operator does not clearly document how it treats robots.txt. Write the Andibot rule anyway, then confirm in your logs that its requests stop.
User-agent: Andibot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the Andibot entry whenever Andi announces a change, because a Tier 2 crawler affects visibility directly.
Checking Andibot on your own site
Because Andi runs only Andibot in our records, one check covers the whole operator. Search your access logs for the string Andibot over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Andi publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 2 crawler rated safe is worth confirming every month, and our log checker does the counting for you.
How top sites treat Andi's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Andi's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Andi's crawlers too.
More questions about Andi
- Will blocking Andi affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Andi's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Andi?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Andi on some sections and block it on others?
- Yes. Inside the group for
Andibot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Andi delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Andi offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Andi?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Andi review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI search crawlability check to see the outcome from outside, including any firewall layer.
How to block or allow Andi in robots.txt
This rule covers the single crawler Andi operates. Add it to the robots.txt file at the root of your domain.
Block Andi completely
User-agent: Andibot
Disallow: /
Allow Andi explicitly
User-agent: Andibot
Allow: /
These Andi rules ask; they do not enforce. If a Andi token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Andi
What crawler does Andi run?
Andi operates 1 crawler in our directory: Andi Search (user-agent Andibot).
Should I block Andi?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Andi in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Andibot then Disallow: /.
Does blocking Andi hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Andi does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.