SB Intuitions

Common mistakes with SB Intuitions's crawlers

The errors we see most often with SB Intuitions's crawlers in the files and firewalls we test:

1. Assuming a robots.txt rule will stop SB Intuitions's crawlers. 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 SB Intuitions's crawlers 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 SB Intuitions's crawlers 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 SB Intuitions's crawlers from outside after every change.

Spotting SB Intuitions in your logs

robots.txt says what Sarashina Search and SB Intuitions Crawler may do; your access logs show what they 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|SBIntuitionsBot" /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|SBIntuitionsBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send these user-agents, so confirm the source before acting on a match:

• SBIntuitions-SearchBot: we hold no published IP list, so use reverse DNS where SB Intuitions documents a hostname and treat an unverifiable Sarashina Search request with caution. Check it separately from SB Intuitions Crawler.
• SBIntuitionsBot: we hold no published IP list, so use reverse DNS where SB Intuitions documents a hostname and treat an unverifiable SB Intuitions Crawler request with caution. Check it separately from Sarashina Search.

What our own data shows about SB Intuitions

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 SB Intuitions's marketing. It covers 2 SB Intuitions tokens in turn.

SBIntuitions-SearchBot in our records

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. No file in our top-10,000 scans names SBIntuitions-SearchBot, so any rule you write for it puts you ahead of almost every large site.

Among the 104 AI and LLM crawlers in our database, SBIntuitions-SearchBot sits 80th 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 fetches a page when a person asks an assistant or app to open it: ChatGPT Agent (OpenAI, Tier 1), ChatGPT Operator (OpenAI, Tier 1), ChatGPT-User (OpenAI, Tier 1), ChatGPT-User/2.0 (OpenAI, Tier 1), Claude-SearchBot (Anthropic, Tier 1). A policy for SBIntuitions-SearchBot is usually a policy for these too.

A decision record for SBIntuitions-SearchBot

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 SBIntuitions-SearchBot entry reads:

• Operator and job: SB Intuitions; it fetches a page when a person asks an assistant or app to open it.
• Priority and behaviour: Tier 2, rated safe, blocking impact low.
• Suggested starting point: Allow, and watch it in your logs.
• Enforcement: SBIntuitions-SearchBot's operator does not clearly document how it treats robots.txt. Write the SBIntuitions-SearchBot rule anyway, then confirm in your logs that its requests stop.

User-agent: SBIntuitions-SearchBot
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the SBIntuitions-SearchBot entry whenever SB Intuitions announces a change, because a Tier 2 crawler affects visibility directly.

SBIntuitionsBot in our records

We first recorded SBIntuitionsBot on March 17, 2026. SB Intuitions documents it on sbintuitions.co.jp, and we recheck that page before each release. No file in our top-10,000 scans names SBIntuitionsBot, so any rule you write for it puts you ahead of almost every large site.

Among the 104 AI and LLM crawlers in our database, SBIntuitionsBot sits 81th 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 to train AI models: ClaudeBot (Anthropic, Tier 1), Google-Extended (Google, Tier 1), GPTBot (OpenAI, Tier 1), Meta-ExternalAgent (Meta, Tier 1), AI2Bot (Allen Institute for AI, Tier 2). A policy for SBIntuitionsBot is usually a policy for these too.

A decision record for SBIntuitionsBot

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 SBIntuitionsBot entry reads:

• Operator and job: SB Intuitions; it collects pages to train AI models.
• 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: SBIntuitionsBot's operator does not clearly document how it treats robots.txt. Write the SBIntuitionsBot rule anyway, then confirm in your logs that its requests stop.

User-agent: SBIntuitionsBot
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the SBIntuitionsBot entry whenever SB Intuitions announces a change, because a Tier 2 crawler affects visibility directly.

How top sites treat SB Intuitions'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 SB Intuitions'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 SB Intuitions's crawlers too.

More questions about SB Intuitions

Will blocking SB Intuitions affect my Google rankings?

Only if one of its tokens is a Google search crawler. None of SB Intuitions's tokens are Googlebot, so classic Google rankings are unaffected.

How quickly does a robots.txt change take effect for SB Intuitions?

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 SB Intuitions on some sections and block it on others?

Yes. Inside the group for SBIntuitions-SearchBot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.

Does blocking SB Intuitions delete content it already collected?

No. robots.txt only controls future visits. For content already collected, check whether SB Intuitions offers a removal or opt-out process.

Is a firewall block better than robots.txt for SB Intuitions?

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.