SplitSignalBot user agent
Operated by Semrush
SplitSignalBot is the Semrush crawler for SplitSignal, a tool for SEO A/B tests.
The SplitSignalBot bot at a glance
- SplitSignalBot is operated by Semrush and fetches pages to power a specific product feature.
- The robots.txt token for SplitSignalBot is SplitSignalBot.
- Blocking an SEO tool crawler has no effect on Google or Bing rankings.
- SplitSignalBot robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is SplitSignalBot?
SplitSignalBot crawls pages taking part in a SplitSignal SEO experiment.
Semrush documents it as a separate robots.txt token.
Should you block SplitSignalBot?
Blocking SplitSignalBot is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an SEO tool crawler has no effect on Google or Bing rankings. |
|---|---|
| Effect on AI visibility | No effect on AI answers. Blocking hides your pages and backlinks from that SEO tool, including from competitors who use it, and breaks your own audits in that tool. |
| Follows robots.txt | Yes |
| Recommendation | Your choice |
How to block or allow SplitSignalBot
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 SplitSignalBot is matched case-insensitively.
robots.txt: block
# Block SplitSignalBot
User-agent: SplitSignalBot
Disallow: /robots.txt: allow
# Allow SplitSignalBot
User-agent: SplitSignalBot
Allow: /robots.txt: partial
# Keep SplitSignalBot out of private areas only
User-agent: SplitSignalBot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to SplitSignalBot
if ($http_user_agent ~* "(SplitSignalBot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to SplitSignalBot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (SplitSignalBot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "SplitSignalBot")How to verify real SplitSignalBot traffic
Semrush publishes no IP list or reverse DNS pattern for SplitSignalBot, 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 SplitSignalBot in your server logs
Search the web server access log for the token. The command below counts SplitSignalBot requests per URL on Nginx or Apache.
grep -i "SplitSignalBot" 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à.
SplitSignalBot FAQ
SplitSignalBot uses the robots.txt token "SplitSignalBot". Semrush does not publish a full user-agent string, so match the token inside the User-Agent header.
Yes. Semrush states that SplitSignalBot follows robots.txt rules written for the "SplitSignalBot" token.
Blocking an SEO tool crawler has no effect on Google or Bing rankings. No effect on AI answers. Blocking hides your pages and backlinks from that SEO tool, including from competitors who use it, and breaks your own audits in that tool.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: SplitSignalBot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Semrush publishes no IP list or reverse DNS pattern for SplitSignalBot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "SplitSignalBot", for example with: grep -i "SplitSignalBot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Semrush crawler documentation. 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.
