Safe Official docs AI & LLM Bots

Sarashina Search

Operated by SB Intuitions

Quick Facts

User-Agent:
SBIntuitions-SearchBot
Category:
AI & LLM Bots
Operator:
SB Intuitions
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
www.sbintuitions.co.jp

Confirmed by the operator

SB Intuitions names SBIntuitions-SearchBot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Sarashina Search?

Sarashina Search is an on-demand AI fetcher operated by SB Intuitions. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into SB Intuitions's assistant.

Sarashina Search is an on-demand AI fetcher operated by SB Intuitions. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into SB Intuitions's assistant.
Sarashina Search uses the user-agent token SBIntuitions-SearchBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Sarashina Search?

✅ No SEO Impact - Blocking Sarashina Search does not affect your rankings in Google, Bing, or any other search engine. Sarashina Search is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
Generally safe to allow; provides legitimate crawling value.

Want to see whether Sarashina Search actually visits you? Read how do I monitor AI bot traffic to my website?

How to block Sarashina Search with robots.txt

<code>User-agent: SBIntuitions-SearchBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: SBIntuitions-SearchBot Disallow: /
Allow all (robots.txt)
User-agent: SBIntuitions-SearchBot Allow: /
Block private only (robots.txt)
User-agent: SBIntuitions-SearchBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Sarashina Search if ($http_user_agent ~* "SBIntuitions-SearchBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Sarashina Search SetEnvIfNoCase User-Agent "SBIntuitions-SearchBot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Sarashina Search safe to allow?

Yes, Sarashina Search is a safe and legitimate crawler operated by SB Intuitions. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Sarashina Search requests resolve to SB Intuitions's domain.

What does Sarashina Search do?

Understanding Sarashina Search's purpose helps you decide whether to allow or block it.

  • Fetches a page only when a user asks an AI assistant to read it
  • Summarizes or extracts the URL the user provided
  • Triggered by real user intent, not bulk crawling
  • Low traffic volume compared with training crawlers
  • Blocking it prevents users from pulling your content into the assistant

Sarashina Search in context

Sarashina Search is a user-triggered agent operated by SB Intuitions. In plain terms, it fetches a page when a person asks an assistant or app to open it. 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 Sarashina Search rests on what you want from SB Intuitions, not on its behaviour. How we rate safety and impact.

How site owners treat Sarashina Search

Our robots.txt study of the Tranco top 10,000 did not track SBIntuitions-SearchBot 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?

Sarashina Search's operator does not clearly document how it treats robots.txt. Write the Sarashina Search rule anyway, then confirm in your logs that its requests stop.

SB Intuitions crawlers and close alternatives

Sarashina Search is one of 2 SB Intuitions crawlers in our database. A User-agent: SBIntuitions-SearchBot group controls Sarashina Search only; the other SB Intuitions tokens below need their own lines.

  • SBIntuitions-SearchBot: this crawler (Tier 2)
  • SBIntuitionsBot: SB Intuitions Crawler, collects pages to train AI models (Tier 2)

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

Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about Sarashina Search is usually a decision about the whole group, so check how your file treats these too.

We first recorded SBIntuitions-SearchBot on September 22, 2026. SB Intuitions documents it on sbintuitions.co.jp, and we recheck that page before each release.

Which rule Sarashina Search actually follows

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

User-agent: *
Disallow: /private/

User-agent: SBIntuitions-SearchBot
Disallow: /drafts/
  1. Find the group. Sarashina Search looks for a group naming SBIntuitions-SearchBot. 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 Sarashina 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.
Test yourself: does a rule under User-agent: * apply to Sarashina Search if the file also has a User-agent: SBIntuitions-SearchBot group?

No. Once a group names it, Sarashina Search reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Sarashina Search remove your pages from AI answers?

Often, yes. Sarashina Search is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: sbintuitions-searchbot the same as User-agent: SBIntuitions-SearchBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Sarashina Search? Decide by situation

Recommended setting for Sarashina Search by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Sarashina Search fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Sarashina Search is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Sarashina Search on your own site

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

Common mistakes with Sarashina Search

The errors we see most often with Sarashina Search in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Sarashina Search. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Sarashina Search as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Sarashina Search visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Sarashina Search from outside after every change.

Spotting Sarashina Search in your logs

robots.txt says what Sarashina Search may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "SBIntuitions-SearchBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "SBIntuitions-SearchBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Sarashina Search user-agent, so confirm the source before acting on a match:

  • SBIntuitions-SearchBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Sarashina Search request with caution.

Frequently Asked Questions

What is the official user-agent string for Sarashina Search?
The official user-agent string for Sarashina Search is: SBIntuitions-SearchBot. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Sarashina Search by performing a reverse-DNS lookup on the source IP.
Is Sarashina Search safe?
Yes, Sarashina Search is a safe and legitimate crawler operated by SB Intuitions. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Sarashina Search hurt my SEO?
✅ No SEO Impact - Blocking Sarashina Search does not affect your rankings in Google, Bing, or any other search engine. Sarashina Search is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
How do I block Sarashina Search in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: SBIntuitions-SearchBot
Disallow: /

This instructs Sarashina Search not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Sarashina Search respect robots.txt?
Sarashina Search is operated by SB Intuitions and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Sarashina Search is crawling my site?
Search your web server access logs for the string SBIntuitions-SearchBot (case-insensitive: grep -i "SBIntuitions-SearchBot" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us