SiteGround is blocking SiteGuru’s crawler
Some SiteGround-hosted websites may block SiteGuru’s crawler before we can complete the SEO audit. This usually happens at SiteGround’s Edge/WAF level, or because of security settings in SiteGround, WordPress, or a plugin.
When this happens, SiteGuru may not be able to crawl your website correctly. You may see failed checks, missing pages, or crawl errors.
Why this happens
SiteGuru needs to visit your pages, just like Google and other search engines do, to check your website for SEO issues.
Some hosting providers and security tools block automated crawlers by default. SiteGround may see SiteGuru as an unknown bot and block or rate-limit the requests.
This does not mean your website is down. It usually means SiteGuru needs to be allowed through SiteGround’s security layer.
Step 1: Check blocked traffic in SiteGround
In SiteGround, go to:
Site Tools > Security > Blocked Traffic
Check whether any SiteGuru crawler IPs are blocked. If they are, remove them from the blocked list.
SiteGuru’s crawler IPs are:
54.78.126.239/32
52.17.9.255/32
34.246.125.226/32
3.248.73.25/32
34.253.76.180/32
These are single IP addresses, written in CIDR format. The /32 means “this exact IP address only.”
Step 2: Ask SiteGround to whitelist SiteGuru
If SiteGuru is still blocked, please contact SiteGround support and ask them to whitelist SiteGuru’s crawler.
You can send them this message:
Hi SiteGround support,
We use SiteGuru to run SEO audits on our website, but the crawler appears to be blocked by SiteGround’s Edge/WAF layer.
Please whitelist the SiteGuru crawler.
User-Agent:
SiteGuruCrawler
Crawler IPs:
54.78.126.239/32
52.17.9.255/32
34.246.125.226/32
3.248.73.25/32
34.253.76.180/32
These are single fixed IPv4 addresses, not wider IP ranges.
Please allow these IPs and the
SiteGuruCrawleruser-agent to access the public pages of our website so SiteGuru can complete its SEO audit.
Step 3: Send us the crawl error details if SiteGround needs logs
SiteGround may ask for details of a recent failed crawl attempt. If they do, contact SiteGuru support and include your website URL.
We can help provide details such as:
- The date and time of the failed crawl
- The URL that failed
- The error code returned to SiteGuru
- Any request ID, Ray ID, or similar response header if available
Should I change the User-Agent to Googlebot?
In some cases, changing the crawler User-Agent in SiteGuru’s advanced settings may help. However, if SiteGround blocks the request at its Edge/WAF level, changing the User-Agent may not be enough.
If changing the User-Agent does not solve the issue, SiteGround will need to whitelist SiteGuru’s crawler IPs.
Need help?
If you are not sure what to send to SiteGround, contact SiteGuru support and we’ll help you gather the details they need.
