Seogard-Bot
Our technical SEO crawler
Identification
Seogard-Bot/1.0 (+https://seogard.io/bot)142.132.133.166Seogard-Bot analyzes your pages to detect SEO regressions (missing metas, broken SSR, incorrect redirects). It respects robots.txt directives and never overloads your servers.
Whitelisting guides
If your firewall (WAF) blocks our crawler, allow our User-Agent or our IP. Pick your WAF below:
Cloudflare
Step 1 — Create a Custom WAF rule (required)
- Log in to your Cloudflare dashboard
- Select your domain
- Go to Security > WAF > Custom Rules
- Click Create rule
- Name:
Allow Seogard Bot - Click Edit expression and paste:
(ip.src eq 142.132.133.166) or (http.user_agent contains "Seogard-Bot") - Action: Skip
- Check all components:
- All remaining custom rules
- All rate limiting rules
- All managed rules
- All Super Bot Fight Mode Rules
- Place at: First
- Click Deploy
Important: use or (not and) between the IP and the User-Agent so the rule matches when either one is present.
Step 2 — Bot Fight Mode (Free plan only)
On Cloudflare's Free plan, the Skip rule cannot bypass Bot Fight Mode. If the crawl is still blocked after step 1:
- Go to Security > Bots
- Turn off Bot Fight Mode
Pro, Business and Enterprise plans: no need to turn off Bot Fight Mode. The Skip rule from step 1 bypasses it automatically.
Akamai
- Log in to Akamai Control Center
- Go to Security > IP/Geo Firewall
- Add
142.132.133.166to the Allow list - Save and deploy the configuration
Alternative: in Bot Manager, add Seogard-Bot to the list of allowed bots.
AWS WAF
- Open the AWS WAF console
- Create an IP Set containing
142.132.133.166/32 - Add an Allow rule in your Web ACL referencing that IP Set
- Place that rule before your blocking rules
Sucuri
- Log in to the Sucuri dashboard
- Go to Firewall > Access Control
- In Whitelist IP, add
142.132.133.166 - Save
Other firewall
Two ways to allow Seogard-Bot:
Method 1 — By IP (recommended)
Add 142.132.133.166 to your firewall's allow list.
Method 2 — By User-Agent
Create a rule that allows requests whose User-Agent header contains Seogard-Bot.
Self-hosted
If you host Seogard yourself, the crawler runs on your server. The IP address to whitelist is your machine's, not 142.132.133.166.
curl -s ifconfig.meReplace 142.132.133.166 with the IP returned in step 1 in the WAF rules of your choice.
Seogard-Bot/1.0 is identical on Cloud and self-hosted. You can also whitelist by User-Agent alone.
Need help?
If you need assistance configuring your firewall, reach out at [email protected]. We can walk you through it step by step.