AddSearch AI
SafeUser-agent: AddSearchBot
Category: AI & LLM Bots
SEO impact if blocked: 2/10
AddSearch
1 crawler operated by AddSearch
https://www.addsearch.com/Who AddSearch is, for site owners
AddSearch operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated safe.
Blocking AddSearch carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for AddSearch: Generally safe to allow; provides legitimate crawling value.
AddSearch at a glance
| Operator | AddSearch |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Website | www.addsearch.com |
Crawler operated by AddSearch
What AddSearch's crawlers are for
AddSearch runs 1 crawler in our database. Grouped by the job each one does:
- a retrieval crawler that feeds AI search answers:
AddSearchBot
The highest-priority token is Tier 2. That puts AddSearch among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat AddSearch
How often site owners write rules for AddSearch's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
AddSearchBot | 66 (1.2%) | Not measured |
A AddSearch 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 AddSearch
A robots.txt file cannot say "AddSearch"; it can only name AddSearch's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything AddSearch fetches through it
User-agent: AddSearchBot
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 AI crawler tester after any change to see the result for each AddSearch token, including firewall refusals.
Test yourself: does User-agent: AddSearch block all of AddSearch's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token AddSearchBot.
Test yourself: if you block one AddSearch token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each AddSearch crawler, explained
A one-paragraph brief for every AddSearch token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- AddSearch AI (
AddSearchBot, Tier 2): a retrieval crawler that feeds AI search answers that builds a search or answer index. Rated safe. AddSearch AI's operator does not clearly document how it treats robots.txt. Write the AddSearch AI rule anyway, then confirm in your logs that its requests stop. 1.2% of top-site robots.txt files name it.
Common mistakes with AddSearch's crawlers
The errors we see most often with AddSearch's crawlers in the files and firewalls we test:
- Blocking AddSearch's crawlers while trying to stop AI training. Retrieval crawlers fetch pages so answers can cite them; blocking it can remove you from those answers without affecting training.
- Letting a firewall or bot-fight mode refuse AddSearch's crawlers while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
- Forgetting that once a
User-agent: AddSearchBotgroup exists, AddSearch's crawlers ignores every rule underUser-agent: *.
All three hide inside a file that looks correct, so check AddSearch's crawlers from outside after every change.
What our own data shows about AddSearch
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 AddSearch's marketing. AddSearch has one token in our database, so the whole picture fits in one place.
AddSearchBot in our records
We first recorded AddSearchBot on June 18, 2026. We could not find a page where AddSearch names it, so treat the token as reported rather than documented. AddSearchBot is outside our tracked token set, but 66 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, AddSearchBot sits 15th by priority (Tier 2), level with AI2Bot, AI2Bot-DeepResearchEval, aiHitBot, AIWebIndex. 81 of the 104 share its safe rating. Other operators with a crawler that builds a search or answer index: AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2), Cloudflare-AutoRAG (Cloudflare, Tier 2). A policy for AddSearchBot is usually a policy for these too.
A decision record for AddSearchBot
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 AddSearchBot entry reads:
- Operator and job: AddSearch; it builds a search or answer index.
- Priority and behaviour: Tier 2, rated safe, blocking impact low.
- Suggested starting point: Allow, and watch it in your logs.
- Enforcement: AddSearchBot's operator does not clearly document how it treats robots.txt. Write the AddSearchBot rule anyway, then confirm in your logs that its requests stop.
User-agent: AddSearchBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the AddSearchBot entry whenever AddSearch announces a change, because a Tier 2 crawler affects visibility directly.
Checking AddSearchBot on your own site
Because AddSearch runs only AddSearchBot in our records, one check covers the whole operator. Search your access logs for the string AddSearchBot 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. AddSearch 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 AddSearch'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 AddSearch'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 AddSearch's crawlers too.
More questions about AddSearch
- Will blocking AddSearch affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of AddSearch's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for AddSearch?
- 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 AddSearch on some sections and block it on others?
- Yes. Inside the group for
AddSearchBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking AddSearch delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether AddSearch offers a removal or opt-out process.
- Is a firewall block better than robots.txt for AddSearch?
- 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 AddSearch 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 crawler checker to see the outcome from outside, including any firewall layer.
How to block or allow AddSearch in robots.txt
This rule covers the single crawler AddSearch operates. Add it to the robots.txt file at the root of your domain.
Block AddSearch completely
User-agent: AddSearchBot
Disallow: /
Allow AddSearch explicitly
User-agent: AddSearchBot
Allow: /
These AddSearch rules ask; they do not enforce. If a AddSearch 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 AddSearch
What crawler does AddSearch run?
AddSearch operates 1 crawler in our directory: AddSearch AI (user-agent AddSearchBot).
Should I block AddSearch?
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 AddSearch in robots.txt?
Add the following to robots.txt at your domain root: User-agent: AddSearchBot then Disallow: /.
Does blocking AddSearch 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 AddSearch 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.