SplitSignalBot
Semrush operates SplitSignalBot, which crawls sites for the SplitSignal tool, used in Semrush's words to create SEO A/B tests on your website. It honors robots.txt under the token SplitSignalBot. Semrush documents no verification method, states that it does not use any consecutive IP blocks, and publishes no IP range file or reverse-DNS suffix.
What SplitSignalBot does
Semrush does not publish a full user-agent string for SplitSignalBot; the /bot/ page documents it only as a robots.txt User-agent token, shown with a Disallow: / rule as the way to block it. That token is the only string Semrush documents for matching the bot in logs. Semrush describes the crawl as feeding the SplitSignal tool, which creates SEO A/B tests on a website, and gives no further detail on what the bot requests or how often it visits.
Allowing SplitSignalBot lets the SplitSignal tool crawl the site to run its SEO A/B tests. Blocking it stops that crawl, which per Semrush's wording removes the site from SplitSignal testing; Semrush documents no other effect. The block is a robots.txt entry with User-agent: SplitSignalBot and Disallow: /, and Semrush states the bot follows robots.txt, so that entry is the documented control.
Semrush documents no verification method. The operator says it does not use any consecutive IP blocks, and publishes no IP list, ASN or reverse-DNS suffix for this bot. JavaScript execution is also undocumented, so a site owner has only the user-agent token to go on when sorting SplitSignalBot traffic from anything else that reaches the server, and no documented way to confirm that a request carrying the token came from Semrush.
Operator note. Semrush documents this token only as a robots.txt User-agent that can be blocked with "Disallow: /" on its bot page. JavaScript execution and IP addresses are not documented.
Controlling SplitSignalBot with robots.txt
Use the token SplitSignalBot in robots.txt. Semrush documents that SplitSignalBot honors robots.txt directives.
User-agent: SplitSignalBot
Disallow: /User-agent: SplitSignalBot
Allow: /Verifying a request is really SplitSignalBot
Anyone can put SplitSignalBot in a User-Agent header. The operator does not document a verification method. Semrush states that "we do not use any consecutive IP blocks".
Common questions
Should I block SplitSignalBot?
If nobody is running SplitSignal SEO A/B tests on your site, blocking it removes a crawl you are not using; Semrush documents no other effect. If your team uses SplitSignal, blocking the bot stops those tests. Add User-agent: SplitSignalBot with Disallow: / to robots.txt to block it.
Does SplitSignalBot run JavaScript?
The operator's documentation does not say. Semrush's /bot/ page lists SplitSignalBot only as a robots.txt token with a Disallow example and gives no details on JavaScript execution, IP addresses or a full user-agent string.
How do I verify SplitSignalBot?
Semrush documents no verification method. The operator states it does not use any consecutive IP blocks and publishes no IP list or reverse-DNS suffix for this bot. The only documented identifier is the SplitSignalBot user-agent token.
Sources
Every fact on this page was checked against Semrush's own documentation, listed below, and re-checked by a second reviewer before publication. Reviewed September 2026.
Related crawlers
This registry documents how operators describe their own bots so site owners can identify and control them. It does not publish third-party IP lists or guess at undocumented behaviour. To see how your own site responds to automated visitors, the bot detection scanner reads a URL's live response and names the protection it finds.