RiggleBot
RiggleBot is our web crawler that scans your pages to identify text elements for A/B testing. It only visits pages you own as a Riggle customer, makes minimal requests, and respects robots.txt.
Bot Identity
IP Address
34.52.172.218
User-Agent
RiggleBot/1.0 (+https://riggleapi.com/bot)
Whitelist Instructions
Cloudflare
Open dashboard →- 1. Log in and select your domain
- 2. Go to Security → WAF → Tools
- 3. Under "IP Access Rules", enter the IP address
- 4. Set Action to Allow and click Add
Sucuri
Open dashboard →- 1. Log in and select your website
- 2. Go to Access Control
- 3. Add the IP to Whitelist IP Addresses
- 4. Save changes
Wordfence
- 1. Go to Wordfence → Firewall in your WordPress admin
- 2. Click the Blocking tab
- 3. Scroll to Allowlisted IP Addresses
- 4. Add the IP address and save
iThemes Security
- 1. Go to Security → Settings
- 2. Click Lockouts in the sidebar
- 3. Find Authorized Hosts section
- 4. Add the IP address and save
All In One WP Security
- 1. Go to WP Security → Firewall
- 2. Click Basic Firewall Rules tab
- 3. Add the IP to the whitelist field
- 4. Save settings
SiteGround Security
- 1. Go to SG Security in WordPress admin
- 2. Click Activity Log tab
- 3. Find any blocked RiggleBot request
- 4. Click Unblock or use server config below
WP Engine
Open dashboard →- 1. Log in and select your environment
- 2. Navigate to Security section
- 3. Contact support to whitelist the IP
WP Engine uses a proprietary firewall. Support can add IP exceptions.
Kinsta
Open dashboard →- 1. Log in and select your site
- 2. Go to Tools → IP Deny
- 3. Ensure the IP is not in the deny list
- 4. Contact support if needed
Flywheel
Open dashboard →- 1. Log in and select your site
- 2. Check Advanced settings
- 3. Contact support to whitelist RiggleBot
Server Configuration
If your platform isn't listed above, add the IP to your server configuration.
Apache (.htaccess)
SetEnvIF Remote_Addr "^34\.52\.172\.218$" AllowedBot Order Deny,Allow Allow from env=AllowedBot
Nginx
allow 34.52.172.218;
Riggle's browser
When someone previews a site in Riggle on a phone, in a demo or from a shared link, the page opens in a browser we run and is shown to them live. A person is looking at every page it asks for and steers it themselves: it doesn't crawl, and nothing it loads is stored. It has no fixed IP address. Each page it requests is signed instead (Web Bot Auth), so your bot protection can verify the request is ours.
Signature-Agent
https://cast.riggleapi.com
Key directory
https://cast.riggleapi.com/.well-known/http-message-signatures-directory
Need help?
If your platform isn't listed or you're having trouble, contact us with your website URL and hosting provider.
sofiane@riggleapi.com